Supported OS:
Collect Gearman metrics to:
The Gearman check is included in the Datadog Agent package, so you don’t need to install anything else on your Gearman job servers.
Follow the instructions below to configure this check for an Agent running on a host. For containerized environments, see the Containerized section.
Edit the gearmand.d/conf.yaml file, in the conf.d/ folder at the root of your Agent’s configuration directory to start collecting your Gearman performance data. See the sample gearmand.d/conf.yaml for all available configuration options.
init_config:
instances:
- server: localhost
port: 4730For containerized environments, see the Autodiscovery Integration Templates for guidance on applying the parameters below.
| Parameter | Value |
|---|---|
<INTEGRATION_NAME> | gearmand |
<INIT_CONFIG> | blank or {} |
<INSTANCE_CONFIG> | {"server":"%%host%%", "port":"4730"} |
Run the Agent’s status subcommand and look for gearmand under the Checks section.
| gearman.unique_tasks (gauge) | The number of all functions registered with Gearman. Shown as task |
| gearman.running (gauge) | The total number of running Gearman jobs. Shown as task |
| gearman.queued (gauge) | The total number of jobs in the queue. Shown as task |
| gearman.workers (gauge) | The total number of capable Gearman workers. Shown as process |
| gearman.running_by_task (gauge) | The number of running Gearman jobs by task. Shown as task |
| gearman.queued_by_task (gauge) | The number of jobs in the queue by task. Shown as task |
| gearman.workers_by_task (gauge) | The number of capable Gearman workers by task. Shown as process |
The Gearmand check does not include any events.
gearman.can_connect:
Returns Critical if the Agent cannot connect to Gearman to collect metrics.
Need help? Contact Datadog support.
On this Page
