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
Is your feature request related to a problem? Please describe.
We publish custom events to new-relic using its record_custom_event API present in python agent and use nrql to create dashboards from those events. Requests processed by our applications are mostly async and we want to create dashboards to typical app metrics like traffic, latency, failure_rate, requests_stuck_until_last_x_mins etc.
The problem is these metrics are published at different timestamps which leads to formation of incorrect hypothesis when looking at a holistic dashboard. While we do publish a custom_timestamp field as well in our events, the plotting of events can only be done via timestamp field. We want an ability to pass a timestamp field in record_custom_event API for python agent so that we can keep all our events related to a single request in sync.
Feature Description
Update record_custom_event API signature to provide support for timestamp
We could've used simple event API that provides but then would have to re-write the entire logic of publishing events to NR. I see the python agent lib has a nice way of collecting sampled events and publishing them and we want to avoid re-inventing the wheel.
Additional context
None
Priority
Really Want
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We publish custom events to new-relic using its
record_custom_event
API present in python agent and usenrql
to create dashboards from those events. Requests processed by our applications are mostly async and we want to create dashboards to typical app metrics liketraffic
,latency
,failure_rate
,requests_stuck_until_last_x_mins
etc.The problem is these metrics are published at different timestamps which leads to formation of incorrect hypothesis when looking at a holistic dashboard. While we do publish a custom_timestamp field as well in our events, the plotting of events can only be done via timestamp field. We want an ability to pass a
timestamp
field inrecord_custom_event
API for python agent so that we can keep all our events related to a single request in sync.Feature Description
Update
record_custom_event
API signature to provide support fortimestamp
Describe Alternatives
We could've used simple event API that provides but then would have to re-write the entire logic of publishing events to NR. I see the python agent lib has a nice way of collecting sampled events and publishing them and we want to avoid re-inventing the wheel.
Additional context
None
Priority
Really Want
The text was updated successfully, but these errors were encountered: