-
Notifications
You must be signed in to change notification settings - Fork 197
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
Undesired metrics added #1197
Labels
Comments
as you can see there is a lot of jmx_* metrics but for some reason amazon-cloudwatch-agent is grabbing only
although I explicitly said I don't want any of those jmx_ since I used I principle I expected only to see |
This issue was marked stale due to lack of activity. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I set amazon-cloudwatch-agent to only grab a single prometheus metric
java_lang_memory_heapmemoryusage_used
but amazon-cloudwatch-agent is adding the following undesired metrics to the PutLogEvents
jmx_scrape_cached_beans
jmx_scrape_duration_seconds
jmx_scrape_error
CloudWatch log event:
the
.CloudWatchMetrics.Metrics
contains 4 elements where I only expected one.I in principle don't want
jmx_scrape_cached_beans
,jmx_scrape_duration_seconds
orjmx_scrape_error
as a cloudwatch metric at all (specially I don't want to pay for those) .I believe it's a bug to be sending those since I explicitly set only
java_lang_memory_heapmemoryusage_used
unless I misunderstood the configuration , if so , is there any way to prevent thosejmx_xxx
metrics to be included?Steps to reproduce
If possible, provide a recipe for reproducing the error.
What did you expect to see?
A clear and concise description of what you expected to see.
What did you see instead?
A clear and concise description of what you saw instead.
What version did you use?
Version: Version: CWAgent/1.300039.0b612 (go1.22.2; linux; amd64)
What config did you use?
config.json
prometheus.yaml
prometheus_sd_jmx.yaml
Environment
OS: (e.g., "Ubuntu 20.04")
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: