-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
bug(new_relic sink): tags not sent with metrics, leading to unwanted aggregation/downsampling #13377
Comments
Additionally, from taking a look at the I'll open a separate ticket to track the lack of full metric support. |
Opened #13781 to track further improvements to the metrics support for the |
@jszwedko I'm currently working on this issue, could you assign it to me? |
Thanks for the contribution @asllop! |
@tobz distribution metrics are not actually supported by the New Relic Metric API. Internally, New Relic can handle this type of metrics (https://docs.newrelic.com/docs/data-apis/understand-data/metric-data/metric-data-type/), but the API only allows injecting gauge, count and summary metrics (https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/report-metrics-metric-api/#send-metric-data). And regarding count metrics, pleas check out this discussion. |
A note for the community
Problem
NewRelic sink ( https://vector.dev/docs/reference/configuration/sinks/new_relic/ ) does not support
.tags
object, but instead of.tags
, NR supports.attributes
( https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/report-metrics-metric-api/ )Remapping
.tags
to.attributes
via VRL does not work.Same metric from different sources ( where for example
.tags.appname
will be different ) shipped via the same Vector instance will be mixed in NR timeseries data. Querying metric based on.tags.appname
metadata value would be impossible then.Configuration
No response
Version
timberio/vector:0.22.2-debian image
Debug Output
No response
Example Data
No response
Additional Context
No response
References
No response
The text was updated successfully, but these errors were encountered: