[awscontainerinsightreceiver] Enable usage of user defined collection interval in awscontainerinsightreceiver #319
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Container Insights supports configuring a collection interval via the CWAgent json config that dictates how often the metrics should be collected from the various sources such as cadvisor.
The collection internal is not used for all the sources the metrics are retrieved from, including:
This change adjusts the containerinsights receiver to pass the CollectionInterval defined in the receiver config on to each scraper.
(metrics_collection_interval in CW Agent config)
opentelemetry-collector-contrib/receiver/awscontainerinsightreceiver/config.go
Line 19 in cb251fe
opentelemetry-collector-contrib/receiver/awscontainerinsightskueuereceiver/config.go
Line 13 in cb251fe
Note: For EFA, the original default collection interval value of 20s will be used if:
Testing
Tested on an EKS Cluster running GPU and Neuron.
Changed CollectionInterval to 30.
Count of metrics increased from 1 per minute to 2 per minute.
Graph of DCGM Exporter metrics count with multiple collection intervals specified:
15s, 30s, 60s, and not-specified (defaults to 60s)