-
Notifications
You must be signed in to change notification settings - Fork 489
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This adds a build duration metric with attributes related to the build id, build ref, driver name, and the resulting status of the build. This also modifies some aspects of how the resource is configured by including `service.instance.id`. This id is used to uniquely identify the CLI invocation for use in downstream aggregators. This allows downstream aggregators to know that the metric for an instance has not reset and that it is a unique invocation for future aggregation. Some work will have to be done in the aggregator to prevent the storage of this instance id as it can cause issues with cardinality limitations, but it's necessary for the initial reporter to include this. The temporality selector is still the same, but has been removed from the otlp exporter options since that one doesn't seem to do anything. I also recently learned the temporality didn't do what I thought it did. I thought it would allow for multiple different invocations to be treated as the same instance for the purposes of aggregation. It does not work this way as the metric sdk considers each of these a gap reset. That's the reason the instance id was added. This makes the difference between cumulative and delta mostly cosmetic, but delta temporality has some benefits for downstream consumers for aggregation so it's likely good to keep. The cli count has been removed as it doesn't contain anything new and wasn't a useful metric. The naming of metrics has also been changed from using `docker` as a prefix and instead relying on the instrumentation name. Signed-off-by: Jonathan A. Sternberg <[email protected]>
- Loading branch information
1 parent
2c3d7da
commit 3764dfa
Showing
15 changed files
with
327 additions
and
120 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.