Regenerate integrations.js (#17603)

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

3 files changed, 7 insertions, 82 deletions

diff --git a/integrations/cloud-authentication/integrations/oidc.md b/integrations/cloud-authentication/integrations/oidc.md
index 3d3653579c..4fcb92c6b9 100644
--- a/integrations/cloud-authentication/integrations/oidc.md
+++ b/integrations/cloud-authentication/integrations/oidc.md
@@ -30,11 +30,12 @@ Integrate your organization's Authorization Servers with Netdata to better manag
 Your server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).
 In order to integrate your Authorization Server with Netdata the creation of a client is required. Clients are applications and services that can request authentication of a user.
 The access settings for your client are the following:
-| field                    | value                                                                                                                                                                                        |
-| :--                      | :--                                                                                                                                                                                          |
-| Root URL                 | https://app.netdata.cloud/                                                                                                                                                                   |
+
+| field                    | value                                                 |
+| :--                      | :--                                                   |
+| Root URL                 | https://app.netdata.cloud/                            |
 | Home/Initiate login URL  | https://app.netdata.cloud/api/v2/auth/account/auth-server?iss={your-server-issuer-url}&redirect_uri=https://app.netdata.cloud/sign-in&register_uri=https://app.netdata.cloud/sign-up/verify  |
-| Redirect URL             | https://app.netdata.cloud/api/v2/auth/account/auth-server/callback                                                                                                                           |
+| Redirect URL             | https://app.netdata.cloud/api/v2/auth/account/auth-server/callback  |
 
 ### Netdata Configuration Steps
 1. Click on the Space settings cog (located above your profile icon)
