You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an informative issue or question for dogstreamer.
After hunting the issue for 48hr, I finally went through source code and found all metrics that are parsed by my log parser were not sent to datadog HQ.
Now suppose in DataDog I want to monitor number of status_code:500 per $host. Basically I want to monitor for which $host I am getting status_code:500. This will not be possible since Dogstream is submitting medians based on timestamp and metric_name (deleting most of the data)
This implementation would be better if the function __aggregate also considers tags associated with metric but that would also fail in above usecase.
Now my question is:
Why metrics aggregation is necessary, why can't log parser send all the metrics returned?
How should I implement my usecase with present implementation?
The text was updated successfully, but these errors were encountered:
This is an informative issue or question for dogstreamer.
After hunting the issue for 48hr, I finally went through source code and found all metrics that are parsed by my log parser were not sent to datadog HQ.
The reason for the same is function _aggregate.
Use case where this implementation fails:
Suppose I am parsing Nginx access logs.
My log format is:
After parsing the logs I am sending metric:
Now suppose in DataDog I want to monitor number of
status_code:500
per$host
. Basically I want to monitor for which$host
I am gettingstatus_code:500
. This will not be possible since Dogstream is submitting medians based ontimestamp
andmetric_name
(deleting most of the data)This implementation would be better if the function __aggregate also considers
tags
associated with metric but that would also fail in above usecase.Now my question is:
The text was updated successfully, but these errors were encountered: