Open travisTheOrange opened 2 months ago
Is anyone able to help with this?
Any reason why you've chosen the namespace
as being sidekiq
? This is causing all metrics to have sidekiq
appended to them, see here.
@carlosroman are you suggesting that even metrics not belonging to Sidekiq would have the prefix sidekiq.*
? So metrics from Datadog would all be prefixed with sidekiq.*
?
And I'd say that in theory it would cause all metrics to have the sidekiq.*
prefix, however, as per my raised issue, no metrics are being prefixed with sidekiq.*
Sorry, I thought you meant that all your metrics are getting sidekiq
appended to them. So adding a namespace
doesn't seem to actually prefix the metrics at the moment?
@carlosroman yeah exactly. Although I raised this issue in the Sidekiq repo and was told the issue is known and being worked on
We're using Datadog and have configured both DD and Sidekiq Pro to send Sidekiq metrics to our Datadog agent. However, when in Datadog the only way we can view the various metrics from Sidekiq is with the prefix
jobs.*
, rather thansidekiq.jobs.*
.Our Sidekiq config file (located in
config/initializers/sidekiq.rb
) looks like this:The first line within the
Sidekiq.configure_server
block was originally not there. Previously we had this line outside the config block, set as:Which resulted in no metrics being sent, maybe. We are seeing metrics in DD now, but we're unsure if it's because of the aforementioned code change or using the prefix
jobs.*
instead ofsidekiq.jobs.*