-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
[reciever/haproxy] Default resource attributes are not set on the emitted metrics #24920
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
receiver/haproxy
Comments
Pinging code owners for receiver/haproxy: @atoulme @MovieStoreGuy. See Adding Labels via Comments if you do not have permissions to add labels yourself. |
Hello @dmitryax , could you please assign this issue to me, i would like to spend some time resolving this feature, thanks |
Thanks @sakulali! |
codeboten
pushed a commit
that referenced
this issue
Sep 21, 2023
jorgeancal
pushed a commit
to jorgeancal/opentelemetry-collector-contrib
that referenced
this issue
Oct 9, 2023
jmsnll
pushed a commit
to jmsnll/opentelemetry-collector-contrib
that referenced
this issue
Nov 12, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Extra attention is needed
receiver/haproxy
The following resource attributes defined in metadata.yaml as enabled by default but not being set on the emitted metrics:
haproxy.url
,haproxy.pid
,haproxy.sid
,haproxy.iid
,haproxy.type
,haproxy.algo
. They should be either removed from metadata.yaml or set on the metrics.Only
haproxy.addr
,haproxy.proxy_name
andhaproxy.service_name
are usedThe text was updated successfully, but these errors were encountered: