Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[WIP] Add protocol for dynamic configuration service #155

Closed
Prev Previous commit
Next Next commit
Clarify fingerprint documentation
  • Loading branch information
wtong98 committed Jun 11, 2020
commit 5406581153f7ff56c8df47588e2a5d8a620a5494

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ message ConfigRequest{
opentelemetry.proto.resource.v1.Resource resource = 2;

// Optional. The value of ConfigResponse.fingerprint for the last configuration
// a resource received that was successfully applied.
// a resource received, regardless whether it was successfully applied.
bytes last_known_fingerprint = 3;
}

Expand All @@ -51,6 +51,12 @@ message ConfigResponse {
// ConfigRequest.last_known_fingerprint, then all other fields besides
// fingerprint in the response are optional, or the same as the last update if
// present.
//
// The exact mechanics of generating the fingerprint is up to the
// implementation. However, a fingerprint must be deterministically determined
// by the configurations -- the same configuration will generate the same
// fingerprint on any instance of an implementation. Hence using a timestamp is
// unacceptable, but a deterministic hash is fine.
bytes fingerprint = 2;

// Dynamic configs specific to metrics
Expand Down