diff --git a/integrations/integrations.js b/integrations/integrations.js
index 9b32d1cbed..fa40acf357 100644
--- a/integrations/integrations.js
+++ b/integrations/integrations.js
@@ -19262,44 +19262,6 @@ export const integrations = [
     {
         "meta": {
             "plugin_name": "python.d.plugin",
-            "module_name": "smartd_log",
-            "monitored_instance": {
-                "name": "S.M.A.R.T.",
-                "link": "https://linux.die.net/man/8/smartd",
-                "categories": [
-                    "data-collection.hardware-devices-and-sensors"
-                ],
-                "icon_filename": "smart.png"
-            },
-            "related_resources": {
-                "integrations": {
-                    "list": []
-                }
-            },
-            "info_provided_to_referring_integrations": {
-                "description": ""
-            },
-            "keywords": [
-                "smart",
-                "S.M.A.R.T.",
-                "SCSI devices",
-                "ATA devices"
-            ],
-            "most_popular": false
-        },
-        "overview": "# S.M.A.R.T.\n\nPlugin: python.d.plugin\nModule: smartd_log\n\n## Overview\n\nThis collector monitors HDD/SSD S.M.A.R.T. metrics about drive health and performance.\n\n\nIt reads `smartd` log files to collect the metrics.\n\n\nThis collector is supported on all platforms.\n\nThis collector only supports collecting metrics from a single instance of this integration.\n\n\n### Default Behavior\n\n#### Auto-Detection\n\nUpon satisfying the prerequisites, the collector will auto-detect metrics if written in either `/var/log/smartd/` or `/var/lib/smartmontools/`.\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",
-        "setup": "## Setup\n\n### Prerequisites\n\n#### Configure `smartd` to write attribute information to files.\n\n`smartd` must be running with `-A` option to write `smartd` attribute information to files.\n\nFor this you need to set `smartd_opts` (or `SMARTD_ARGS`, check _smartd.service_ content) in `/etc/default/smartmontools`:\n\n```\n# dump smartd attrs info every 600 seconds\nsmartd_opts=\"-A /var/log/smartd/ -i 600\"\n```\n\nYou may need to create the smartd directory before smartd will write to it: \n\n```sh\nmkdir -p /var/log/smartd\n```\n\nOtherwise, all the smartd `.csv` files may get written to `/var/lib/smartmontools` (default location). See also <https://linux.die.net/man/8/smartd> for more info on the `-A --attributelog=PREFIX` command.\n\n`smartd` appends logs at every run. It's strongly recommended to use `logrotate` for smartd files.\n\n\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `python.d/smartd_log.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config python.d/smartd_log.conf\n```\n#### Options\n\nThis particular collector does not need further configuration to work if permissions are satisfied, but you can always customize it's data collection behavior.\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 summary=\"Config options\" %}\n| Name | Description | Default | Required |\n|:----|:-----------|:-------|:--------:|\n| log_path | path to smartd log files. | /var/log/smartd | yes |\n| exclude_disks | Space-separated patterns. If the pattern is in the drive name, the module will not collect data for it. |  | no |\n| age | Time in minutes since the last dump to file. | 30 | no |\n| update_every | Sets the default data collection frequency. | 1 | 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\n{% /details %}\n#### Examples\n\n##### Basic\n\nA basic configuration example.\n\n```yaml\ncustom:\n  name: smartd_log\n  log_path: '/var/log/smartd/'\n\n```\n",
-        "troubleshooting": "## Troubleshooting\n\n### Debug Mode\n\nTo troubleshoot issues with the `smartd_log` 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 smartd_log debug trace\n  ```\n\n",
-        "alerts": "## Alerts\n\nThere are no alerts configured by default for this integration.\n",
-        "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\nThe metrics listed below are split in terms of availability on device type, SCSI or ATA.\n\n### Per S.M.A.R.T. instance\n\nThese metrics refer to the entire monitored application.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit | SCSI | ATA |\n|:------|:----------|:----|:---:|:---:|\n| smartd_log.read_error_rate | a dimension per device | value |   | \u2022 |\n| smartd_log.seek_error_rate | a dimension per device | value |   | \u2022 |\n| smartd_log.soft_read_error_rate | a dimension per device | errors |   | \u2022 |\n| smartd_log.write_error_rate | a dimension per device | value |   | \u2022 |\n| smartd_log.read_total_err_corrected | a dimension per device | errors | \u2022 |   |\n| smartd_log.read_total_unc_errors | a dimension per device | errors | \u2022 |   |\n| smartd_log.write_total_err_corrected | a dimension per device | errors | \u2022 |   |\n| smartd_log.write_total_unc_errors | a dimension per device | errors | \u2022 |   |\n| smartd_log.verify_total_err_corrected | a dimension per device | errors | \u2022 |   |\n| smartd_log.verify_total_unc_errors | a dimension per device | errors | \u2022 |   |\n| smartd_log.sata_interface_downshift | a dimension per device | events |   | \u2022 |\n| smartd_log.udma_crc_error_count | a dimension per device | errors |   | \u2022 |\n| smartd_log.throughput_performance | a dimension per device | value |   | \u2022 |\n| smartd_log.seek_time_performance | a dimension per device | value |   | \u2022 |\n| smartd_log.start_stop_count | a dimension per device | events |   | \u2022 |\n| smartd_log.power_on_hours_count | a dimension per device | hours |   | \u2022 |\n| smartd_log.power_cycle_count | a dimension per device | events |   | \u2022 |\n| smartd_log.unexpected_power_loss | a dimension per device | events |   | \u2022 |\n| smartd_log.spin_up_time | a dimension per device | ms |   | \u2022 |\n| smartd_log.spin_up_retries | a dimension per device | retries |   | \u2022 |\n| smartd_log.calibration_retries | a dimension per device | retries |   | \u2022 |\n| smartd_log.airflow_temperature_celsius | a dimension per device | celsius |   | \u2022 |\n| smartd_log.temperature_celsius | a dimension per device | celsius | \u2022 | \u2022 |\n| smartd_log.reallocated_sectors_count | a dimension per device | sectors |   | \u2022 |\n| smartd_log.reserved_block_count | a dimension per device | percentage |   | \u2022 |\n| smartd_log.program_fail_count | a dimension per device | errors |   | \u2022 |\n| smartd_log.erase_fail_count | a dimension per device | failures |   | \u2022 |\n| smartd_log.wear_leveller_worst_case_erase_count | a dimension per device | erases |   | \u2022 |\n| smartd_log.unused_reserved_nand_blocks | a dimension per device | blocks |   | \u2022 |\n| smartd_log.reallocation_event_count | a dimension per device | events |   | \u2022 |\n| smartd_log.current_pending_sector_count | a dimension per device | sectors |   | \u2022 |\n| smartd_log.offline_uncorrectable_sector_count | a dimension per device | sectors |   | \u2022 |\n| smartd_log.percent_lifetime_used | a dimension per device | percentage |   | \u2022 |\n| smartd_log.media_wearout_indicator | a dimension per device | percentage |   | \u2022 |\n| smartd_log.nand_writes_1gib | a dimension per device | GiB |   | \u2022 |\n\n",
-        "integration_type": "collector",
-        "id": "python.d.plugin-smartd_log-S.M.A.R.T.",
-        "edit_link": "https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/smartd_log/metadata.yaml",
-        "related_resources": ""
-    },
-    {
-        "meta": {
-            "plugin_name": "python.d.plugin",
             "module_name": "spigotmc",
             "monitored_instance": {
                 "name": "SpigotMC",
@@ -22318,7 +22280,7 @@ export const integrations = [
             "oidc"
         ],
         "overview": "# OIDC\n\nIntegrate your organization's Authorization Servers with Netdata to better manage your team's access controls to Netdata Cloud.\n",
-        "setup": "## Setup\n\n### Prerequisites\n- Authorization Server with OIDC protocol supported\n- A Netdata Cloud account\n- Access to the Space as an **Admin**\n- Space needs to be on a paid plan\n\n### Setting up Authorization Server\nYour server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).\nIn order to integrate your Authorization Server with Netdata the creation of a client is required. Clients are applications and services that can request authentication of a user.\nThe access settings for your client are the following:\n| field                    | value                                                                                                                                                                                        |\n| :--                      | :--                                                                                                                                                                                          |\n| Root URL                 | https://app.netdata.cloud/                                                                                                                                                                   |\n| Home/Initiate login URL  | https://app.netdata.cloud/api/v2/auth/account/auth-server?iss={your-server-issuer-url}&redirect_uri=https://app.netdata.cloud/sign-in&register_uri=https://app.netdata.cloud/sign-up/verify  |\n| Redirect URL             | https://app.netdata.cloud/api/v2/auth/account/auth-server/callback                                                                                                                           |\n\n### Netdata Configuration Steps\n1. Click on the Space settings cog (located above your profile icon)\n2. Click on the **Authentication** tab\n3. On the OIDC card, click on **Configure**\n4. Fill in the required credentials:\n    - **Issuer URL** the Authorization Server Issuer URL, e.g. `https://my-auth-server.com/`\n    - **Client ID** the Client ID from the created client\n    - **Client Secret** the Client Secret from the created client\n    - **Authorization URL** the Authorization Server authorization URL, e.g. `https://my-auth-server.com/openid-connect/auth`\n    - **Token URL** the Authorization Server token URL, e.g. `https://my-auth-server.com/openid-connect/token`\n    - **User URL** the Authorization Server user info URL, e.g. `https://my-auth-server.com/openid-connect/userinfo`\n\n### Supported features\n* SP-initiated SSO (Single Sign-On)\n* IdP-initiated SSO\n\n### SP-initiated SSO\n\nIf you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/enterprise-sso-authentication.md#from-netdata-sign-up-page).\n\n\n### Reference\nhttps://openid.net/developers/how-connect-works/\n\n",
+        "setup": "## Setup\n\n### Prerequisites\n- Authorization Server with OIDC protocol supported\n- A Netdata Cloud account\n- Access to the Space as an **Admin**\n- Space needs to be on a paid plan\n\n### Setting up Authorization Server\nYour server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).\nIn order to integrate your Authorization Server with Netdata the creation of a client is required. Clients are applications and services that can request authentication of a user.\nThe access settings for your client are the following:\n\n| field                    | value                                                 |\n| :--                      | :--                                                   |\n| Root URL                 | https://app.netdata.cloud/                            |\n| Home/Initiate login URL  | https://app.netdata.cloud/api/v2/auth/account/auth-server?iss={your-server-issuer-url}&redirect_uri=https://app.netdata.cloud/sign-in&register_uri=https://app.netdata.cloud/sign-up/verify  |\n| Redirect URL             | https://app.netdata.cloud/api/v2/auth/account/auth-server/callback  |\n\n### Netdata Configuration Steps\n1. Click on the Space settings cog (located above your profile icon)\n2. Click on the **Authentication** tab\n3. On the OIDC card, click on **Configure**\n4. Fill in the required credentials:\n    - **Issuer URL** the Authorization Server Issuer URL, e.g. `https://my-auth-server.com/`\n    - **Client ID** the Client ID from the created client\n    - **Client Secret** the Client Secret from the created client\n    - **Authorization URL** the Authorization Server authorization URL, e.g. `https://my-auth-server.com/openid-connect/auth`\n    - **Token URL** the Authorization Server token URL, e.g. `https://my-auth-server.com/openid-connect/token`\n    - **User URL** the Authorization Server user info URL, e.g. `https://my-auth-server.com/openid-connect/userinfo`\n\n### Supported features\n* SP-initiated SSO (Single Sign-On)\n* IdP-initiated SSO\n\n### SP-initiated SSO\n\nIf you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/enterprise-sso-authentication.md#from-netdata-sign-up-page).\n\n\n### Reference\nhttps://openid.net/developers/how-connect-works/\n\n",
         "integration_type": "authentication",
         "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-authentication/metadata.yaml",
         "troubleshooting": ""
diff --git a/integrations/integrations.json b/integrations/integrations.json
index 2edb415bd0..d1eab26cd4 100644
--- a/integrations/integrations.json
+++ b/integrations/integrations.json
@@ -19260,44 +19260,6 @@
         {
             "meta": {
                 "plugin_name": "python.d.plugin",
-                "module_name": "smartd_log",
-                "monitored_instance": {
-                    "name": "S.M.A.R.T.",
-                    "link": "https://linux.die.net/man/8/smartd",
-                    "categories": [
-                        "data-collection.hardware-devices-and-sensors"
-                    ],
-                    "icon_filename": "smart.png"
-                },
-                "related_resources": {
-                    "integrations": {
-                        "list": []
-                    }
-                },
-                "info_provided_to_referring_integrations": {
-                    "description": ""
-                },
-                "keywords": [
-                    "smart",
-                    "S.M.A.R.T.",
-                    "SCSI devices",
-                    "ATA devices"
-                ],
-                "most_popular": false
-            },
-            "overview": "# S.M.A.R.T.\n\nPlugin: python.d.plugin\nModule: smartd_log\n\n## Overview\n\nThis collector monitors HDD/SSD S.M.A.R.T. metrics about drive health and performance.\n\n\nIt reads `smartd` log files to collect the metrics.\n\n\nThis collector is supported on all platforms.\n\nThis collector only supports collecting metrics from a single instance of this integration.\n\n\n### Default Behavior\n\n#### Auto-Detection\n\nUpon satisfying the prerequisites, the collector will auto-detect metrics if written in either `/var/log/smartd/` or `/var/lib/smartmontools/`.\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",
-            "setup": "## Setup\n\n### Prerequisites\n\n#### Configure `smartd` to write attribute information to files.\n\n`smartd` must be running with `-A` option to write `smartd` attribute information to files.\n\nFor this you need to set `smartd_opts` (or `SMARTD_ARGS`, check _smartd.service_ content) in `/etc/default/smartmontools`:\n\n```\n# dump smartd attrs info every 600 seconds\nsmartd_opts=\"-A /var/log/smartd/ -i 600\"\n```\n\nYou may need to create the smartd directory before smartd will write to it: \n\n```sh\nmkdir -p /var/log/smartd\n```\n\nOtherwise, all the smartd `.csv` files may get written to `/var/lib/smartmontools` (default location). See also <https://linux.die.net/man/8/smartd> for more info on the `-A --attributelog=PREFIX` command.\n\n`smartd` appends logs at every run. It's strongly recommended to use `logrotate` for smartd files.\n\n\n\n### Configuration\n\n#### File\n\nThe configuration file name for this integration is `python.d/smartd_log.conf`.\n\n\nYou can edit the configuration file using the `edit-config` script from the\nNetdata [config directory](https://github.com/netdata/netdata/blob/master/docs/netdata-agent/configuration.md#the-netdata-config-directory).\n\n```bash\ncd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata\nsudo ./edit-config python.d/smartd_log.conf\n```\n#### Options\n\nThis particular collector does not need further configuration to work if permissions are satisfied, but you can always customize it's data collection behavior.\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| log_path | path to smartd log files. | /var/log/smartd | yes |\n| exclude_disks | Space-separated patterns. If the pattern is in the drive name, the module will not collect data for it. |  | no |\n| age | Time in minutes since the last dump to file. | 30 | no |\n| update_every | Sets the default data collection frequency. | 1 | 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\n#### Examples\n\n##### Basic\n\nA basic configuration example.\n\n```yaml\ncustom:\n  name: smartd_log\n  log_path: '/var/log/smartd/'\n\n```\n",
-            "troubleshooting": "## Troubleshooting\n\n### Debug Mode\n\nTo troubleshoot issues with the `smartd_log` 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 smartd_log debug trace\n  ```\n\n",
-            "alerts": "## Alerts\n\nThere are no alerts configured by default for this integration.\n",
-            "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\nThe metrics listed below are split in terms of availability on device type, SCSI or ATA.\n\n### Per S.M.A.R.T. instance\n\nThese metrics refer to the entire monitored application.\n\nThis scope has no labels.\n\nMetrics:\n\n| Metric | Dimensions | Unit | SCSI | ATA |\n|:------|:----------|:----|:---:|:---:|\n| smartd_log.read_error_rate | a dimension per device | value |   | \u2022 |\n| smartd_log.seek_error_rate | a dimension per device | value |   | \u2022 |\n| smartd_log.soft_read_error_rate | a dimension per device | errors |   | \u2022 |\n| smartd_log.write_error_rate | a dimension per device | value |   | \u2022 |\n| smartd_log.read_total_err_corrected | a dimension per device | errors | \u2022 |   |\n| smartd_log.read_total_unc_errors | a dimension per device | errors | \u2022 |   |\n| smartd_log.write_total_err_corrected | a dimension per device | errors | \u2022 |   |\n| smartd_log.write_total_unc_errors | a dimension per device | errors | \u2022 |   |\n| smartd_log.verify_total_err_corrected | a dimension per device | errors | \u2022 |   |\n| smartd_log.verify_total_unc_errors | a dimension per device | errors | \u2022 |   |\n| smartd_log.sata_interface_downshift | a dimension per device | events |   | \u2022 |\n| smartd_log.udma_crc_error_count | a dimension per device | errors |   | \u2022 |\n| smartd_log.throughput_performance | a dimension per device | value |   | \u2022 |\n| smartd_log.seek_time_performance | a dimension per device | value |   | \u2022 |\n| smartd_log.start_stop_count | a dimension per device | events |   | \u2022 |\n| smartd_log.power_on_hours_count | a dimension per device | hours |   | \u2022 |\n| smartd_log.power_cycle_count | a dimension per device | events |   | \u2022 |\n| smartd_log.unexpected_power_loss | a dimension per device | events |   | \u2022 |\n| smartd_log.spin_up_time | a dimension per device | ms |   | \u2022 |\n| smartd_log.spin_up_retries | a dimension per device | retries |   | \u2022 |\n| smartd_log.calibration_retries | a dimension per device | retries |   | \u2022 |\n| smartd_log.airflow_temperature_celsius | a dimension per device | celsius |   | \u2022 |\n| smartd_log.temperature_celsius | a dimension per device | celsius | \u2022 | \u2022 |\n| smartd_log.reallocated_sectors_count | a dimension per device | sectors |   | \u2022 |\n| smartd_log.reserved_block_count | a dimension per device | percentage |   | \u2022 |\n| smartd_log.program_fail_count | a dimension per device | errors |   | \u2022 |\n| smartd_log.erase_fail_count | a dimension per device | failures |   | \u2022 |\n| smartd_log.wear_leveller_worst_case_erase_count | a dimension per device | erases |   | \u2022 |\n| smartd_log.unused_reserved_nand_blocks | a dimension per device | blocks |   | \u2022 |\n| smartd_log.reallocation_event_count | a dimension per device | events |   | \u2022 |\n| smartd_log.current_pending_sector_count | a dimension per device | sectors |   | \u2022 |\n| smartd_log.offline_uncorrectable_sector_count | a dimension per device | sectors |   | \u2022 |\n| smartd_log.percent_lifetime_used | a dimension per device | percentage |   | \u2022 |\n| smartd_log.media_wearout_indicator | a dimension per device | percentage |   | \u2022 |\n| smartd_log.nand_writes_1gib | a dimension per device | GiB |   | \u2022 |\n\n",
-            "integration_type": "collector",
-            "id": "python.d.plugin-smartd_log-S.M.A.R.T.",
-            "edit_link": "https://github.com/netdata/netdata/blob/master/src/collectors/python.d.plugin/smartd_log/metadata.yaml",
-            "related_resources": ""
-        },
-        {
-            "meta": {
-                "plugin_name": "python.d.plugin",
                 "module_name": "spigotmc",
                 "monitored_instance": {
                     "name": "SpigotMC",
@@ -22316,7 +22278,7 @@
                 "oidc"
             ],
             "overview": "# OIDC\n\nIntegrate your organization's Authorization Servers with Netdata to better manage your team's access controls to Netdata Cloud.\n",
-            "setup": "## Setup\n\n### Prerequisites\n- Authorization Server with OIDC protocol supported\n- A Netdata Cloud account\n- Access to the Space as an **Admin**\n- Space needs to be on a paid plan\n\n### Setting up Authorization Server\nYour server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).\nIn order to integrate your Authorization Server with Netdata the creation of a client is required. Clients are applications and services that can request authentication of a user.\nThe access settings for your client are the following:\n| field                    | value                                                                                                                                                                                        |\n| :--                      | :--                                                                                                                                                                                          |\n| Root URL                 | https://app.netdata.cloud/                                                                                                                                                                   |\n| Home/Initiate login URL  | https://app.netdata.cloud/api/v2/auth/account/auth-server?iss={your-server-issuer-url}&redirect_uri=https://app.netdata.cloud/sign-in&register_uri=https://app.netdata.cloud/sign-up/verify  |\n| Redirect URL             | https://app.netdata.cloud/api/v2/auth/account/auth-server/callback                                                                                                                           |\n\n### Netdata Configuration Steps\n1. Click on the Space settings cog (located above your profile icon)\n2. Click on the **Authentication** tab\n3. On the OIDC card, click on **Configure**\n4. Fill in the required credentials:\n    - **Issuer URL** the Authorization Server Issuer URL, e.g. `https://my-auth-server.com/`\n    - **Client ID** the Client ID from the created client\n    - **Client Secret** the Client Secret from the created client\n    - **Authorization URL** the Authorization Server authorization URL, e.g. `https://my-auth-server.com/openid-connect/auth`\n    - **Token URL** the Authorization Server token URL, e.g. `https://my-auth-server.com/openid-connect/token`\n    - **User URL** the Authorization Server user info URL, e.g. `https://my-auth-server.com/openid-connect/userinfo`\n\n### Supported features\n* SP-initiated SSO (Single Sign-On)\n* IdP-initiated SSO\n\n### SP-initiated SSO\n\nIf you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/enterprise-sso-authentication.md#from-netdata-sign-up-page).\n\n\n### Reference\nhttps://openid.net/developers/how-connect-works/\n\n",
+            "setup": "## Setup\n\n### Prerequisites\n- Authorization Server with OIDC protocol supported\n- A Netdata Cloud account\n- Access to the Space as an **Admin**\n- Space needs to be on a paid plan\n\n### Setting up Authorization Server\nYour server should follow the [full specification for OIDC](https://openid.net/specs/openid-connect-core-1_0.html).\nIn order to integrate your Authorization Server with Netdata the creation of a client is required. Clients are applications and services that can request authentication of a user.\nThe access settings for your client are the following:\n\n| field                    | value                                                 |\n| :--                      | :--                                                   |\n| Root URL                 | https://app.netdata.cloud/                            |\n| Home/Initiate login URL  | https://app.netdata.cloud/api/v2/auth/account/auth-server?iss={your-server-issuer-url}&redirect_uri=https://app.netdata.cloud/sign-in&register_uri=https://app.netdata.cloud/sign-up/verify  |\n| Redirect URL             | https://app.netdata.cloud/api/v2/auth/account/auth-server/callback  |\n\n### Netdata Configuration Steps\n1. Click on the Space settings cog (located above your profile icon)\n2. Click on the **Authentication** tab\n3. On the OIDC card, click on **Configure**\n4. Fill in the required credentials:\n    - **Issuer URL** the Authorization Server Issuer URL, e.g. `https://my-auth-server.com/`\n    - **Client ID** the Client ID from the created client\n    - **Client Secret** the Client Secret from the created client\n    - **Authorization URL** the Authorization Server authorization URL, e.g. `https://my-auth-server.com/openid-connect/auth`\n    - **Token URL** the Authorization Server token URL, e.g. `https://my-auth-server.com/openid-connect/token`\n    - **User URL** the Authorization Server user info URL, e.g. `https://my-auth-server.com/openid-connect/userinfo`\n\n### Supported features\n* SP-initiated SSO (Single Sign-On)\n* IdP-initiated SSO\n\n### SP-initiated SSO\n\nIf you start your authentication flow from Netdata sign-in page please check [these steps](https://github.com/netdata/netdata/blob/master/docs/netdata-cloud/enterprise-sso-authentication.md#from-netdata-sign-up-page).\n\n\n### Reference\nhttps://openid.net/developers/how-connect-works/\n\n",
             "integration_type": "authentication",
             "edit_link": "https://github.com/netdata/netdata/blob/master/integrations/cloud-authentication/metadata.yaml",
             "troubleshooting": ""