-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
[new_relic sink] actually set the metric type in the metrics API model object #13903
Comments
The models for count metrics are different in New Relic and Vector. While New Relic expects it to contain an For more info on New Relic metric model: https://docs.newrelic.com/docs/data-apis/understand-data/metric-data/metric-data-type/ EDIT: Actually, because in Vector the count value keeps incrementing and contains the accumulated count (every metric sent contains the previous count value plus the new ones that happened since the last metric was sent), I think it is pretty much akin to the concept of gauge, and it's safe to just send Vector count metrics as New Relic gauge metrics. For New Relic, a gauge is just a value that changes over time, up and down. For Vector a count is a value that changes over time but only up (or zero). |
@jszwedko please correct me if I'm wrong regarding how Vector count metrics work. |
We do have a metric normalizer layer for all metrics sinks that can convert any absolute metrics (including counters) into incremental values. We can easily setup this layer to convert counters to incremental values. For the interval, It sounds like storing the previous request time and emitting the difference between that and now may be sufficient, as that would be interval over which the counter has accumulated. |
No description provided.
The text was updated successfully, but these errors were encountered: