- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
Supported OS
This integration monitors Sidekiq through Dogstatsd. It collects metrics through Datadog’s Dogstatsd Ruby client.
Note Only Sidekiq Pro (>= 3.6) or Enterprise (>= 1.1.0) users can collect metrics.
The Sidekiq integration is packaged with the Datadog Agent. No additional installation is needed on your server.
Install the dogstatsd-ruby
gem:
gem install dogstatsd-ruby
Enable Sidekiq Pro metric collection by including this in your initializer; for a containerized deployment, update localhost
to your Agent container address:
require 'datadog/statsd' # gem 'dogstatsd-ruby'
Sidekiq::Pro.dogstatsd = ->{ Datadog::Statsd.new('localhost', 8125, namespace:'sidekiq') }
Sidekiq.configure_server do |config|
config.server_middleware do |chain|
require 'sidekiq/middleware/server/statsd'
chain.add Sidekiq::Middleware::Server::Statsd
end
end
If you are using Sidekiq Enterprise and would like to collect historical metrics, include this line as well:
Sidekiq.configure_server do |config|
# history is captured every 30 seconds by default
config.retain_history(30)
end
See the Sidekiq Pro and Enterprise documentation for more information, and the Dogstatsd Ruby documentation for further configuration options.
Update the Datadog Agent main configuration file datadog.yaml
by adding the following configs:
# dogstatsd_mapper_cache_size: 1000 # default to 1000
dogstatsd_mapper_profiles:
- name: sidekiq
prefix: "sidekiq."
mappings:
- match: 'sidekiq\.sidekiq\.(.*)'
match_type: "regex"
name: "sidekiq.$1"
- match: 'sidekiq\.jobs\.(.*)\.perform'
name: "sidekiq.jobs.perform"
match_type: "regex"
tags:
worker: "$1"
- match: 'sidekiq\.jobs\.(.*)\.(count|success|failure)'
name: "sidekiq.jobs.worker.$2"
match_type: "regex"
tags:
worker: "$1"
These parameters can also be set by adding the DD_DOGSTATSD_MAPPER_PROFILES
environment variable to the Datadog Agent.
sidekiq.batches.complete (count) | Count of when a batch is completed |
sidekiq.batches.created (count) | Count of when a batch is created |
sidekiq.batches.success (count) | Count of when a batch is successful |
sidekiq.busy (count) | Total Busy Size (Enterprise only) Shown as job |
sidekiq.dead (count) | Total Dead Size (Enterprise only) Shown as job |
sidekiq.enqueued (count) | Total size of all known queues (Enterprise only) Shown as job |
sidekiq.failed (count) | Number of job executions which raised an error (Enterprise only) Shown as job |
sidekiq.jobs.count (count) | Total count of Sidekiq jobs Shown as job |
sidekiq.jobs.expired (count) | Count of when a job is expired Shown as job |
sidekiq.jobs.failure (count) | Total count of failed Sidekiq jobs Shown as job |
sidekiq.jobs.perform.95percentile (gauge) | 95th percentile of amount of time spent in a worker Shown as millisecond |
sidekiq.jobs.perform.avg (gauge) | Average amount of time spent in a worker Shown as millisecond |
sidekiq.jobs.perform.count (gauge) | Count of the amount of time spent in a worker Shown as millisecond |
sidekiq.jobs.perform.max (gauge) | Max amount of time spent in a worker Shown as millisecond |
sidekiq.jobs.perform.median (gauge) | Median amount of time spent in a worker Shown as millisecond |
sidekiq.jobs.recovered.fetch (count) | Count of when a job is recovered by super_fetch after process crash Shown as job |
sidekiq.jobs.recovered.push (count) | Count of when a job is recovered by reliable_push after network outage Shown as job |
sidekiq.jobs.success (count) | Total count of successful Sidekiq jobs Shown as job |
sidekiq.jobs.worker.count (count) | Count of Sidekiq jobs Shown as job |
sidekiq.jobs.worker.failure (count) | Count of failed Sidekiq jobs Shown as job |
sidekiq.jobs.worker.success (count) | Count of successful Sidekiq jobs Shown as job |
sidekiq.processed (count) | Number of job executions completed (success or failure) (Enterprise only) Shown as job |
sidekiq.retries (count) | Total retries size (Enterprise only) Shown as job |
sidekiq.scheduled (count) | Total Scheduled Size (Enterprise only) Shown as job |
The Sidekiq integration also allows custom metrics, see Sidekiq Enterprise Historical Metrics.
Collecting logs is disabled by default in the Datadog Agent. Enable it in the datadog.yaml
file with:
logs_enabled: true
Add this configuration block to your sidekiq.d/conf.yaml
file to start collecting your Sidekiq logs:
logs:
- type: file
path: /var/log/sidekiq.log
source: sidekiq
service: <SERVICE>
Change the path
and service
parameter values and configure them for your environment. If you cannot find your logs, see Sidekiq Logging.
Sidekiq does not include any service checks.
Sidekiq does not include any events.
Need help? Contact Datadog support.