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
Our app runs on heroku, we manage to setup yabeda-sidekiq with a custom exporter we built to send metrics to the logs, so we could parse it somewhere else, worked without problem
But I was trying to use yabeda-prometheus and the /metric endpoint. Locally I got the same scenario from here #27, tried configuring both suggested solutions but I couldn't get all metrincs in a single /metric endpoint.
But reading all the info about multi process and containerize scenarios, I come to the conclusion that the combo yabed-sidekiq+ yabeda-prometheus won't work on a heroku setup that have sidekiq running in multiple dynos, correct? I can't expose everything and consolidate the data in a safe way before exposing it.
Or did I miss something?
The text was updated successfully, but these errors were encountered:
Hi there, before anything very nice 😃
Our app runs on heroku, we manage to setup
yabeda-sidekiq
with a custom exporter we built to send metrics to the logs, so we could parse it somewhere else, worked without problemBut I was trying to use
yabeda-prometheus
and the/metric
endpoint. Locally I got the same scenario from here #27, tried configuring both suggested solutions but I couldn't get all metrincs in a single/metric
endpoint.But reading all the info about multi process and containerize scenarios, I come to the conclusion that the combo
yabed-sidekiq
+yabeda-prometheus
won't work on a heroku setup that have sidekiq running in multiple dynos, correct? I can't expose everything and consolidate the data in a safe way before exposing it.Or did I miss something?
The text was updated successfully, but these errors were encountered: