-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
Collectd receiver is not processing meta #30036
Comments
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
any update on this? |
Not sure how to exactly help you. Do you want to open a failing test PR with your exact requirements? |
@atoulme , as you can see from the above payload meta attribute is pushed from the collectd http plugin, however collectd receiver plugin the dropping that information. Without that information data pushed via googlemanagedprometheus exporter shall fail stating the error duplicate timeseries as those fileds are essential to be kept into scraped metrics. Let me know this helps, i can add more detail if required. Arguably, another fix would simply be that meta attributes are pushed into the scraped metrics so make each entry uniq, further avoiding the issue of duplicate metrics. |
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself. |
This issue has been closed as inactive because it has been stale for 120 days with no activity. |
Component(s)
receiver/collectd
What happened?
Description
Collectd receiver is not forwarding the meta payload for processing. This is a issue where duplicate timeseries is not allowed, such as googlemanagedprometheus exporter.
Steps to Reproduce
Otle config
Expected Result
It should get process and otel should add meta fields as the labels.
Actual Result
Meta fields are dropped post processing causing the issue of duplicate timeseries in googlemanagedprometheus exporter.
Collector version
0.80.0
Environment information
Environment
OS: (e.g., "Ubuntu 20.04")
Compiler(if manually compiled): (e.g., "go 14.2")
root@cluster-3a83-m:/etc/otelcol-contrib# cat /etc/*release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
root@cluster-3a83-m:/etc/otelcol-contrib#
OpenTelemetry Collector configuration
Log output
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: