-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Namespace not being used with Sidekiq Pro #292
Comments
Is anyone able to help with this? |
Any reason why you've chosen the |
@carlosroman are you suggesting that even metrics not belonging to Sidekiq would have the prefix And I'd say that in theory it would cause all metrics to have the |
Sorry, I thought you meant that all your metrics are getting |
@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.*
The text was updated successfully, but these errors were encountered: