@cryptotaxi247 / netdata-1 / commits / bf649dd0e

Regenerate integrations.js (#18299)

Co-authored-by: ilyam8 <22274335+ilyam8@users.noreply.github.com>

Netdata bot committed Aug 9, 2024 at 12:06 UTC bf649dd0e98082eaffacd5e0510ded40e1301819

5 files changed +307 -73

integrations/integrations.js

+36 -36

@@ -4248,6 +4248,42 @@ export const integrations = [

4248 "edit_link": "https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/modules/freeradius/metadata.yaml",

4249 "related_resources": ""

4250 },

4251 + {

4252 + "meta": {

4253 + "id": "collector-go.d.plugin-gearman",

4254 + "plugin_name": "go.d.plugin",

4255 + "module_name": "gearman",

4256 + "monitored_instance": {

4257 + "name": "Gearman",

4258 + "link": "https://gearman.org/",

4259 + "categories": [

4260 + "data-collection.distributed-computing-systems"

4261 + ],

4262 + "icon_filename": "gearman.png"

4263 + },

4264 + "related_resources": {

4265 + "integrations": {

4266 + "list": []

4267 + }

4268 + },

4269 + "info_provided_to_referring_integrations": {

4270 + "description": ""

4271 + },

4272 + "keywords": [

4273 + "gearman"

4274 + ],

4275 + "most_popular": false

4276 + },

4277 + "overview": "# Gearman\n\nPlugin: go.d.plugin\nModule: gearman\n\n## Overview\n\nMonitors jobs activity, priority and available workers. It collects summary and function-specific statistics.\n\n\nThis collector connects to a Gearman instance via TCP socket and executes the following commands:\n\n- status\n- priority-status\n\n\nThis collector is supported on all platforms.\n\nThis collector supports collecting metrics from multiple instances of this integration, including remote instances.\n\n\n### Default Behavior\n\n#### Auto-Detection\n\nBy default, it detects Gearman instances running on localhost that are listening on port 4730.\n\n\n#### Limits\n\nThe default configuration for this integration does not impose any limits on data collection.\n\n#### Performance Impact\n\nThe default configuration for this integration is not expected to impose a significant performance impact on the system.\n",

4278 + "setup": "## Setup\n\n### Prerequisites\n\nNo action required.\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `go.d/gearman.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config go.d/gearman.conf\n```\n#### Options\n\nThe following options can be defined globally: update_every, autodetection_retry.\n\n\n{% details open=true summary=\"Config options\" %}\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| update_every | Data collection frequency. | 1 | no |\n| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |\n| address | The IP address and port where the Gearman service listens for connections. | 127.0.0.1:11211 | yes |\n| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |\n\n{% /details %}\n#### Examples\n\n##### Basic\n\nA basic example configuration.\n\n{% details open=true summary=\"Config\" %}\n```yaml\njobs:\n - name: local\n address: 127.0.0.1:4730\n\n```\n{% /details %}\n##### Multi-instance\n\n> **Note**: When you define multiple jobs, their names must be unique.\n\nCollecting metrics from local and remote instances.\n\n\n{% details open=true summary=\"Config\" %}\n```yaml\njobs:\n - name: local\n address: 127.0.0.1:4730\n\n - name: remote\n address: 203.0.113.0:4730\n\n```\n{% /details %}\n",

4279 + "troubleshooting": "## Troubleshooting\n\n### Debug Mode\n\nTo troubleshoot issues with the `gearman` collector, run the `go.d.plugin` with the debug option enabled. The output\nshould give you clues as to why the collector isn't working.\n\n- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on\n your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`.\n\n ```bash\n cd /usr/libexec/netdata/plugins.d/\n ```\n\n- Switch to the `netdata` user.\n\n ```bash\n sudo -u netdata -s\n ```\n\n- Run the `go.d.plugin` to debug the collector:\n\n ```bash\n ./go.d.plugin -d -m gearman\n ```\n\n### Getting Logs\n\nIf you're encountering problems with the `gearman` collector, follow these steps to retrieve logs and identify potential issues:\n\n- **Run the command** specific to your system (systemd, non-systemd, or Docker container).\n- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.\n\n#### System with systemd\n\nUse the following command to view logs generated since the last Netdata service restart:\n\n```bash\njournalctl _SYSTEMD_INVOCATION_ID=\"$(systemctl show --value --property=InvocationID netdata)\" --namespace=netdata --grep gearman\n```\n\n#### System without systemd\n\nLocate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name:\n\n```bash\ngrep gearman /var/log/netdata/collector.log\n```\n\n**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues.\n\n#### Docker Container\n\nIf your Netdata runs in a Docker container named \"netdata\" (replace if different), use this command:\n\n```bash\ndocker logs netdata 2>&1 | grep gearman\n```\n\n",

4280 + "alerts": "## Alerts\n\nThere are no alerts configured by default for this integration.\n",

4281 + "metrics": "## Metrics\n\nMetrics grouped by *scope*.\n\nThe scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.\n\n\n\n### Per Gearman instance\n\nThese metrics refer to the entire monitored application.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.queued_jobs_activity | running, waiting | jobs |\n| gearman.queued_jobs_priority | high, normal, low | jobs |\n\n### Per Gearman instance\n\nThese metrics refer to the Function (task).\n\nLabels:\n\n| Label | Description |\n|:-----------|:----------------|\n| function_name | Function name. |\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.function_queued_jobs_activity | running, waiting | jobs |\n| gearman.function_queued_jobs_priority | high, normal, low | jobs |\n| gearman.function_workers | available | workers |\n\n",

4282 + "integration_type": "collector",

4283 + "id": "go.d.plugin-gearman-Gearman",

4284 + "edit_link": "https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/modules/gearman/metadata.yaml",

4285 + "related_resources": ""

4286 + },

4287 {

4288 "meta": {

4289 "id": "collector-go.d.plugin-geth",

@@ -18957,42 +18993,6 @@ export const integrations = [

18993 "edit_link": "https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/exim/metadata.yaml",

18994 "related_resources": ""

18995 },

18960 - {

18961 - "meta": {

18962 - "plugin_name": "python.d.plugin",

18963 - "module_name": "gearman",

18964 - "monitored_instance": {

18965 - "name": "Gearman",

18966 - "link": "http://gearman.org/",

18967 - "categories": [

18968 - "data-collection.distributed-computing-systems"

18969 - ],

18970 - "icon_filename": "gearman.png"

18971 - },

18972 - "related_resources": {

18973 - "integrations": {

18974 - "list": []

18975 - }

18976 - },

18977 - "info_provided_to_referring_integrations": {

18978 - "description": ""

18979 - },

18980 - "keywords": [

18981 - "gearman",

18982 - "gearman job server"

18983 - ],

18984 - "most_popular": false

18985 - },

18986 - "overview": "# Gearman\n\nPlugin: python.d.plugin\nModule: gearman\n\n## Overview\n\nMonitor Gearman metrics for proficient system task distribution. Track job counts, worker statuses, and queue lengths for effective distributed task management.\n\nThis collector connects to a Gearman instance via either TCP or unix socket.\n\nThis collector is supported on all platforms.\n\nThis collector supports collecting metrics from multiple instances of this integration, including remote instances.\n\n\n### Default Behavior\n\n#### Auto-Detection\n\nWhen no configuration file is found, the collector tries to connect to TCP/IP socket: localhost:4730.\n\n#### Limits\n\nThe default configuration for this integration does not impose any limits on data collection.\n\n#### Performance Impact\n\nThe default configuration for this integration is not expected to impose a significant performance impact on the system.\n",

18987 - "setup": "## Setup\n\n### Prerequisites\n\n#### Socket permissions\n\nThe gearman UNIX socket should have read permission for user netdata.\n\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `python.d/gearman.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config python.d/gearman.conf\n```\n#### Options\n\nThere are 2 sections:\n\n* Global variables\n* One or more JOBS that can define multiple different instances to monitor.\n\nThe following options can be defined globally: priority, penalty, autodetection_retry, update_every, but can also be defined per JOB to override the global values.\n\nAdditionally, the following collapsed table contains all the options that can be configured inside a JOB definition.\n\nEvery configuration JOB starts with a `job_name` value which will appear in the dashboard, unless a `name` parameter is specified.\n\n\n{% details open=true summary=\"Config options\" %}\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| update_every | Sets the default data collection frequency. | 5 | no |\n| priority | Controls the order of charts at the netdata dashboard. | 60000 | no |\n| autodetection_retry | Sets the job re-check interval in seconds. | 0 | no |\n| penalty | Indicates whether to apply penalty to update_every in case of failures. | yes | no |\n| name | Job name. This value will overwrite the `job_name` value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works. | | no |\n| host | URL or IP where gearman is running. | localhost | no |\n| port | Port of URL or IP where gearman is running. | 4730 | no |\n| tls | Use tls to connect to gearman. | false | no |\n| cert | Provide a certificate file if needed to connect to a TLS gearman instance. | | no |\n| key | Provide a key file if needed to connect to a TLS gearman instance. | | no |\n\n{% /details %}\n#### Examples\n\n##### Local gearman service\n\nA basic host and port gearman configuration for localhost.\n\n```yaml\nlocalhost:\n name: 'local'\n host: 'localhost'\n port: 4730\n\n```\n##### Multi-instance\n\n> **Note**: When you define multiple jobs, their names must be unique.\n\nCollecting metrics from local and remote instances.\n\n\n{% details open=true summary=\"Config\" %}\n```yaml\nlocalhost:\n name: 'local'\n host: 'localhost'\n port: 4730\n\nremote:\n name: 'remote'\n host: '192.0.2.1'\n port: 4730\n\n```\n{% /details %}\n",

18988 - "troubleshooting": "## Troubleshooting\n\n### Debug Mode\n\nTo troubleshoot issues with the `gearman` collector, run the `python.d.plugin` with the debug option enabled. The output\nshould give you clues as to why the collector isn't working.\n\n- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on\n your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`.\n\n ```bash\n cd /usr/libexec/netdata/plugins.d/\n ```\n\n- Switch to the `netdata` user.\n\n ```bash\n sudo -u netdata -s\n ```\n\n- Run the `python.d.plugin` to debug the collector:\n\n ```bash\n ./python.d.plugin gearman debug trace\n ```\n\n### Getting Logs\n\nIf you're encountering problems with the `gearman` collector, follow these steps to retrieve logs and identify potential issues:\n\n- **Run the command** specific to your system (systemd, non-systemd, or Docker container).\n- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.\n\n#### System with systemd\n\nUse the following command to view logs generated since the last Netdata service restart:\n\n```bash\njournalctl _SYSTEMD_INVOCATION_ID=\"$(systemctl show --value --property=InvocationID netdata)\" --namespace=netdata --grep gearman\n```\n\n#### System without systemd\n\nLocate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name:\n\n```bash\ngrep gearman /var/log/netdata/collector.log\n```\n\n**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues.\n\n#### Docker Container\n\nIf your Netdata runs in a Docker container named \"netdata\" (replace if different), use this command:\n\n```bash\ndocker logs netdata 2>&1 | grep gearman\n```\n\n",

18989 - "alerts": "## Alerts\n\n\nThe following alerts are available:\n\n| Alert name | On metric | Description |\n|:------------|:----------|:------------|\n| [ gearman_workers_queued ](https://github.com/netdata/netdata/blob/master/src/health/health.d/gearman.conf) | gearman.single_job | average number of queued jobs over the last 10 minutes |\n",

18990 - "metrics": "## Metrics\n\nMetrics grouped by *scope*.\n\nThe scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.\n\n\n\n### Per Gearman instance\n\nThese metrics refer to the entire monitored application.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.total_jobs | Pending, Running | Jobs |\n\n### Per gearman job\n\nMetrics related to Gearman jobs. Each job produces its own set of the following metrics.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.single_job | Pending, Idle, Runnning | Jobs |\n\n",

18991 - "integration_type": "collector",

18992 - "id": "python.d.plugin-gearman-Gearman",

18993 - "edit_link": "https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/gearman/metadata.yaml",

18994 - "related_resources": ""

18995 - },

18996 {

18997 "meta": {

18998 "plugin_name": "python.d.plugin",

integrations/integrations.json

+36 -36

@@ -4246,6 +4246,42 @@

4246 "edit_link": "https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/modules/freeradius/metadata.yaml",

4247 "related_resources": ""

4248 },

4249 + {

4250 + "meta": {

4251 + "id": "collector-go.d.plugin-gearman",

4252 + "plugin_name": "go.d.plugin",

4253 + "module_name": "gearman",

4254 + "monitored_instance": {

4255 + "name": "Gearman",

4256 + "link": "https://gearman.org/",

4257 + "categories": [

4258 + "data-collection.distributed-computing-systems"

4259 + ],

4260 + "icon_filename": "gearman.png"

4261 + },

4262 + "related_resources": {

4263 + "integrations": {

4264 + "list": []

4265 + }

4266 + },

4267 + "info_provided_to_referring_integrations": {

4268 + "description": ""

4269 + },

4270 + "keywords": [

4271 + "gearman"

4272 + ],

4273 + "most_popular": false

4274 + },

4275 + "overview": "# Gearman\n\nPlugin: go.d.plugin\nModule: gearman\n\n## Overview\n\nMonitors jobs activity, priority and available workers. It collects summary and function-specific statistics.\n\n\nThis collector connects to a Gearman instance via TCP socket and executes the following commands:\n\n- status\n- priority-status\n\n\nThis collector is supported on all platforms.\n\nThis collector supports collecting metrics from multiple instances of this integration, including remote instances.\n\n\n### Default Behavior\n\n#### Auto-Detection\n\nBy default, it detects Gearman instances running on localhost that are listening on port 4730.\n\n\n#### Limits\n\nThe default configuration for this integration does not impose any limits on data collection.\n\n#### Performance Impact\n\nThe default configuration for this integration is not expected to impose a significant performance impact on the system.\n",

4276 + "setup": "## Setup\n\n### Prerequisites\n\nNo action required.\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `go.d/gearman.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config go.d/gearman.conf\n```\n#### Options\n\nThe following options can be defined globally: update_every, autodetection_retry.\n\n\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| update_every | Data collection frequency. | 1 | no |\n| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |\n| address | The IP address and port where the Gearman service listens for connections. | 127.0.0.1:11211 | yes |\n| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |\n\n#### Examples\n\n##### Basic\n\nA basic example configuration.\n\n```yaml\njobs:\n - name: local\n address: 127.0.0.1:4730\n\n```\n##### Multi-instance\n\n> **Note**: When you define multiple jobs, their names must be unique.\n\nCollecting metrics from local and remote instances.\n\n\n```yaml\njobs:\n - name: local\n address: 127.0.0.1:4730\n\n - name: remote\n address: 203.0.113.0:4730\n\n```\n",

4277 + "troubleshooting": "## Troubleshooting\n\n### Debug Mode\n\nTo troubleshoot issues with the `gearman` collector, run the `go.d.plugin` with the debug option enabled. The output\nshould give you clues as to why the collector isn't working.\n\n- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on\n your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`.\n\n ```bash\n cd /usr/libexec/netdata/plugins.d/\n ```\n\n- Switch to the `netdata` user.\n\n ```bash\n sudo -u netdata -s\n ```\n\n- Run the `go.d.plugin` to debug the collector:\n\n ```bash\n ./go.d.plugin -d -m gearman\n ```\n\n### Getting Logs\n\nIf you're encountering problems with the `gearman` collector, follow these steps to retrieve logs and identify potential issues:\n\n- **Run the command** specific to your system (systemd, non-systemd, or Docker container).\n- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.\n\n#### System with systemd\n\nUse the following command to view logs generated since the last Netdata service restart:\n\n```bash\njournalctl _SYSTEMD_INVOCATION_ID=\"$(systemctl show --value --property=InvocationID netdata)\" --namespace=netdata --grep gearman\n```\n\n#### System without systemd\n\nLocate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name:\n\n```bash\ngrep gearman /var/log/netdata/collector.log\n```\n\n**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues.\n\n#### Docker Container\n\nIf your Netdata runs in a Docker container named \"netdata\" (replace if different), use this command:\n\n```bash\ndocker logs netdata 2>&1 | grep gearman\n```\n\n",

4278 + "alerts": "## Alerts\n\nThere are no alerts configured by default for this integration.\n",

4279 + "metrics": "## Metrics\n\nMetrics grouped by *scope*.\n\nThe scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.\n\n\n\n### Per Gearman instance\n\nThese metrics refer to the entire monitored application.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.queued_jobs_activity | running, waiting | jobs |\n| gearman.queued_jobs_priority | high, normal, low | jobs |\n\n### Per Gearman instance\n\nThese metrics refer to the Function (task).\n\nLabels:\n\n| Label | Description |\n|:-----------|:----------------|\n| function_name | Function name. |\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.function_queued_jobs_activity | running, waiting | jobs |\n| gearman.function_queued_jobs_priority | high, normal, low | jobs |\n| gearman.function_workers | available | workers |\n\n",

4280 + "integration_type": "collector",

4281 + "id": "go.d.plugin-gearman-Gearman",

4282 + "edit_link": "https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/modules/gearman/metadata.yaml",

4283 + "related_resources": ""

4284 + },

4285 {

4286 "meta": {

4287 "id": "collector-go.d.plugin-geth",

@@ -18955,42 +18991,6 @@

18991 "edit_link": "https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/exim/metadata.yaml",

18992 "related_resources": ""

18993 },

18958 - {

18959 - "meta": {

18960 - "plugin_name": "python.d.plugin",

18961 - "module_name": "gearman",

18962 - "monitored_instance": {

18963 - "name": "Gearman",

18964 - "link": "http://gearman.org/",

18965 - "categories": [

18966 - "data-collection.distributed-computing-systems"

18967 - ],

18968 - "icon_filename": "gearman.png"

18969 - },

18970 - "related_resources": {

18971 - "integrations": {

18972 - "list": []

18973 - }

18974 - },

18975 - "info_provided_to_referring_integrations": {

18976 - "description": ""

18977 - },

18978 - "keywords": [

18979 - "gearman",

18980 - "gearman job server"

18981 - ],

18982 - "most_popular": false

18983 - },

18984 - "overview": "# Gearman\n\nPlugin: python.d.plugin\nModule: gearman\n\n## Overview\n\nMonitor Gearman metrics for proficient system task distribution. Track job counts, worker statuses, and queue lengths for effective distributed task management.\n\nThis collector connects to a Gearman instance via either TCP or unix socket.\n\nThis collector is supported on all platforms.\n\nThis collector supports collecting metrics from multiple instances of this integration, including remote instances.\n\n\n### Default Behavior\n\n#### Auto-Detection\n\nWhen no configuration file is found, the collector tries to connect to TCP/IP socket: localhost:4730.\n\n#### Limits\n\nThe default configuration for this integration does not impose any limits on data collection.\n\n#### Performance Impact\n\nThe default configuration for this integration is not expected to impose a significant performance impact on the system.\n",

18985 - "setup": "## Setup\n\n### Prerequisites\n\n#### Socket permissions\n\nThe gearman UNIX socket should have read permission for user netdata.\n\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `python.d/gearman.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config python.d/gearman.conf\n```\n#### Options\n\nThere are 2 sections:\n\n* Global variables\n* One or more JOBS that can define multiple different instances to monitor.\n\nThe following options can be defined globally: priority, penalty, autodetection_retry, update_every, but can also be defined per JOB to override the global values.\n\nAdditionally, the following collapsed table contains all the options that can be configured inside a JOB definition.\n\nEvery configuration JOB starts with a `job_name` value which will appear in the dashboard, unless a `name` parameter is specified.\n\n\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| update_every | Sets the default data collection frequency. | 5 | no |\n| priority | Controls the order of charts at the netdata dashboard. | 60000 | no |\n| autodetection_retry | Sets the job re-check interval in seconds. | 0 | no |\n| penalty | Indicates whether to apply penalty to update_every in case of failures. | yes | no |\n| name | Job name. This value will overwrite the `job_name` value. JOBS with the same name are mutually exclusive. Only one of them will be allowed running at any time. This allows autodetection to try several alternatives and pick the one that works. | | no |\n| host | URL or IP where gearman is running. | localhost | no |\n| port | Port of URL or IP where gearman is running. | 4730 | no |\n| tls | Use tls to connect to gearman. | false | no |\n| cert | Provide a certificate file if needed to connect to a TLS gearman instance. | | no |\n| key | Provide a key file if needed to connect to a TLS gearman instance. | | no |\n\n#### Examples\n\n##### Local gearman service\n\nA basic host and port gearman configuration for localhost.\n\n```yaml\nlocalhost:\n name: 'local'\n host: 'localhost'\n port: 4730\n\n```\n##### Multi-instance\n\n> **Note**: When you define multiple jobs, their names must be unique.\n\nCollecting metrics from local and remote instances.\n\n\n```yaml\nlocalhost:\n name: 'local'\n host: 'localhost'\n port: 4730\n\nremote:\n name: 'remote'\n host: '192.0.2.1'\n port: 4730\n\n```\n",

18986 - "troubleshooting": "## Troubleshooting\n\n### Debug Mode\n\nTo troubleshoot issues with the `gearman` collector, run the `python.d.plugin` with the debug option enabled. The output\nshould give you clues as to why the collector isn't working.\n\n- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on\n your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`.\n\n ```bash\n cd /usr/libexec/netdata/plugins.d/\n ```\n\n- Switch to the `netdata` user.\n\n ```bash\n sudo -u netdata -s\n ```\n\n- Run the `python.d.plugin` to debug the collector:\n\n ```bash\n ./python.d.plugin gearman debug trace\n ```\n\n### Getting Logs\n\nIf you're encountering problems with the `gearman` collector, follow these steps to retrieve logs and identify potential issues:\n\n- **Run the command** specific to your system (systemd, non-systemd, or Docker container).\n- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.\n\n#### System with systemd\n\nUse the following command to view logs generated since the last Netdata service restart:\n\n```bash\njournalctl _SYSTEMD_INVOCATION_ID=\"$(systemctl show --value --property=InvocationID netdata)\" --namespace=netdata --grep gearman\n```\n\n#### System without systemd\n\nLocate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name:\n\n```bash\ngrep gearman /var/log/netdata/collector.log\n```\n\n**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues.\n\n#### Docker Container\n\nIf your Netdata runs in a Docker container named \"netdata\" (replace if different), use this command:\n\n```bash\ndocker logs netdata 2>&1 | grep gearman\n```\n\n",

18987 - "alerts": "## Alerts\n\n\nThe following alerts are available:\n\n| Alert name | On metric | Description |\n|:------------|:----------|:------------|\n| [ gearman_workers_queued ](https://github.com/netdata/netdata/blob/master/src/health/health.d/gearman.conf) | gearman.single_job | average number of queued jobs over the last 10 minutes |\n",

18988 - "metrics": "## Metrics\n\nMetrics grouped by *scope*.\n\nThe scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.\n\n\n\n### Per Gearman instance\n\nThese metrics refer to the entire monitored application.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.total_jobs | Pending, Running | Jobs |\n\n### Per gearman job\n\nMetrics related to Gearman jobs. Each job produces its own set of the following metrics.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit |\n|:------|:----------|:----|\n| gearman.single_job | Pending, Idle, Runnning | Jobs |\n\n",

18989 - "integration_type": "collector",

18990 - "id": "python.d.plugin-gearman-Gearman",

18991 - "edit_link": "https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/gearman/metadata.yaml",

18992 - "related_resources": ""

18993 - },

18994 {

18995 "meta": {

18996 "plugin_name": "python.d.plugin",

src/collectors/COLLECTORS.md

+1 -1

@@ -283,7 +283,7 @@ If you don't see the app/service you'd like to monitor in this list:

283

284 - [BOINC](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/boinc/integrations/boinc.md)

285

286 -- [Gearman](https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/gearman/integrations/gearman.md)

286 +- [Gearman](https://github.com/netdata/netdata/blob/master/src/go/plugin/go.d/modules/gearman/integrations/gearman.md)

287

288 ### DNS and DHCP Servers

289

src/go/plugin/go.d/modules/gearman/README.md new

@@ -0,0 +1 @@

1 +integrations/gearman.md

\ No newline at end of file

src/go/plugin/go.d/modules/gearman/integrations/gearman.md new

+233

@@ -0,0 +1,233 @@

1 +<!--startmeta

2 +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/gearman/README.md"

3 +meta_yaml: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/modules/gearman/metadata.yaml"

4 +sidebar_label: "Gearman"

5 +learn_status: "Published"

6 +learn_rel_path: "Collecting Metrics/Distributed Computing Systems"

7 +most_popular: False

8 +message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE"

9 +endmeta-->

10 +

11 +# Gearman

12 +

13 +

14 +<img src="https://netdata.cloud/img/gearman.png" width="150"/>

15 +

16 +

17 +Plugin: go.d.plugin

18 +Module: gearman

19 +

20 +<img src="https://img.shields.io/badge/maintained%20by-Netdata-%2300ab44" />

21 +

22 +## Overview

23 +

24 +Monitors jobs activity, priority and available workers. It collects summary and function-specific statistics.

25 +

26 +

27 +This collector connects to a Gearman instance via TCP socket and executes the following commands:

28 +

29 +- status

30 +- priority-status

31 +

32 +

33 +This collector is supported on all platforms.

34 +

35 +This collector supports collecting metrics from multiple instances of this integration, including remote instances.

36 +

37 +

38 +### Default Behavior

39 +

40 +#### Auto-Detection

41 +

42 +By default, it detects Gearman instances running on localhost that are listening on port 4730.

43 +

44 +

45 +#### Limits

46 +

47 +The default configuration for this integration does not impose any limits on data collection.

48 +

49 +#### Performance Impact

50 +

51 +The default configuration for this integration is not expected to impose a significant performance impact on the system.

52 +

53 +

54 +## Metrics

55 +

56 +Metrics grouped by *scope*.

57 +

58 +The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels.

59 +

60 +

61 +

62 +### Per Gearman instance

63 +

64 +These metrics refer to the entire monitored application.

65 +

66 +This scope has no labels.

67 +

68 +Metrics:

69 +

70 +| Metric | Dimensions | Unit |

71 +|:------|:----------|:----|

72 +| gearman.queued_jobs_activity | running, waiting | jobs |

73 +| gearman.queued_jobs_priority | high, normal, low | jobs |

74 +

75 +### Per Gearman instance

76 +

77 +These metrics refer to the Function (task).

78 +

79 +Labels:

80 +

81 +| Label | Description |

82 +|:-----------|:----------------|

83 +| function_name | Function name. |

84 +

85 +Metrics:

86 +

87 +| Metric | Dimensions | Unit |

88 +|:------|:----------|:----|

89 +| gearman.function_queued_jobs_activity | running, waiting | jobs |

90 +| gearman.function_queued_jobs_priority | high, normal, low | jobs |

91 +| gearman.function_workers | available | workers |

92 +

93 +

94 +

95 +## Alerts

96 +

97 +There are no alerts configured by default for this integration.

98 +

99 +

100 +## Setup

101 +

102 +### Prerequisites

103 +

104 +No action required.

105 +

106 +### Configuration

107 +

108 +#### File

109 +

110 +The configuration file name for this integration is `go.d/gearman.conf`.

111 +

112 +

113 +You can edit the configuration file using the `edit-config` script from the

114 +Netdata [config directory](/docs/netdata-agent/configuration/README.md#the-netdata-config-directory).

115 +

116 +```bash

117 +cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata

118 +sudo ./edit-config go.d/gearman.conf

119 +```

120 +#### Options

121 +

122 +The following options can be defined globally: update_every, autodetection_retry.

123 +

124 +

125 +<details open><summary>Config options</summary>

126 +

128 +|:----|:-----------|:-------|:--------:|

129 +| update_every | Data collection frequency. | 1 | no |

130 +| autodetection_retry | Recheck interval in seconds. Zero means no recheck will be scheduled. | 0 | no |

131 +| address | The IP address and port where the Gearman service listens for connections. | 127.0.0.1:11211 | yes |

132 +| timeout | Connection, read, and write timeout duration in seconds. The timeout includes name resolution. | 1 | no |

133 +

134 +</details>

135 +

136 +#### Examples

137 +

138 +##### Basic

139 +

140 +A basic example configuration.

141 +

142 +<details open><summary>Config</summary>

143 +

144 +```yaml

145 +jobs:

146 + - name: local

147 + address: 127.0.0.1:4730

148 +

149 +```

150 +</details>

151 +

152 +##### Multi-instance

153 +

154 +> **Note**: When you define multiple jobs, their names must be unique.

155 +

156 +Collecting metrics from local and remote instances.

157 +

158 +

159 +<details open><summary>Config</summary>

160 +

161 +```yaml

162 +jobs:

163 + - name: local

164 + address: 127.0.0.1:4730

165 +

166 + - name: remote

167 + address: 203.0.113.0:4730

168 +

169 +```

170 +</details>

171 +

172 +

173 +

174 +## Troubleshooting

175 +

176 +### Debug Mode

177 +

178 +To troubleshoot issues with the `gearman` collector, run the `go.d.plugin` with the debug option enabled. The output

179 +should give you clues as to why the collector isn't working.

180 +

181 +- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on

182 + your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`.

183 +

184 + ```bash

185 + cd /usr/libexec/netdata/plugins.d/

186 + ```

187 +

188 +- Switch to the `netdata` user.

189 +

190 + ```bash

191 + sudo -u netdata -s

192 + ```

193 +

194 +- Run the `go.d.plugin` to debug the collector:

195 +

196 + ```bash

197 + ./go.d.plugin -d -m gearman

198 + ```

199 +

200 +### Getting Logs

201 +

202 +If you're encountering problems with the `gearman` collector, follow these steps to retrieve logs and identify potential issues:

203 +

204 +- **Run the command** specific to your system (systemd, non-systemd, or Docker container).

205 +- **Examine the output** for any warnings or error messages that might indicate issues. These messages should provide clues about the root cause of the problem.

206 +

207 +#### System with systemd

208 +

209 +Use the following command to view logs generated since the last Netdata service restart:

210 +

211 +```bash

212 +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep gearman

213 +```

214 +

215 +#### System without systemd

216 +

217 +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name:

218 +

219 +```bash

220 +grep gearman /var/log/netdata/collector.log

221 +```

222 +

223 +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues.

224 +

225 +#### Docker Container

226 +

227 +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command:

228 +

229 +```bash

230 +docker logs netdata 2>&1 | grep gearman

231 +```

232 +

233 +