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
We started to use this for monitoring sidekiq job for datadog.
Currently this library creates one metrics for job name, (success, error, latency). It would be very handy if
we can have sidekiq_job.latency as metric name and job_name and result as tag. Of course it will create cardinality explosion if you have many jobs but for small apps this will be fine.
If metric is structured that way, setting up monitor/alert will be much easier on datadog, we can simply have one catch-all monitor for all job error count for instance.
The text was updated successfully, but these errors were encountered:
Thanks for building and publishing this library!
We started to use this for monitoring sidekiq job for datadog.
Currently this library creates one metrics for job name, (success, error, latency). It would be very handy if
we can have
sidekiq_job.latency
as metric name andjob_name
andresult
as tag. Of course it will create cardinality explosion if you have many jobs but for small apps this will be fine.If metric is structured that way, setting up monitor/alert will be much easier on datadog, we can simply have one catch-all monitor for all job error count for instance.
The text was updated successfully, but these errors were encountered: