diff --git a/docs/Collecting Metrics/Collectors/Applications/RUM Receiver.mdx b/docs/Collecting Metrics/Collectors/Applications/RUM Receiver.mdx index f400287cc..183ddf1fd 100644 --- a/docs/Collecting Metrics/Collectors/Applications/RUM Receiver.mdx +++ b/docs/Collecting Metrics/Collectors/Applications/RUM Receiver.mdx @@ -61,7 +61,7 @@ Resource usage depends on accepted browser traffic and the configured measuremen #### Install the DEM plugin -DEM is experimental and opt-in. Build Netdata with `-DENABLE_PLUGIN_DEM=ON`, or use `--enable-plugin-dem` with the source installer. Install the resulting DEM plugin package. +Linux builds include DEM by default. Native installations include the `netdata-plugin-dem` package. RUM does not require the optional browser runtime. #### Expose the receiver diff --git a/docs/Collecting Metrics/Collectors/Applications/Real User Monitoring.mdx b/docs/Collecting Metrics/Collectors/Applications/Real User Monitoring.mdx index 7adf11b41..82dd8b50a 100644 --- a/docs/Collecting Metrics/Collectors/Applications/Real User Monitoring.mdx +++ b/docs/Collecting Metrics/Collectors/Applications/Real User Monitoring.mdx @@ -77,7 +77,7 @@ Resource usage depends on accepted browser traffic and the configured measuremen #### Install the DEM plugin -DEM is experimental and opt-in. Build Netdata with `-DENABLE_PLUGIN_DEM=ON`, or use `--enable-plugin-dem` with the source installer. Install the resulting DEM plugin package. +Linux builds include DEM by default. Native installations include the `netdata-plugin-dem` package. RUM does not require the optional browser runtime. #### Configure the receiver and site diff --git a/docs/Collecting Metrics/Collectors/Hardware and Sensors/IPMI Go collector.mdx b/docs/Collecting Metrics/Collectors/Hardware and Sensors/IPMI Go collector.mdx index 174305f1c..11e883b66 100644 --- a/docs/Collecting Metrics/Collectors/Hardware and Sensors/IPMI Go collector.mdx +++ b/docs/Collecting Metrics/Collectors/Hardware and Sensors/IPMI Go collector.mdx @@ -29,7 +29,7 @@ Module: ipmi Monitor hardware sensor readings, sensor health and System Event Log entries through IPMI. -Queries a local Linux OpenIPMI device or a remote BMC over IPMI 1.5 LAN or IPMI 2.0 LAN+ using the configured account. The collector reads sensors and SEL metadata; it does not change BMC configuration or clear the event log. +Queries a local Linux OpenIPMI device or a remote BMC over IPMI 1.5 LAN or IPMI 2.0 LAN+ using the configured account. The collector reads sensors and the System Event Log (SEL); it does not change BMC configuration or clear the event log. This collector is only supported on the following platforms: @@ -59,7 +59,7 @@ This plugin requires Linux. Keep FreeIPMI for legacy direct drivers, bridged sen #### Performance Impact -IPMI command latency grows with sensor count. Increase update_every when a complete sensor scan takes longer than the configured interval. +IPMI command latency grows with sensor count. Increase update_every when a complete sensor scan takes longer than the configured interval. Sensor thresholds are read with the SDR inventory, about every five minutes, at most one command per threshold sensor. With collect_sel enabled, the first collections after a start also read the existing System Event Log, for up to two seconds each (a quarter of update_every when shorter), until all records are read. Later collections read only new records, or the whole log again after the BMC clears or rewrites it. ## Setup @@ -98,7 +98,7 @@ Options apply to each IPMI job. Configure one local device or remote BMC per job | | privilege_level | Session privilege requested from the BMC. User privilege is sufficient for standard sensor and SEL commands. | user | no | | **Collection** | update_every | Data collection frequency in seconds. | 10 | no | | | timeout | Timeout for session setup and for each IPMI command. | 5s | no | -| | collect_sel | Collect the System Event Log entry count. | yes | no | +| | collect_sel | Read the System Event Log: the entry count and new records charts, and the ipmi-sel Live Data view. | yes | no | | **Virtual Node** | vnode | Associates this job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no | @@ -167,6 +167,7 @@ The following alerts are available: |:------------|:----------|:------------| | [ ipmi_sensor_state ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipmi.conf) | ipmi.sensor_state | IPMI sensor $\{label:sensor} ($\{label:component}) state | | [ ipmi_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipmi.conf) | ipmi.sel | number of events in the IPMI System Event Log (SEL) | +| [ ipmi_sel_critical_events ](https://github.com/netdata/netdata/blob/master/src/health/health.d/ipmi.conf) | ipmi.sel_new_records | Number of critical events, other than threshold crossings, observed by the collector in the last 10 minutes. Failed SEL reads can delay reporting. The alert clears when no new one is observed, not when the problem is resolved; the ipmi-sel Live Data view lists the records | @@ -176,7 +177,17 @@ Metrics grouped by *scope*. The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. -Each sensor has its own reading and state chart. SEL is the raw repository entry count, including records FreeIPMI may filter during interpretation. The stock ipmi_events alert template matches the ipmi.sel context and applies to every Go job and to the C collector. +Each sensor has its own reading and state chart. SEL is the raw repository entry count, including +records FreeIPMI may filter during interpretation. The stock ipmi_events alert template matches the ipmi.sel +context and applies to every Go job and to the C collector. + +The SEL new records chart counts records newly observed since the previous value, by default FreeIPMI state. +Records already in the log when collection starts are not counted: the chart appears once the first read of +the log completes. After the BMC log is cleared or rewritten, rereading the same record does not count it +again. After the initial baseline, observed events are reported during rescans even if rollover prevents the +whole log from being read. A failed SEL read leaves a gap, and records observed during it count in the next +successful value. + ### Per sensor @@ -218,6 +229,23 @@ Metrics: | ipmi.sel | IPMI System Event Log Entries | events | events | +### Per SEL event type + +New System Event Log records of one event type on the selected BMC. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| event_type | `threshold` for threshold events, which also change the state of their sensor; `discrete` for every other record, OEM records included. | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| ipmi.sel_new_records | IPMI System Event Log New Records | nominal, warning, critical, unknown | records | + + ## Live Data @@ -225,7 +253,7 @@ Inspect the latest successful collection without issuing more IPMI commands. ### IPMI Sensors -Show current readings and default FreeIPMI health states, with sensor counts by component and state. +Show current readings, the thresholds the BMC uses for each threshold sensor, and default FreeIPMI health states, with sensor counts by component and state. Compare a reading with its thresholds to see how close it is to a limit; by default only crossing a critical or non-recoverable threshold makes the state critical. | Aspect | Description | |:-------|:------------| @@ -247,7 +275,7 @@ No additional configuration is required. #### Returns -One row per discovered full or compact sensor record, expanded for sharing. Unavailable numeric readings are null. +One row per discovered full or compact sensor record, expanded for sharing. Unavailable numeric readings are null. Thresholds are in the reading's units and are null when the sensor has none or they could not be read. | Column | Type | Unit | Visibility | Description | |:-------|:-----|:-----|:-----------|:------------| @@ -257,9 +285,64 @@ One row per discovered full or compact sensor record, expanded for sharing. Unav | Reading | float | | | Current reading; null when unavailable. | | Units | string | | | Reading units; null for discrete sensors. | | State | string | | | Default FreeIPMI health interpretation. | +| LNR | float | | | Lower non-recoverable threshold. | +| LCR | float | | | Lower critical threshold. | +| LNC | float | | | Lower non-critical threshold. | +| UNC | float | | | Upper non-critical threshold. | +| UCR | float | | | Upper critical threshold. | +| UNR | float | | | Upper non-recoverable threshold. | | Key | string | | hidden | Stable sensor identity within the collection job. | | rowOptions | none | | hidden | Row health severity. | +### IPMI System Event Log + +Browse the hardware events the BMC recorded, such as threshold crossings, fan, power and memory errors, processor throttling and boots, with default FreeIPMI states. Use it to see when a problem started and how often it recurs; the sensor charts show only the current state. + +| Aspect | Description | +|:-------|:------------| +| Name | `Ipmi-sel` | +| Require Cloud | no | +| Performance | Reads the records the collector already read from the BMC; sends no BMC requests. | +| Security | Read-only hardware event records from the configured target. | +| Availability | Available for jobs with collect_sel enabled while they run; when no job collects the SEL, requests return HTTP 404. Returns HTTP 503 before the first successful collection, after a collection failure, or while the BMC has not answered SEL requests. On the first collections of a large log, it shows the oldest records read so far. | + +#### Prerequisites + +No additional configuration is required. + +#### Parameters + +| Parameter | Type | Description | Required | Default | Options | +|:---------|:-----|:------------|:--------:|:--------|:--------| +| Instance | select | Select the IPMI collection job. | no | First available job | | +| State | select | Show only records with this default FreeIPMI state. | no | all | All states (default), Critical, Warning, Nominal, Unknown | +| Search | string | Case-sensitive Netdata simple patterns against sensor, type, event, direction, state, generator and record ID. Use `*DIMM*` for a substring. Space-separated patterns are checked in order; the first match decides, `!` excludes, and no match excludes the row. | no | No text filter | | + +#### Returns + +One row per SEL record the BMC retains, newest first in log order. The dashboard time range does not +filter the table, because SEL records are often weeks apart. Times are converted to UTC with the BMC's +SEL UTC offset. When the BMC reports none, times are the BMC clock, and the view shows how far that +clock is from the Agent clock. Records logged before a daylight saving change can be off by an hour, +because the BMC reports only its current offset. Records without a date (OEM records without a +timestamp, or records logged before the BMC clock was set) show Time as Unavailable. + + +| Column | Type | Unit | Visibility | Description | +|:-------|:-----|:-----|:-----------|:------------| +| Order | integer | | hidden | Position in the log, newest first. | +| Time | timestamp | | | When the BMC logged the record, in UTC; Unavailable when the record has no date. | +| Sensor | string | | | SDR sensor name, or the event generator and sensor number (for example BIOS #34) when the BMC has no record of that sensor. | +| Sensor Type | string | | | IPMI sensor type. | +| Event | string | | | Event description; threshold events include the trigger reading and threshold when the BMC records them and the sensor's SDR record describes their conversion. | +| Direction | string | | | Assertion (the condition started) or Deassertion (it ended). | +| State | string | | | Default FreeIPMI interpretation of the record. | +| Record ID | string | | hidden | SEL record identifier. | +| Generator | string | | hidden | Event generator, such as the BMC, BIOS or SMI handler, and its ID. | +| BMC Time | string | | hidden | Timestamp as the BMC recorded it, before UTC conversion. | +| Raw | string | | hidden | Record bytes as returned by the BMC. | +| rowOptions | none | | hidden | Row health severity. | + ## Troubleshooting diff --git a/docs/Collecting Metrics/Collectors/Synthetic Testing/Browser Journey.mdx b/docs/Collecting Metrics/Collectors/Synthetic Testing/Browser Journey.mdx index dff7d4a99..ae0f2c435 100644 --- a/docs/Collecting Metrics/Collectors/Synthetic Testing/Browser Journey.mdx +++ b/docs/Collecting Metrics/Collectors/Synthetic Testing/Browser Journey.mdx @@ -63,20 +63,34 @@ Each attempt starts a fresh browser and consumes CPU, memory and target website ### Prerequisites +#### Prepare the browser sandbox policy + +Managed bundles and preloads on Ubuntu hosts with restricted user namespaces, including Ubuntu 24.04, +require administrator-prepared AppArmor policy. DEM does not automatically allow service-writable +browser paths. The native runtime package supplies its own profile for its root-owned browser. +Containers also require compatible host and container namespace, AppArmor and seccomp policies. +Follow the [runtime setup guide](https://github.com/netdata/netdata/blob/master/src/go/plugin/dem/README.md#runtime-setup-and-retirement) +and keep Chromium's sandbox enabled when qualifying the actual service deployment. + + #### Set up the browser runtime Browser monitoring requires an explicitly installed runtime on Linux amd64 or arm64, running as the -unprivileged Netdata service account with Chromium sandboxing enabled. Delivery is experimental; -production downloads and native packages are not provided yet. +unprivileged Netdata service account with Chromium sandboxing enabled. Native installations use the optional +`netdata-dem-runtime` package on live systemd hosts; package hooks may restart the Agent. Other installation +methods use managed bundles or protected preloads. Production publication still requires release and platform qualification. -Obtain a trusted release descriptor and matching archive, then run as the service account: +For offline managed installation, set `runtime.offline_keyring` in `dem.conf` to the path of an +administrator-provisioned public OpenPGP keyring. Obtain a signed release descriptor and matching archive, +then run as the service account: ```sh -dem.plugin runtime install --manifest /absolute/path/manifest.json --archive /absolute/path/runtime.tar.gz +dem.plugin runtime install --release /absolute/path/release.json --archive /absolute/path/runtime.tar.zst dem.plugin runtime status ``` -Restart DEM to activate the installation. Enabling a monitor never downloads a runtime. +Restart DEM to activate the installation. Explicit install enables automatic update preparation; add +--manual-updates for manual control. Enabling a monitor never downloads a runtime. Use `dem.plugin runtime qualify` under the service's execution policy to check both journeys and Lighthouse. See the [runtime setup guide](https://github.com/netdata/netdata/blob/master/src/go/plugin/dem/README.md#runtime-setup-and-retirement) for updates, explicit downloads, installation paths and protected preloads. diff --git a/docs/Collecting Metrics/Collectors/Synthetic Testing/Lighthouse Desktop Audit.mdx b/docs/Collecting Metrics/Collectors/Synthetic Testing/Lighthouse Desktop Audit.mdx index 9e89c523c..d649a7db3 100644 --- a/docs/Collecting Metrics/Collectors/Synthetic Testing/Lighthouse Desktop Audit.mdx +++ b/docs/Collecting Metrics/Collectors/Synthetic Testing/Lighthouse Desktop Audit.mdx @@ -62,20 +62,34 @@ Each attempt starts a fresh browser and consumes CPU, memory and target website ### Prerequisites +#### Prepare the browser sandbox policy + +Managed bundles and preloads on Ubuntu hosts with restricted user namespaces, including Ubuntu 24.04, +require administrator-prepared AppArmor policy. DEM does not automatically allow service-writable +browser paths. The native runtime package supplies its own profile for its root-owned browser. +Containers also require compatible host and container namespace, AppArmor and seccomp policies. +Follow the [runtime setup guide](https://github.com/netdata/netdata/blob/master/src/go/plugin/dem/README.md#runtime-setup-and-retirement) +and keep Chromium's sandbox enabled when qualifying the actual service deployment. + + #### Set up the browser runtime Browser monitoring requires an explicitly installed runtime on Linux amd64 or arm64, running as the -unprivileged Netdata service account with Chromium sandboxing enabled. Delivery is experimental; -production downloads and native packages are not provided yet. +unprivileged Netdata service account with Chromium sandboxing enabled. Native installations use the optional +`netdata-dem-runtime` package on live systemd hosts; package hooks may restart the Agent. Other installation +methods use managed bundles or protected preloads. Production publication still requires release and platform qualification. -Obtain a trusted release descriptor and matching archive, then run as the service account: +For offline managed installation, set `runtime.offline_keyring` in `dem.conf` to the path of an +administrator-provisioned public OpenPGP keyring. Obtain a signed release descriptor and matching archive, +then run as the service account: ```sh -dem.plugin runtime install --manifest /absolute/path/manifest.json --archive /absolute/path/runtime.tar.gz +dem.plugin runtime install --release /absolute/path/release.json --archive /absolute/path/runtime.tar.zst dem.plugin runtime status ``` -Restart DEM to activate the installation. Enabling a monitor never downloads a runtime. +Restart DEM to activate the installation. Explicit install enables automatic update preparation; add +--manual-updates for manual control. Enabling a monitor never downloads a runtime. Use `dem.plugin runtime qualify` under the service's execution policy to check both journeys and Lighthouse. See the [runtime setup guide](https://github.com/netdata/netdata/blob/master/src/go/plugin/dem/README.md#runtime-setup-and-retirement) for updates, explicit downloads, installation paths and protected preloads. diff --git a/docs/Netdata Agent/Logging.mdx b/docs/Netdata Agent/Logging.mdx index eefe73206..433bbb6fd 100644 --- a/docs/Netdata Agent/Logging.mdx +++ b/docs/Netdata Agent/Logging.mdx @@ -231,7 +231,7 @@ Example logrotate configuration: | `ND_SRC_IP` | `src_ip` | `SourceIP` | 24 | when the event happened during an inbound request, this is the IP the request came from | | `ND_SRC_PORT` | `src_port` | `SourcePort` | 25 | when the event happened during an inbound request, this is the port the request came from | | `ND_SRC_FORWARDED_HOST` | `src_forwarded_host` | `SourceForwardedHost` | 26 | the contents of the HTTP header `X-Forwarded-Host` | -| `ND_SRC_FORWARDED_FOR` | `src_forwarded_for` | `SourceForwardedFor` | 27 | the contents of the HTTP header `X-Forwarded-For` | +| `ND_SRC_FORWARDED_FOR` | `src_forwarded_for` | `SourceForwardedFor` | 27 | the first address in the HTTP header `X-Forwarded-For`, if it is a valid IPv4/IPv6 address (port dropped) | | `ND_SRC_CAPABILITIES` | `src_capabilities` | `SourceCapabilities` | 28 | when the request came from a child, this is the communication capabilities of the child | | `ND_DST_TRANSPORT` | `dst_transport` | `DestinationTransport` | 29 | when the event happened during an outbound request, this is the outbound request transport | | `ND_DST_IP` | `dst_ip` | `DestinationIP` | 30 | when the event happened during an outbound request, this is the IP the request destination | diff --git a/docs/Netdata Agent/Versions & Platforms.mdx b/docs/Netdata Agent/Versions & Platforms.mdx index bb34fb41e..eb1feefcb 100644 --- a/docs/Netdata Agent/Versions & Platforms.mdx +++ b/docs/Netdata Agent/Versions & Platforms.mdx @@ -83,6 +83,7 @@ Our [static builds](#static-builds) are expected to work on these platforms if a | Docker | 19.03 or newer | x86\_64, ARMv7, AArch64 | See our [Docker documentation](/docs/netdata-agent/installation/docker) for more info on using Netdata on Docker | | Debian | 13.x | x86\_64, i386, ARMv7, AArch64 | | | Debian | 12.x | x86\_64, i386, ARMv7, AArch64 | | +| Fedora | 45 | x86\_64, AArch64 | | | Fedora | 44 | x86\_64, AArch64 | | | Fedora | 43 | x86\_64, AArch64 | | | openSUSE | Tumbleweed | x86\_64, AArch64 | | @@ -96,6 +97,7 @@ Our [static builds](#static-builds) are expected to work on these platforms if a | Rocky Linux | 10.x | x86\_64, AArch64 | Also includes support for Alma Linux and other ABI compatible RHEL derivatives | | Rocky Linux | 9.x | x86\_64, AArch64 | Also includes support for Alma Linux and other ABI compatible RHEL derivatives | | Rocky Linux | 8.x | x86\_64, AArch64 | Also includes support for Alma Linux and other ABI compatible RHEL derivatives | +| Ubuntu | 26.10 | x86\_64, AArch64, ARMv7 | | | Ubuntu | 26.04 | x86\_64, AArch64, ARMv7 | | | Ubuntu | 24.04 | x86\_64, AArch64, ARMv7 | | | Ubuntu | 22.04 | x86\_64, ARMv7, AArch64 | | diff --git a/docs/Netdata Cloud On-Prem/High Availability and Disaster Recovery.mdx b/docs/Netdata Cloud On-Prem/High Availability and Disaster Recovery.mdx new file mode 100644 index 000000000..36a184fd3 --- /dev/null +++ b/docs/Netdata Cloud On-Prem/High Availability and Disaster Recovery.mdx @@ -0,0 +1,483 @@ +--- +custom_edit_url: "https://github.com/netdata/netdata-cloud-onprem/edit/master/docs/learn.netdata.cloud/high-availability-and-disaster-recovery.md" +sidebar_label: "High Availability and Disaster Recovery" +learn_status: "Published" +learn_rel_path: "Netdata Cloud On-Prem" +sidebar_position: "100" +learn_link: "https://learn.netdata.cloud/docs/netdata-cloud-on-prem/high-availability-and-disaster-recovery" +slug: "/netdata-cloud-on-prem/high-availability-and-disaster-recovery" +--- + +# Netdata Cloud On-Prem High Availability and Disaster Recovery + +This guide shows you how to **back up and restore** your Netdata Cloud On-Prem installation and how to run it in an **active/passive setup**, where a second installation is ready to take over when the first one fails. + +:::note + +This guide requires the `netdata-cloud-onprem` Helm chart **version 2.7.0 or newer**. If you run an older version, upgrade it first. + +::: + +## Where Your Data Lives + +Knowing where the state is kept tells you what needs to be backed up and what can simply be reinstalled. + +| Component | What It Keeps | State | +| --------------------------------- | ------------------------------------------------------------------------------------------------- | ----------------------------------- | +| **Netdata Cloud services** | Nothing, every microservice is stateless | None | +| **PostgreSQL** | Users, spaces, rooms, agents, nodes, chart contexts, alerts synced with the Agents, settings | **Persistent** | +| **Elasticsearch** | Feed events triggered by the actions in Netdata Cloud On-Prem and by the Agents | **Persistent** | +| **Pulsar, EMQX** | Messages passed between the Agents and the Netdata Cloud services, and between the services | In transit only\* | +| **Redis** | Cache that speeds up some operations, derived from the PostgreSQL state | Disposable | +| **Keys** | Keys used to sign tokens and **encrypt some of the database entries** | **Persistent**, not in `values.yaml` | + +\* Notifications and feed events queued at the moment of failover are lost. + +:::warning + +**The keys are as important as the database.** Some database entries are encrypted with them, so **a database backup without the matching keys cannot be restored**. Losing or changing the keys results in data loss. + +By default, the keys are generated randomly on the first installation into the `netdata-cloud-common` secret. You can also deliver them yourself with `global.autogeneratedSecrets.secretBased.existingSecret`. **In both cases you must back them up.** + +::: + +## Backup and Restore + +### What to Back Up + +| What | How | Required | +| ---------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | +| **PostgreSQL** | Your database backup tools, for example `pg_dump`, volume snapshots or point-in-time recovery of your provider | **Yes** | +| **Elasticsearch** | [Elasticsearch snapshots](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshot-restore.html) | Recommended, without it you lose the history of feed events | +| **Helm values** | `helm get values -n netdata-cloud netdata-cloud-onprem -o yaml` | **Yes** | +| **Keys** | See [Move the Keys to Your Own Secret](#move-the-keys-to-your-own-secret) | **Yes** | +| **Webhook TLS certificate** | The `cloud-notifications-dispatcher-service-webhook-tls` secret, or the secret set in `cloud_notifications_dispatcher_service.webhookCertificate.secretBased.existingSecret` | Only when your webhook receivers verify the certificate | +| **Secrets referenced in the Helm values** | License, database credentials, SSO, SMTP and ingress TLS secrets referenced by the `existingSecret` options are not part of the values | **Yes**, or recreate them from your secret store | +| **Redis, Pulsar, EMQX** | Not needed | No | + +:::warning + +**The keys must come from the same installation as the database backup.** Keys from a different installation cannot decrypt the data. + +::: + +### Move the Keys to Your Own Secret + +We recommend moving the keys to a secret managed by you **before you ever need a restore**. You then back up and restore a single secret, which you can keep in your secret store (for example Vault or External Secrets), and your installation is ready for the [active/passive setup](#activepassive-setup). + +Installations created by older chart versions keep some of the keys outside of `netdata-cloud-common`: `SPACEROOM_AES_SECRET` in the `cloud-spaceroom-service` secret and `INSIGHTS_SECRETS_KEY` in the `cloud-insights-service` secret. + +Step 1: Create the `netdata-cloud-keys` secret from the keys of your installation
+ +Use the command from the description of `global.autogeneratedSecrets.secretBased.existingSecret` in the `values.yaml` file of the `netdata-cloud-onprem` chart. It collects the keys from all the secrets above and copies them without decoding. The description also lists the required keys and their format.
+ +
Step 2: Use the secret in your Helm values
+ +```yaml +global: + autogeneratedSecrets: + secretBased: + existingSecret: netdata-cloud-keys +``` + +
Step 3: Upgrade your installation
+ +```bash +helm upgrade --wait --install netdata-cloud-onprem -n netdata-cloud -f values.yaml . +``` + +The chart validates the secret before the upgrade: it must contain all the keys in the expected format, and they must be the same as the keys your installation already uses. If anything is wrong, the upgrade fails with an error that explains what to fix. + +
Step 4: Back up the secret
+ +Store the secret together with your database backups:
+ +```bash +kubectl -n netdata-cloud get secret netdata-cloud-keys -o json \ +| jq '{apiVersion, kind, type, metadata: {name: .metadata.name}, data}' > netdata-cloud-keys.json +``` + +:::tip + +If your webhook receivers verify the webhook TLS certificate, do the same with it: copy it to your own `kubernetes.io/tls` secret and set it in `cloud_notifications_dispatcher_service.webhookCertificate.secretBased.existingSecret`. Otherwise, the restored installation generates a new certificate. + +::: + +### Restore Step by Step + +
+The restore flow diagram
+ +```mermaid +flowchart LR + db("**🗄️ Restore Databases**

PostgreSQL

Elasticsearch") + secrets("**🔑 Create Secrets**

Keys, webhook certificate,

secrets referenced

in the values") + install("**📦 Helm Install**

Backed-up values

with existingSecret") + agents("**🌍 Agents Reconnect**

Re-claim the Agents

claimed after the backup") + + db --> secrets --> install --> agents + + %% Style definitions + classDef neutral fill:#f9f9f9,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef database fill:#2196F3,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef complete fill:#4caf50,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef alert fill:#ffeb3b,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + + %% Apply styles + class db database + class secrets,install neutral + class agents alert +``` + +
+ +Step 1: Prepare the cluster and the dependencies
+ +Follow the [installation guide](https://learn.netdata.cloud/docs/netdata-cloud-on-prem/installation) up to the installation of the `netdata-cloud-onprem` chart. Pulsar, EMQX, Redis, Traefik and the ingress controller start empty.
+ +
Step 2: Restore PostgreSQL and Elasticsearch
+ +Restore the databases with your backup tools. Make sure the Helm values point to the restored databases.
+ +
Step 3: Create the secrets
+ +Create the keys secret in the namespace of the installation:
+ +```bash +kubectl -n netdata-cloud apply -f netdata-cloud-keys.json +``` + +Recreate the webhook TLS certificate, if you backed it up, and the secrets referenced in your Helm values (license, database credentials, SSO, SMTP, ingress TLS).
+ +
Step 4: Install Netdata Cloud On-Prem
+ +Use the backed-up Helm values with the keys secret set:
+ +```yaml +global: + autogeneratedSecrets: + secretBased: + existingSecret: netdata-cloud-keys +``` + +```bash +helm upgrade --wait --install netdata-cloud-onprem -n netdata-cloud --create-namespace -f values.yaml . +``` + +Use the chart version of the backed-up installation or a newer one. Downgrades are not supported, because the database migrations cannot be reverted.
+ +
Step 5: Verify the restore
+ +Log in and check that your spaces, rooms and nodes are there. The Agents reconnect by themselves within a few minutes after a controlled switchover, up to 20 minutes after an outage.
+ +### What a Restore Brings Back + +A restore brings your installation back to **the moment of the backup**. Everything that happened afterwards is lost: users, spaces, rooms, invitations, alert silencing rules and settings created or changed after the backup. + +:::note + +**Agents claimed after the backup cannot reconnect.** They are not in the restored database, so Netdata Cloud On-Prem rejects them and they keep retrying every minute. To fix it, [reconnect the Agent](https://learn.netdata.cloud/docs/netdata-cloud/connect-agent#reconnect-agent): remove its `cloud.d/` directory and claim it again. If the Agent is claimed with `claim.conf` or environment variables, restarting it after removing the directory is enough. + +::: + +PostgreSQL and Elasticsearch backups don't have to be taken at exactly the same moment. The only effect is a gap or a few extra events in the feed. + +:::tip + +Back up PostgreSQL often, or use point-in-time recovery, to keep the loss small. **Test your restore procedure regularly** on a separate installation, so you know it works before you need it. + +::: + +## Active/Passive Setup + +### How It Works + +In the active/passive setup, you run **two Netdata Cloud On-Prem installations** that share the same PostgreSQL and Elasticsearch: + +- **The primary side** is active. All the Agents are connected to it. +- **The failover side** is installed with the same version and the same configuration, but it is on standby: its Netdata Cloud services are scaled to 0 and its CronJobs are suspended. Its own Pulsar, EMQX and Redis keep running. It takes over when the primary side fails. + +
+The active/passive setup diagram
+ +```mermaid +flowchart TD + agents("**🌍 Netdata Agents**

and users") + dns("**🧭 DNS / Load Balancer**

netdata.example.com") + + subgraph primary ["Primary side (active)"] + p_emqx("**📤 EMQX**

Agents connected") + p_services("**⚙️ Netdata Cloud services**

CronJobs active") + p_deps("**⚡ Pulsar, Redis**") + p_keys("**🔑 netdata-cloud-keys**") + end + + subgraph failover ["Failover side (standby)"] + f_emqx("**📤 EMQX**

No Agents") + f_services("**⚙️ Netdata Cloud services**

Scaled to 0,

CronJobs suspended") + f_deps("**⚡ Pulsar, Redis**") + f_keys("**🔑 netdata-cloud-keys**

same keys") + end + + sql("**✨ PostgreSQL**") + elk("**🗞️ Elasticsearch**") + + agents --> dns + dns ==> p_emqx + dns ==> p_services + dns -.->|**on failover**| failover + p_emqx --- p_services --- p_deps + f_emqx --- f_services --- f_deps + p_services --> sql + p_services --> elk + f_services -.-> sql + f_services -.-> elk + + %% Style definitions + classDef alert fill:#ffeb3b,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef neutral fill:#f9f9f9,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef complete fill:#4caf50,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef database fill:#2196F3,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef standby fill:#e0e0e0,stroke:#9e9e9e,stroke-width:3px,color:#616161,font-size:18px,stroke-dasharray:5 5 + + %% Apply styles + class agents alert + class dns,p_emqx,p_deps,p_keys,f_emqx,f_deps,f_keys neutral + class p_services complete + class f_services standby + class sql,elk database +``` + +
+ +| Component | Primary Side | Failover Side | +| --------------------------------------------- | -------------------------------- | -------------------------------- | +| **PostgreSQL, Elasticsearch** | Shared | Shared | +| **Pulsar, EMQX, Redis, Traefik, ingress** | Own | Own | +| **Keys secret, webhook TLS certificate** | Same copy | Same copy | +| **Netdata Cloud services, CronJobs** | Running | Scaled to 0, suspended | +| **Helm values** | `global.standby: false` | `global.standby: true` | +| **Agents** | Connected | Connected only after a failover | + +**Before you begin**, make sure that: + +- **PostgreSQL and Elasticsearch are reachable from both sides.** Their own high availability is out of the scope of this guide, follow your database provider's recommendations, because they are shared by both sides. +- **Both sides use the same public hostname** (`global.public`) with a TLS certificate valid for it. The Agents connect to Netdata Cloud On-Prem using this hostname, so a failover only changes where the hostname points to (DNS record or load balancer). If you switch with DNS, use a low TTL. +- **Both sides use the same Helm values**, except `global.standby`, including the same license and the same secrets referenced in the values. +- **Both sides use the same keys**, delivered with `global.autogeneratedSecrets.secretBased.existingSecret`. + +### Why the Failover Side Is on Standby + +The Netdata Cloud services don't elect a leader between the two sides, they take their work from the shared PostgreSQL. A failover side with running services would do a part of the work of the primary side, but with its own Pulsar and EMQX, where no Agents are connected. + +**Background workers** of the services take jobs from PostgreSQL: alert notifications, alert and chart contexts checkpoint commands for the Agents, and AI reports. A job is taken by one side only, so on the failover side: + +- the checkpoint commands are sent to its EMQX, where no Agent receives them, so roughly half of them are lost, +- the alert notifications are delivered by its notifications dispatcher, so they depend on the health of the failover side. + +**CronJobs** compare the state of their own side with PostgreSQL. The Agents keep a long-running connection to the EMQX broker of the side they are connected to. The `sanitize-unreachable-agents` CronJob runs every 5 minutes and compares **the connections in the EMQX of its own side** with the Agent states in PostgreSQL: + +- An Agent that is online in PostgreSQL but not connected to its EMQX is **marked as unreachable**. +- An Agent that is connected to its EMQX but unreachable in PostgreSQL is **disconnected from EMQX**, so it connects again and resyncs its state. + +If the CronJobs ran on both sides, the failover side, with no Agents in its EMQX, would mark all the Agents as unreachable every 5 minutes. The primary side would then disconnect all of them, they would reconnect, and the cycle would start again. + +`global.standby: true` prevents both: it scales all the Netdata Cloud services to 0 and suspends all the CronJobs. The database migrations still run on every `helm install` and `helm upgrade`. + +:::warning + +**Exactly one side must run with `global.standby: false` at any time.** + +::: + +The same mechanism helps during a failover. The primary side can no longer update the Agent states, so PostgreSQL still shows them as connected. When an Agent connects to the failover side, Netdata Cloud On-Prem notices that it is not connected to the local EMQX and lets it in. The first `sanitize-unreachable-agents` run on the new primary side marks the Agents that haven't reconnected yet as unreachable. + +### Set Up Both Sides + +Step 1: Create the keys secret
+ +For an existing installation, [move the keys to your own secret](#move-the-keys-to-your-own-secret) on the primary side. For a new installation, create the secret with new keys using the command from the description of `global.autogeneratedSecrets.secretBased.existingSecret` in the `values.yaml` file of the `netdata-cloud-onprem` chart.
+ +
Step 2: Copy the keys secret to the failover side
+ +```bash +kubectl --context -n netdata-cloud get secret netdata-cloud-keys -o json \ +| jq '{apiVersion, kind, type, metadata: {name: .metadata.name}, data}' \ +| kubectl --context -n netdata-cloud apply -f - +``` + +Copy the secrets referenced in your Helm values (license, database credentials, SSO, SMTP, ingress TLS) the same way, or create them on both sides from your secret store.
+ +
Step 3: Use the same webhook TLS certificate
+ +Each installation generates its own self-signed webhook TLS certificate. If your webhook receivers verify it, create one `kubernetes.io/tls` secret on both sides and set it in the Helm values:
+ +```bash +kubectl -n netdata-cloud create secret tls netdata-cloud-webhook-tls --cert=webhook.crt --key=webhook.key +``` + +```yaml +cloud_notifications_dispatcher_service: + webhookCertificate: + secretBased: + existingSecret: netdata-cloud-webhook-tls +``` + +
Step 4: Install or upgrade the primary side
+ +```yaml +global: + standby: false + autogeneratedSecrets: + secretBased: + existingSecret: netdata-cloud-keys +``` + +```bash +helm upgrade --wait --install netdata-cloud-onprem -n netdata-cloud --create-namespace -f values.yaml . +``` + +
Step 5: Install the failover side
+ +Use the same chart version and the same Helm values, on standby:
+ +```yaml +global: + standby: true + autogeneratedSecrets: + secretBased: + existingSecret: netdata-cloud-keys +``` + +```bash +helm upgrade --wait --install netdata-cloud-onprem -n netdata-cloud --create-namespace -f values.yaml . +``` + +
Step 6: Point the public hostname to the primary side
+ +Configure your DNS record or load balancer so the public hostname points to the primary side only.
+ +### Fail Over + +
+The failover diagram
+ +```mermaid +flowchart TD + agents("**🌍 Netdata Agents**

and users") + dns("**🧭 DNS / Load Balancer**

netdata.example.com") + + subgraph primary ["Old primary side (standby)"] + p_emqx("**📤 EMQX**

Stopped") + p_services("**⚙️ Netdata Cloud services**

Scaled to 0,

CronJobs suspended") + end + + subgraph failover ["New primary side (active)"] + f_emqx("**📤 EMQX**

Agents reconnect") + f_services("**⚙️ Netdata Cloud services**

Running,

CronJobs active") + end + + sql("**✨ PostgreSQL**") + elk("**🗞️ Elasticsearch**") + + agents --> dns + dns -. "**disconnected**" .-x p_emqx + dns ==> f_emqx + dns ==> f_services + f_emqx --- f_services + f_services --> sql + f_services --> elk + p_services -.-x sql + + %% Style definitions + classDef alert fill:#ffeb3b,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef neutral fill:#f9f9f9,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef complete fill:#4caf50,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef database fill:#2196F3,stroke:#000000,stroke-width:3px,color:#000000,font-size:18px + classDef broken fill:#e0e0e0,stroke:#9e9e9e,stroke-width:3px,color:#616161,font-size:18px,stroke-dasharray:5 5 + + %% Apply styles + class agents alert + class dns,f_emqx neutral + class f_services complete + class p_emqx,p_services broken + class sql,elk database +``` + +
+ +The failover is a manual procedure. If you automate it, the automation must follow the same steps in the same order. + +Step 1: Disconnect the Agents from the primary side
+ +If the primary side is still reachable, put it on standby first and then stop its EMQX:
+ +```bash +# set global.standby: true in the primary side values +helm upgrade --wait netdata-cloud-onprem -n netdata-cloud -f values.yaml . + +# find the EMQX StatefulSet with: kubectl -n netdata-cloud get statefulsets +kubectl -n netdata-cloud scale statefulset --replicas=0 +``` + +Stopping EMQX closes the long-running Agent connections. If the primary side is not reachable at all, make sure it can't come back by itself with its services running, for example by keeping it isolated from the databases.
+ +
Step 2: Activate the failover side
+ +Set `global.standby: false` in the failover side values and upgrade it. `--wait` returns when the Netdata Cloud services are running:
+ +```bash +helm upgrade --wait netdata-cloud-onprem -n netdata-cloud -f values.yaml . +``` + +The failover side is now the primary side.
+ +
Step 3: Point the public hostname to the new primary side
+ +Change your DNS record or load balancer. The Agents notice the closed connection, connect again using the same hostname and reach the new primary side within a few minutes. No changes are needed on the Agents.
+ +
Step 4: Verify the failover
+ +Log in and check that your nodes are online. Within 5 minutes, the Agents that haven't reconnected yet are shown as offline.
+ +
Step 5: Bring the old primary side back as the failover side
+ +Once it's repaired, make sure it runs with `global.standby: true` **before** its services and CronJobs can run, then start its EMQX again. It is now the failover side. To fail back, repeat the procedure in the opposite direction.
+ +:::warning + +**Never activate one side while the Agents are still connected to the other side**, and never bring the old primary side back with its services running. Otherwise, both sides share the work and fight over the Agent states as described in [Why the Failover Side Is on Standby](#why-the-failover-side-is-on-standby). + +::: + +### Upgrade + +Both sides must run the same version. The database migrations run as Helm hook Jobs on every `helm install` and `helm upgrade`, so they run on the first upgraded side and change the shared database. + +Step 1: Back up the databases and the Helm values
+ +[Back up](#what-to-back-up) PostgreSQL and Elasticsearch, and save the Helm values and the chart version of the primary side. Downgrades are not supported, because the migrations cannot be reverted, so this backup is your only way back. The keys don't change during an upgrade.
+ +
Step 2: Upgrade the primary side
+ +```bash +helm upgrade --wait netdata-cloud-onprem -n netdata-cloud -f values.yaml . +``` + +
Step 3: Upgrade the failover side right after
+ +Use the same chart version. The database is already migrated to this version, so its migrations find nothing left to do.
+ +```bash +helm upgrade --wait netdata-cloud-onprem -n netdata-cloud -f values.yaml . +``` + +Until it's upgraded, the failover side keeps the old version, but its services are scaled to 0, so nothing of it uses the migrated database.
+ +:::warning + +**Don't fail over between the two upgrades.** A failover activates the failover side with `helm upgrade`, which runs its migrations too. The database is already migrated to a newer version than the migrations of the failover side know, so they fail and the `helm upgrade` fails with them. Finish the upgrade of the failover side before any failover. + +::: + +If the upgrade of the primary side fails, restore PostgreSQL and Elasticsearch from the backup from Step 1, and only then bring the primary side back to the previous chart version with the saved Helm values. The previous version doesn't work with the migrated database. The failover side was not upgraded yet, so it matches the restored database and needs no changes. diff --git a/docs/Netdata Cloud On-Prem/Release Notes.mdx b/docs/Netdata Cloud On-Prem/Release Notes.mdx index ec0c6de1e..7b3b21ef1 100644 --- a/docs/Netdata Cloud On-Prem/Release Notes.mdx +++ b/docs/Netdata Cloud On-Prem/Release Notes.mdx @@ -10,6 +10,42 @@ slug: "/netdata-cloud-on-prem/release-notes" # Release notes +## 2.7.0 (2026-11-04) + +### Breaking changes + +- Stricter OIDC SSO token verification: an ID token is required, and `aud`, `azp`, expiry and nonce are strictly validated. Identity providers that issue non-standard tokens may fail at login after the upgrade +- Removed nine unused charts `/api/v2` endpoints. Scripts or integrations calling them now get a 404 +- Silencing rules API: removed `severities`, use `notification_options` instead +- Feed lean search: the `sort` value of each hit now also includes the event ID, which can break clients decoding it strictly as integers + +### Features + +- Helm chart supports active/passive high availability, with a standby mode and keys managed in a single Kubernetes secret outside the chart. Documentation is available at https://learn.netdata.cloud/docs/netdata-cloud-on-prem/high-availability-and-disaster-recovery +- Notification channels can be limited to alerts of a given role, class, type and component +- Alert Markers: custom alert styles and sounds driven by personal or space rules +- Decommission nodes from the UI or through a new bulk API. Notifications for decommissioned nodes are skipped +- Anomalies replaced by a new incident investigation workspace +- Run metric correlations directly from a chart highlight. Metric Correlations now defaults to Volume instead of KS2 +- Custom node groups can keep their nodes out of the default groups +- Added a Raised Alerts table card to custom dashboards +- Topology maps handle larger topologies, using WebGPU on capable devices +- New dashboard coverage for Windows, IIS, Exchange, MSMQ, DNS, Redfish, Linux Audit and SMBIOS memory +- AI features (when `cloud-insights-service` is enabled): Infrastructure Knowledge with AI memories, chat answers that keep generating if the connection drops, filtering reports by node, AI analysis from Anomalies and Metric Correlations, and GitLab and PagerDuty OAuth for MCP +- Rooms with Agents below v2.12.2 now show a critical security notice + +### Bug fixes + +- Fixed OIDC SSO with providers that send `aud` as an array, such as JumpCloud +- Alerts: fixed filtering for multi-role alerts, incomplete transition history, room transitions including other rooms' nodes, and notification dispatcher deadlocks +- Silencing rules: recurrences and dates now follow the rule's timezone +- Fixed large parent Agents dropping messages on reconnect due to rate limits +- Dyncfg: fixed dependent fields, array tabs and per-node addressing on Agent dashboards +- Fixed lean feed search skipping events that share a timestamp +- Helm chart: the webhook certificate is no longer regenerated on every upgrade, and `helm upgrade --reuse-values` from older releases no longer fails +- Agent dashboards now honour the Agent telemetry opt-out +- Update Golang to 1.27.3 and dependencies + ## 2.6.0 (2026-08-20) ### Features diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki Cloud Controller.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki Cloud Controller.mdx index a2b4a0cfa..f5d3cdccd 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki Cloud Controller.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki Cloud Controller.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, meraki, (cloud, controller), snmp, sd-wan, npm] description: "Monitor Cisco Meraki (Cloud Controller) (sd-wan) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "640" +sidebar_position: "650" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-meraki-cloud-controller" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-meraki-cloud-controller" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki.mdx new file mode 100644 index 000000000..f90a9cba6 --- /dev/null +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Meraki.mdx @@ -0,0 +1,845 @@ +--- +custom_edit_url: "https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/meraki/metadata.yaml" +sidebar_label: "Cisco Meraki" +learn_status: "Published" +learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" +keywords: [cisco meraki, meraki, meraki dashboard, meraki api, dashboard api, cisco] +description: "Monitor device availability, switch port traffic and uplink traffic in a Cisco Meraki organization, with each device shown as its own Netdata node." +message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" +sidebar_position: "640" +learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-meraki" +slug: "/network-performance-monitoring/device-metrics/integrations/cisco-meraki" +--- + + +# Cisco Meraki + + +Cisco Meraki + + +Plugin: go.d.plugin +Module: meraki + +Maintained by Netdata + +## Overview + +Monitor device availability, switch port traffic and uplink traffic in a Cisco Meraki organization, with each device shown as its own Netdata node. + +- **Device availability**: the status Meraki Dashboard reports for each device: `online`, `alerting`, `offline` or `dormant`. +- **Inventory**: how many devices are assigned to the organization's networks, and which ones. +- **Switch ports** (two opt-in options): sent and received kilobits/s, and packets/s, of every switch port, on the switch's node. +- **Uplink traffic** (opt-in): sent and received kilobits/s of each WAN and cellular uplink of every MX security appliance and Z teleworker gateway network. +- **Fleet filtering**: device nodes and charts carry organization, network, model and product type labels, so a large fleet can be grouped and filtered. + +Every device type Meraki reports availability for is covered, including security appliances (MX), switches (MS), wireless access points (MR), cameras (MV), sensors (MT) and cellular gateways (MG). + + +The collector sends read-only HTTPS requests to the Meraki Dashboard API in the cloud, authenticated with an API key. It never connects to the devices: the Agent needs outbound HTTPS (port 443) to the regional API host and to the Meraki shard hosts the API redirects to, such as `n123.meraki.com`. + +Every collection (every 5 minutes by default) reads these API operations completely, page by page: + +| Operation | Used for | Read | +|:----------|:---------|:-----| +| `getOrganizations` | The name of the configured organization | Always | +| `getOrganizationNetworks` | Network names for the labels | Always | +| `getOrganizationDevices` | The devices assigned to networks, one node each | Always | +| `getOrganizationDevicesAvailabilities` | The status of each device | Always | +| `getOrganizationSwitchPortsUsageHistoryByDeviceByInterval` | Switch port traffic | With `collect_switch_port_traffic` | +| `getDeviceSwitchPortsStatusesPackets` | Switch port packet rates, one request per switch | With `collect_switch_port_packets` | +| `getOrganizationApplianceUplinksUsageByNetwork` | Uplink traffic | With `collect_appliance_uplink_traffic` | + +Whatever `update_every` is, switch port traffic is looked up in the last 15 minutes, uplink traffic is read for the 5 minutes that ended 5 minutes ago, and packet rates for the last 5 minutes. + +When a job starts, one small `getOrganizationDevices` request checks that the API key can reach the organization. + + +This collector is supported on all platforms. + +This collector supports collecting metrics from multiple instances of this integration. + +The collector needs an API key whose owner has at least read-only access to the organization. A Meraki API key acts with the permissions of the Dashboard administrator who created it; the collector only reads. + + +### Default Behavior + +#### Auto-Detection + +Nothing is detected automatically: each job monitors the one organization set in `organization_id`, with the API key you configure. Within that organization, every collection finds all assigned devices and adds a node for each new one. + + +#### Limits + +- **Five-minute data.** Meraki refreshes device availability every 5 minutes without a sample time, and traffic values are averages over at least 5 minutes, so an `update_every` below 300 seconds adds requests, not detail. Above 300 seconds, each traffic value still covers only one Meraki window, usually 5 minutes, not the whole collection interval. +- **Traffic lags behind.** Meraki publishes traffic some minutes after it happens. Switch port traffic is the latest interval Meraki has reported within the last 15 minutes, so it can be up to 15 minutes old; the interval age chart shows how old it is, and the chart has a gap when Meraki has reported no usable interval in that time. Uplink traffic covers the 5 minutes that ended 5 minutes earlier, to give Meraki time to count the bytes. Packet rates cover the last 5 minutes, which Meraki may not have finished reporting. Missed collections are not backfilled. +- **Uplinks belong to the network.** When more than one appliance of a network was active, such as a warm spare pair, Meraki adds up their bytes per interface. Uplink charts are therefore per network and interface, on the job's node or its virtual node, not on an appliance's node. +- **Shared API budget.** Meraki allows 10 requests per second per organization and 100 per source IP address, shared with every other application using them. The collector sends at most 10 requests per second per job, and after a `429 Too Many Requests` answer it sends nothing until the `Retry-After` wait Meraki requested has passed. See [Meraki API rate limits](https://developer.cisco.com/meraki/api-v1/rate-limit/). + + +#### Performance Impact + +Collecting costs the Agent little CPU; the nodes and charts it creates, counted below, use Agent memory and disk like any others. On the Meraki side, each operation costs one request per page, plus one for each redirect Meraki answers with: + +| Operation | Page size | +|:----------|:----------| +| `getOrganizations` | 9,000 organizations visible to the API key | +| `getOrganizationNetworks` | 1,000 networks | +| `getOrganizationDevices` | 1,000 assigned devices | +| `getOrganizationDevicesAvailabilities` | 1,000 devices | + +An organization with 2,500 devices in 40 networks takes 1 + 1 + 3 + 3 = 8 requests per collection. Increase `update_every` to make fewer requests; increase `timeout` if a very large organization cannot finish within it. + +Each traffic option adds requests to every collection: + +| Option | Requests | Charts | +|:-------|:---------|:-------| +| `collect_switch_port_traffic` | 1 per 50 switches Meraki lists for the organization | 2 per switch port | +| `collect_switch_port_packets` | 1 per assigned switch | 1 per switch port | +| `collect_appliance_uplink_traffic` | 1 | 1 per uplink | + +Requests are paced at 10 per second, so packet rates for 1,000 switches add about 100 seconds to every collection, more than the default `timeout` of 60 seconds. A collection that runs past `timeout` updates no chart, availability included. For a large fleet, raise `timeout` with `collect_switch_port_packets`, or leave it off. + +Every assigned device becomes a Netdata node: an organization with 2,000 devices adds 2,000 nodes. + + +## Setup + + +You can configure the **meraki** collector in two ways: + +| Method | Best for | How to | +|-----------------------|------------------------------------------------------------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------| +| [**UI**](#via-ui) | Fast setup without editing files | Go to **Nodes → Configure this node → Collectors → Jobs**, search for **meraki**, then click **+** to add a job. | +| [**File**](#via-file) | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit `go.d/meraki.conf` and add a job. | + +:::important + +UI configuration requires paid Netdata Cloud plan. + +::: + + +### Prerequisites + +#### Enable Dashboard API access for the organization + +API requests are rejected until the organization allows them. In Meraki Dashboard, open **Organization > Settings** and enable **Dashboard API access**. See [How to use the Meraki Dashboard API](https://documentation.meraki.com/Platform_Management/Dashboard_Administration/Operate_and_Maintain/How-Tos/How_to_Use_the_Cisco_Meraki_Dashboard_API). + + +#### Create an API key for a read-only administrator + +A Meraki API key has the permissions of the administrator who creates it. Use a Dashboard administrator account with read-only access to the organization, and generate an API key from that account's **My profile** page. Keep the key out of the configuration file: put it in an environment variable of the Netdata service or in a file readable by the `netdata` user. + +To verify the key, list the organizations it can see with the command shown for the `organization_id` option. + + +#### Allow the Agent's address if the organization restricts API access by IP + +This applies only when the organization limits Dashboard API access to specific source addresses. Add the public IP address the Agent's requests leave from; otherwise organization requests fail with HTTP 403. + + + +### Configuration + +#### Options + +Configure one organization per job. The following options can be defined globally: update_every, autodetection_retry. + +
+Config options + + + +| Group | Option | Description | Default | Required | +|:------|:-----|:------------|:--------|:---------:| +| **Target** | [url](#option-target-url) | URL of the Meraki Dashboard API endpoint. | https://api.meraki.com/api/v1 | no | +| | [organization_id](#option-target-organization-id) | Meraki organization ID to monitor. | | yes | +| **Authentication** | api_key | Meraki API key. Set either this or bearer_token_file. | | no | +| | [bearer_token_file](#option-authentication-bearer-token-file) | Path to a file containing the Meraki API key, reread for every request. Set either this or api_key. | | no | +| **Traffic** | [collect_switch_port_traffic](#option-traffic-collect-switch-port-traffic) | Collect the average traffic of every switch port, shown on its switch's node. | no | no | +| | [collect_switch_port_packets](#option-traffic-collect-switch-port-packets) | Collect the packet rates of every switch port, at one API request per switch per collection. | no | no | +| | [collect_appliance_uplink_traffic](#option-traffic-collect-appliance-uplink-traffic) | Collect the average traffic of each uplink of every MX and Z network, shown on the job's node or its virtual node. | no | no | +| **Collection** | update_every | Data collection interval, in seconds. | 300 | no | +| | autodetection_retry | How often to retry the initial connection when the job fails to start, in seconds. Zero disables retries. | 0 | no | +| | timeout | Complete collection or connection-check timeout, in seconds, including all pages and request pacing. | 60 | no | +| | vnode | Associates the organization and appliance uplink charts with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). Device nodes are created separately. | | no | +| **Transport** | [proxy_url](#option-transport-proxy-url) | HTTP proxy URL. Empty value uses environment proxy variables. | | no | +| | tls_ca | Path to a CA certificate file used to verify the server certificate. | | no | +| | tls_cert | Path to a client certificate file. Requires tls_key. | | no | +| | tls_key | Path to the client certificate key file. Requires tls_cert. | | no | +| | tls_skip_verify | Skip verification of the server certificate and hostname. | no | no | + + +##### url + +Use the API endpoint of the region that hosts the organization: + +| Region | URL | +|:-------|:----| +| Global (default) | `https://api.meraki.com/api/v1` | +| Canada | `https://api.meraki.ca/api/v1` | +| China | `https://api.meraki.cn/api/v1` | +| India | `https://api.meraki.in/api/v1` | +| United States FedRAMP | `https://api.gov-meraki.com/api/v1` | + +The URL must use HTTPS with the path exactly `/api/v1` (a prefix such as `/meraki/api/v1` is not accepted), without credentials, query or fragment. + +A private endpoint or reverse proxy in front of the API also works, with one condition. Meraki's redirects and next-page links point at Meraki hosts, and with a custom endpoint the collector follows them only within that endpoint. The proxy must therefore rewrite the `Location` and `Link` headers to its own address; otherwise every list longer than one page fails with `invalid pagination target`. + + + +##### organization_id + +The ID of the organization, not its name. The organizations an API key can see, with their IDs, are listed by the command below; for an organization in another region, replace the host with the one in `url`. + +```bash +curl -s -H "Authorization: Bearer $MERAKI_API_KEY" https://api.meraki.com/api/v1/organizations +``` + + + +##### bearer_token_file + +Use this when a secret manager rotates the key in place: the next request uses the new key without a restart. The file must be readable by the `netdata` user. + + + +##### collect_switch_port_traffic + +Adds two charts per port to each switch's node: sent and received kilobits/s from the latest interval Meraki has reported within the last 15 minutes, usually 5 minutes long, or a gap when it has reported none, and how old that interval is. + + + +##### collect_switch_port_packets + +Adds a chart of the sent and received packets/s of each port, counting every packet type, to each switch's node. Because it costs a request per switch, it is the option that decides `timeout` on large fleets; see Performance Impact. + + + +##### collect_appliance_uplink_traffic + +Adds a chart per network and uplink interface (for example `wan1`, `wan2` or `cellular`) with the sent and received kilobits/s of the 5 minutes that ended 5 minutes earlier, on the job's node or `vnode`. + + + +##### proxy_url + +If the proxy URL contains credentials, use a secret reference such as `${env:MERAKI_PROXY_URL}` instead of entering the authenticated URL directly into the form. + + +
+ + +#### via UI + +Configure the **meraki** collector from the Netdata web interface: + +1. Go to **Nodes**. +2. Select the node **where you want the meraki data-collection job to run** and click the :gear: (**Configure this node**). That node will run the data collection. +3. The **Collectors → Jobs** view opens by default. +4. In the Search box, type _meraki_ (or scroll the list) to locate the **meraki** collector. +5. Click the **+** next to the **meraki** collector to add a new job. +6. Fill in the job fields, then click **Test** to verify the configuration and **Submit** to save. + - **Test** validates the provided settings and checks the collector's startup prerequisites. Successful validation does not guarantee that every metric will be available during collection. + - If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest. + + +#### via File + +The configuration file name for this integration is `go.d/meraki.conf`. + +The file format is YAML. Generally, the structure is: + +```yaml +update_every: 1 +autodetection_retry: 0 +jobs: + - name: some_name1 + - name: some_name2 +``` +You can edit the configuration file using the [`edit-config`](/docs/netdata-agent/configuration#edit-configuration-files) script from the +Netdata [config directory](/docs/netdata-agent/configuration#locate-your-config-directory). + +```bash +cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata +sudo ./edit-config go.d/meraki.conf +``` + +##### Examples + +###### Basic + +Monitor one organization, with the API key read from an environment variable. + +
+Config + +```yaml +jobs: + - name: meraki + organization_id: "123456" + api_key: ${env:MERAKI_API_KEY} + +``` +
+ +###### Switch port and uplink traffic + +Also collect the traffic of every switch port and MX or Z uplink. + +
+Config + +```yaml +jobs: + - name: meraki + organization_id: "123456" + api_key: ${env:MERAKI_API_KEY} + collect_switch_port_traffic: yes + collect_appliance_uplink_traffic: yes + +``` +
+ +###### Switch port packets on a large fleet + +Also collect packet rates, which cost one request per switch. The longer `timeout` leaves room for about 1,500 switches. + +
+Config + +```yaml +jobs: + - name: meraki + organization_id: "123456" + api_key: ${env:MERAKI_API_KEY} + collect_switch_port_packets: yes + timeout: 180 + +``` +
+ +###### API key in a rotated file + +Read the key from a file that a secret manager rotates. The file is read again for every request. + +
+Config + +```yaml +jobs: + - name: meraki + organization_id: "123456" + bearer_token_file: /run/secrets/meraki_api_key + +``` +
+ +###### Regional API endpoint + +Monitor an organization hosted outside the global region, here Canada. + +
+Config + +```yaml +jobs: + - name: meraki-canada + url: https://api.meraki.ca/api/v1 + organization_id: "123456" + api_key: ${env:MERAKI_API_KEY} + +``` +
+ +###### Through an HTTP proxy + +Reach the API through an outbound proxy. + +
+Config + +```yaml +jobs: + - name: meraki + organization_id: "123456" + api_key: ${env:MERAKI_API_KEY} + proxy_url: http://proxy.example.com:3128 + +``` +
+ +###### Several organizations + +One job per organization. Each organization has its own API budget; the jobs share the per-IP budget. + +
+Config + +```yaml +jobs: + - name: meraki-hq + organization_id: "123456" + api_key: ${env:MERAKI_API_KEY} + + - name: meraki-retail + organization_id: "654321" + api_key: ${env:MERAKI_API_KEY} + +``` +
+ + + +## Alerts + +There are no alerts configured by default for this integration. + + + +## Metrics + +Metrics grouped by *scope*. + +The scope defines the instance that the metric belongs to. An instance is uniquely identified by a set of labels. + +- **Where charts appear.** The organization and uplink charts are on the node that runs the job, or on its virtual node when `vnode` is set. Device charts, switch port charts included, are on each device's own node, named after the device; `meraki-` followed by the serial when the device has no name; or `meraki-` followed by a generated ID when the name contains an apostrophe, backslash or line break. +- **Gaps, not offline or zero.** A device whose status is missing, unknown or reported for another network has no availability value for that collection; it is never reported offline because of missing data. Its inventory chart stays at 1 while the device is assigned. Likewise, a traffic value Meraki leaves out, or reports twice with different values, is a gap, not a zero. +- **Failed collections.** A failed inventory request, a timeout or a cancellation updates no chart. A failed traffic request leaves gaps only in its own charts, except an HTTP 429, after which no more traffic is requested in that collection. +- **Removed devices.** When a device leaves the inventory, its charts stop updating and become obsolete. Netdata keeps the node and its history. + + + +### Per organization + +The configured Meraki organization. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| organization_id | Meraki organization ID, for example `123456`. | +| organization_name | Meraki organization name. | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| meraki.organization_assigned_devices | Meraki Assigned Devices | assigned | devices | + + +### Per device + +One device assigned to a network of the organization, shown as its own node. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| organization_id | Meraki organization ID. | +| organization_name | Meraki organization name. | +| serial | Device serial number, for example `Q2XX-XXXX-XXXX`. | +| device_name | Device name in Dashboard; empty when unnamed. | +| model | Device model, for example `MS120-8`. | +| product_type | Meraki product type, for example `appliance`, `switch`, `wireless`, `camera`, `sensor` or `cellularGateway`. | +| network_id | ID of the network the device is assigned to. | +| network_name | Name of the network the device is assigned to. | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| meraki.device_assigned | Meraki Device Inventory Membership | assigned | devices | +| meraki.device_availability | Meraki Device Availability | alerting, dormant, offline, online | status | + + +### Per switch port + +One port of an assigned switch, on the switch's node, when `collect_switch_port_traffic` or `collect_switch_port_packets` is enabled. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| organization_id | Meraki organization ID. | +| organization_name | Meraki organization name. | +| serial | Device serial number, for example `Q2XX-XXXX-XXXX`. | +| device_name | Device name in Dashboard; empty when unnamed. | +| model | Device model, for example `MS120-8`. | +| product_type | Meraki product type, for example `appliance`, `switch`, `wireless`, `camera`, `sensor` or `cellularGateway`. | +| network_id | ID of the network the device is assigned to. | +| network_name | Name of the network the device is assigned to. | +| port_id | Port ID as Meraki reports it, usually the port number such as `1`; ports on a module also carry the slot and module type. | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| meraki.switch_port_traffic | Meraki Switch Port Traffic | received, sent | kilobits/s | +| meraki.switch_port_traffic_interval_age | Meraki Switch Port Traffic Interval Age | age | seconds | +| meraki.switch_port_packets | Meraki Switch Port Packets | received, sent | packets/s | + + +### Per appliance uplink + +One uplink interface of an MX or Z network, on the job's node or its virtual node, when `collect_appliance_uplink_traffic` is enabled. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| organization_id | Meraki organization ID. | +| organization_name | Meraki organization name. | +| network_id | ID of the MX or Z network. | +| network_name | Name of the MX or Z network. | +| interface | Uplink interface, for example `wan1`, `wan2` or `cellular`. | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| meraki.appliance_uplink_traffic | Meraki Appliance Uplink Traffic | received, sent | kilobits/s | + + + +## Troubleshooting + +### Diagnostics + +#### Debug Mode + +**Important**: Debug mode is not supported for data collection jobs created via the UI using the Dyncfg feature. + +To troubleshoot issues with the `meraki` collector, run the `go.d.plugin` with the debug option enabled. The output +should give you clues as to why the collector isn't working. + +- Navigate to the `plugins.d` directory, usually at `/usr/libexec/netdata/plugins.d/`. If that's not the case on + your system, open `netdata.conf` and look for the `plugins` setting under `[directories]`. + + ```bash + cd /usr/libexec/netdata/plugins.d/ + ``` + +- Switch to the `netdata` user. + + ```bash + sudo -u netdata -s + ``` + +- Run the `go.d.plugin` to debug the collector: + + ```bash + ./go.d.plugin -d -m meraki + ``` + + To debug a specific job: + + ```bash + ./go.d.plugin -d -m meraki -j jobName + ``` + +#### Getting Logs + +If you're encountering problems with the `meraki` collector, follow these steps to retrieve logs and identify potential issues: + +- **Run the command** specific to your system (systemd, non-systemd, or Docker container). +- **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. + +##### System with systemd + +Use the following command to view logs generated since the last Netdata service restart: + +```bash +journalctl _SYSTEMD_INVOCATION_ID="$(systemctl show --value --property=InvocationID netdata)" --namespace=netdata --grep meraki +``` + +##### System without systemd + +Locate the collector log file, typically at `/var/log/netdata/collector.log`, and use `grep` to filter for collector's name: + +```bash +grep meraki /var/log/netdata/collector.log +``` + +**Note**: This method shows logs from all restarts. Focus on the **latest entries** for troubleshooting current issues. + +##### Docker Container + +If your Netdata runs in a Docker container named "netdata" (replace if different), use this command: + +```bash +docker logs netdata 2>&1 | grep meraki +``` + +### Known Errors + +#### `operation`: HTTP status 401 + +**Cause** + +Meraki rejected the API key. It is mistyped, revoked, or belongs to a deleted administrator account. + +**Fix** + +Generate a new API key and update `api_key` and restart the job, or replace the contents of the file named by `bearer_token_file`, which is read again on the next request. + +#### `operation`: HTTP status 403 + +**Cause** + +The API key's owner lacks permission for the request, or the organization restricts API access by source IP and the Agent's address is not allowed. + +**Fix** + +Grant the key's owner read-only access to the organization and, if it restricts API access by IP, allow the Agent's public address. See the prerequisites. + +#### `operation`: HTTP status 404 + +**Cause** + +Meraki answers 404 when the API key cannot reach the organization at all. The organization ID is wrong, the key's owner has no access to it, or Dashboard API access is disabled for it. + +**Fix** + +Check `organization_id` against the organizations the key can see (see the `organization_id` option), grant the key's owner read-only access, and enable Dashboard API access for the organization. + +#### configured organization_id is not visible to the Meraki credential + +**Cause** + +The API key works, but the organization in `organization_id` is not among the organizations it can see. + +**Fix** + +Check `organization_id` against the organizations the key can see (see the `organization_id` option), or use an API key of an administrator of that organization. + +#### `operation`: HTTP status 429 + +**Cause** + +Meraki rate-limited the request. The budgets of 10 requests per second per organization and 100 per source IP address are shared with every other application and job using them. + +**Fix** + +The collector sends nothing until the `Retry-After` delay Meraki requested has passed. If this happens when the job starts, the job retries after that delay only when `autodetection_retry` is set. + +If it happens regularly, reduce the organization's other API usage, move other API clients off the Agent's address, or increase `update_every`. + + +#### Meraki API Retry-After delay has not elapsed + +**Cause** + +An earlier request was rate-limited and the wait Meraki requested is still running, so the collector skipped this collection without contacting the API. + +**Fix** + +No action is needed; collection resumes when the wait ends. If it recurs, see the HTTP status 429 entry. + +#### `operation`: HTTP status `5xx` + +**Cause** + +The Meraki API had a temporary failure, or a proxy in between could not reach it. + +**Fix** + +Usually none; the next collection tries again. If it persists, check Meraki's service status and, when `proxy_url` is set, the proxy. + +#### `operation`: HTTP request failed: `reason` + +**Cause** + +The request got no HTTP answer. The end of the message says why; for `context deadline exceeded`, see that entry. + +**Fix** + +| Reason contains | Check | +|:----------------|:------| +| `no such host` | DNS resolution of the API host on the Agent | +| `connection refused`, `i/o timeout`, `connection reset` | Firewall rules for outbound HTTPS (port 443) to the API host and the Meraki shard hosts | +| `proxyconnect` | `proxy_url`, or the proxy environment variables when `proxy_url` is empty | +| `x509:` or `tls:` | Certificate trust: set `tls_ca` when a proxy or private endpoint uses its own CA | +| `Meraki redirect` | The API or a proxy redirected the request to a host the collector does not trust; see the `url` option | + +To test the same path from the Agent host, preferably as the `netdata` user (replace the host with the one in `url` for another region): + +```bash +curl -sS -o /dev/null -w '%{http_code}\n' -H "Authorization: Bearer $MERAKI_API_KEY" https://api.meraki.com/api/v1/organizations +``` + + +#### context deadline exceeded + +**Cause** + +A collection or the startup check took longer than `timeout`. Every page counts toward it, and the collector sends at most 10 requests per second, so a very large organization or a slow network can run out of time. + +**Fix** + +Check connectivity to the API endpoint. If requests succeed but the organization cannot finish in time, increase `timeout`. With `collect_switch_port_packets`, every switch adds a request; raise `timeout` with the number of switches, or disable the option. + +#### `operation`: invalid pagination target + +**Cause** + +A next-page link pointed outside the endpoint in `url`. This happens when `url` is a proxy or private endpoint that passes Meraki's `Link` headers through unchanged, and only for lists longer than one page. + +**Fix** + +Configure the proxy to rewrite `Location` and `Link` headers to its own address, or set `url` to the Meraki API endpoint of the organization's region. + +#### `operation`: cannot prepare authenticated request + +**When** + +`bearer_token_file` is set. + +**Cause** + +The key file is missing, empty or not readable by the `netdata` user. + +**Fix** + +Check the path in `bearer_token_file`, that the file contains the API key, and that the `netdata` user can read it. + +#### `operation`: invalid JSON array response + +**Cause** + +The endpoint answered with something other than Meraki API data, typically because `url` points to another service or a proxy answered with its own page. + +**Fix** + +Set `url` to a Meraki API endpoint with the path `/api/v1` (see the `url` option), and check `proxy_url`. + +#### Meraki requires exactly one API key or bearer token file + +**Cause** + +Both authentication options are empty, both are set, or `api_key` contains a line break. + +**Fix** + +Set either `api_key` or `bearer_token_file` and clear the other. Make sure the key is on one line. + +#### Meraki base URL must be an HTTPS /api/v1 URL without credentials, query or fragment + +**Cause** + +`url` is not an HTTPS URL with the path `/api/v1`, or it contains a user name, password, query or fragment. + +**Fix** + +Use one of the regional endpoints listed for the `url` option, or your endpoint's HTTPS URL with the path `/api/v1`. + +#### organization_id must be a nonempty organization ID without surrounding whitespace + +**Cause** + +`organization_id` is empty, has leading or trailing spaces, or is `.` or `..`. + +**Fix** + +Set `organization_id` to the organization's ID, quoted as a string in YAML (`"123456"`). + +#### cannot initialize Meraki HTTP transport; check proxy and TLS configuration + +**Cause** + +`proxy_url` is not a valid URL, or a TLS file in `tls_ca`, `tls_cert` or `tls_key` cannot be read or parsed. + +**Fix** + +Check `proxy_url`, and that the TLS files exist, are readable by the `netdata` user and contain PEM data. + +#### tls_cert and tls_key must be configured together + +**Cause** + +Only one of the client certificate options is set. + +**Fix** + +Set both `tls_cert` and `tls_key`, or neither. + +#### Meraki assigned device has no serial + +**Cause** + +The assigned-device list from Meraki contained an entry without a serial number. The whole collection is dropped rather than shown with a device missing. + +**Fix** + +Usually temporary; the next collection reads the list again. If it persists, report it to Cisco Meraki support with the time of the error. + +#### conflicting Meraki assigned-device records + +**Cause** + +The assigned-device list listed the same serial twice with different details, typically because a device was renamed or moved while the pages were read. The whole collection is dropped. + +**Fix** + +Usually temporary; the next collection reads the list again. If it persists, report it to Cisco Meraki support. + +#### conflicting Meraki network records + +**Cause** + +The network list listed the same network ID twice with different names, typically because a network was renamed while the pages were read. The whole collection is dropped. + +**Fix** + +Usually temporary; the next collection reads the list again. If it persists, report it to Cisco Meraki support. + +#### conflicting Meraki organization records + +**Cause** + +The organization list listed the configured organization ID twice with different details. The whole collection is dropped. + +**Fix** + +Usually temporary; the next collection reads the list again. If it persists, report it to Cisco Meraki support. + +#### Meraki network belongs to a different organization + +**Cause** + +The network list for the configured organization contained a network of another organization. The whole collection is dropped. + +**Fix** + +Usually temporary; the next collection reads the list again. If it persists, report it to Cisco Meraki support. + +#### Device node shows inventory but no availability chart + +**Cause** + +Meraki did not report a usable status for the device in the last collection. Availability can lag a new assignment or a network move by one refresh. + +**Fix** + +Check the device's status in Dashboard and wait for the next 5-minute refresh. Run the collector in debug mode (see Diagnostics) to see how many devices had no usable status. + +#### Meraki `traffic` unavailable: `error` + +**Cause** + +A switch port traffic, switch port packets or appliance uplink traffic request failed. That traffic has gaps for this collection (for packets, only the ports of that switch); inventory, availability and the other traffic options still update. After an HTTP 429, no more traffic requests are sent in this collection. The warning is logged at most once an hour per kind of traffic. + +**Fix** + +Most messages continue with another error on this page, such as `getDeviceSwitchPortsStatusesPackets: HTTP status 403`; follow that entry. Inventory worked in the same collection, so an HTTP 403 or 404 here is about that traffic data, not about `organization_id`: check in Meraki Dashboard that the API key's administrator can see the switch or network and that it reports this data. + +#### Switch port or uplink traffic charts are missing + +**Cause** + +The traffic option is off, the organization has no switches or no MX or Z networks, or Meraki reported no usable value. Switch port traffic also has gaps while Meraki has reported no interval that ended in the last 15 minutes. + +**Fix** + +Enable `collect_switch_port_traffic`, `collect_switch_port_packets` or `collect_appliance_uplink_traffic`. If they are on, look for the traffic warning above in the logs, and compare with the traffic Meraki Dashboard shows for the switch or network. diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco NCS.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco NCS.mdx index 5ce75a79b..280372a7d 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco NCS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco NCS.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, ncs, snmp, router, npm] description: "Monitor Cisco NCS (router) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "650" +sidebar_position: "660" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-ncs" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-ncs" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Nexus.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Nexus.mdx index ab5562788..89bb512b3 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Nexus.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Nexus.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, nexus, snmp, switch, npm] description: "Monitor Cisco Nexus (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "660" +sidebar_position: "670" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-nexus" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-nexus" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco SB.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco SB.mdx index f5f84593f..9d21bac27 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco SB.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco SB.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, sb, snmp, smb, npm] description: "Monitor Cisco SB device metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "670" +sidebar_position: "680" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-sb" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-sb" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UC Virtual Machine.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UC Virtual Machine.mdx index 9ad568a1d..9afc99e2b 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UC Virtual Machine.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UC Virtual Machine.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, uc, virtual, machine, snmp, server, npm] description: "Monitor Cisco UC Virtual Machine (server) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "680" +sidebar_position: "690" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-uc-virtual-machine" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-uc-virtual-machine" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UCS.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UCS.mdx index ae3918bf4..197e4bce7 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UCS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco UCS.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, ucs, snmp, ucs, npm] description: "Monitor Cisco UCS server metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "690" +sidebar_position: "700" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-ucs" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-ucs" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco WAN Optimizer.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco WAN Optimizer.mdx index 279aa74a2..603f14d9d 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco WAN Optimizer.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco WAN Optimizer.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cisco, wan, optimizer, snmp, wave, npm] description: "Monitor Cisco WAN Optimizer (wave) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "700" +sidebar_position: "710" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cisco-wan-optimizer" slug: "/network-performance-monitoring/device-metrics/integrations/cisco-wan-optimizer" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler SDX.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler SDX.mdx index 29795baf9..44258684c 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler SDX.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler SDX.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [citrix, netscaler, sdx, snmp, loadbalancer, npm] description: "Monitor Citrix Netscaler SDX (loadbalancer) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "730" +sidebar_position: "740" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/citrix-netscaler-sdx" slug: "/network-performance-monitoring/device-metrics/integrations/citrix-netscaler-sdx" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler.mdx index b27827642..fdacf1402 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix Netscaler.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [citrix, netscaler, snmp, loadbalancer, npm] description: "Monitor Citrix Netscaler (loadbalancer) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "720" +sidebar_position: "730" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/citrix-netscaler" slug: "/network-performance-monitoring/device-metrics/integrations/citrix-netscaler" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix.mdx index 70c84d3c1..125a5098a 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Citrix.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [citrix, snmp, network device, npm] description: "Monitor Citrix (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "710" +sidebar_position: "720" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/citrix" slug: "/network-performance-monitoring/device-metrics/integrations/citrix" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cradlepoint.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cradlepoint.mdx index fc7c07d1f..ad1f57628 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cradlepoint.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cradlepoint.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cradlepoint, snmp, network device, npm] description: "Monitor Cradlepoint (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "740" +sidebar_position: "750" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cradlepoint" slug: "/network-performance-monitoring/device-metrics/integrations/cradlepoint" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cyberpower PDU.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cyberpower PDU.mdx index 5b6336629..8d9f270a1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cyberpower PDU.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cyberpower PDU.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [cyberpower, pdu, snmp, pdu, npm] description: "Monitor Cyberpower PDU (pdu) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "750" +sidebar_position: "760" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/cyberpower-pdu" slug: "/network-performance-monitoring/device-metrics/integrations/cyberpower-pdu" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell EMC Data Domain.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell EMC Data Domain.mdx index d4152ee6c..6d9626ec9 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell EMC Data Domain.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell EMC Data Domain.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, emc, data, domain, snmp, network device, npm] description: "Monitor Dell EMC Data Domain (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "770" +sidebar_position: "780" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell-emc-data-domain" slug: "/network-performance-monitoring/device-metrics/integrations/dell-emc-data-domain" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Force10.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Force10.mdx index 865e4018a..16ab22dc4 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Force10.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Force10.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, force10, snmp, switch, npm] description: "Monitor Dell Force10 (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "780" +sidebar_position: "790" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell-force10" slug: "/network-performance-monitoring/device-metrics/integrations/dell-force10" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell OS10.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell OS10.mdx index a9f2a8b71..3fba7be14 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell OS10.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell OS10.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, os10, snmp, switch, npm] description: "Monitor Dell OS10 (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "790" +sidebar_position: "800" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell-os10" slug: "/network-performance-monitoring/device-metrics/integrations/dell-os10" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Powerconnect.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Powerconnect.mdx index da3ceb31c..7369c9fac 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Powerconnect.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Powerconnect.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, powerconnect, snmp, switch, npm] description: "Monitor Dell Powerconnect (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "800" +sidebar_position: "810" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell-powerconnect" slug: "/network-performance-monitoring/device-metrics/integrations/dell-powerconnect" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Poweredge.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Poweredge.mdx index 448e0d1e4..ced3a3d9d 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Poweredge.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Poweredge.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, poweredge, snmp, server, npm] description: "Monitor Dell Poweredge (server) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "810" +sidebar_position: "820" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell-poweredge" slug: "/network-performance-monitoring/device-metrics/integrations/dell-poweredge" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Sonicwall.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Sonicwall.mdx index 1e11d99ff..aceee9b74 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Sonicwall.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell Sonicwall.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, sonicwall, snmp, firewall, npm] description: "Monitor Dell Sonicwall (firewall) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "820" +sidebar_position: "830" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell-sonicwall" slug: "/network-performance-monitoring/device-metrics/integrations/dell-sonicwall" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell.mdx index 7b088c7b4..466347b1b 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dell.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dell, snmp, network device, npm] description: "Monitor Dell (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "760" +sidebar_position: "770" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dell" slug: "/network-performance-monitoring/device-metrics/integrations/dell" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dialogic Media Gateway.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dialogic Media Gateway.mdx index 9b311359f..643dac965 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dialogic Media Gateway.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dialogic Media Gateway.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dialogic, media, gateway, snmp, network device, npm] description: "Monitor Dialogic Media Gateway (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "830" +sidebar_position: "840" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dialogic-media-gateway" slug: "/network-performance-monitoring/device-metrics/integrations/dialogic-media-gateway" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink DGS Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink DGS Switch.mdx index 5fa14544d..36ab55789 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink DGS Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink DGS Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dlink, dgs, switch, snmp, switch, npm] description: "Monitor Dlink DGS Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "850" +sidebar_position: "860" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dlink-dgs-switch" slug: "/network-performance-monitoring/device-metrics/integrations/dlink-dgs-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink.mdx index 7410c2bfb..325cf54f9 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Dlink.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [dlink, snmp, network device, npm] description: "Monitor Dlink (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "840" +sidebar_position: "850" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/dlink" slug: "/network-performance-monitoring/device-metrics/integrations/dlink" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton Epdu.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton Epdu.mdx index ef50e8752..365510b07 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton Epdu.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton Epdu.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [eaton, epdu, snmp, pdu, npm] description: "Monitor Eaton ePDU power distribution metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "860" +sidebar_position: "870" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/eaton-epdu" slug: "/network-performance-monitoring/device-metrics/integrations/eaton-epdu" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton UPS.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton UPS.mdx index 2f5dc3546..ec3bba41a 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton UPS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Eaton UPS.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [eaton, ups, snmp, ups, npm] description: "Monitor Eaton UPS power and battery metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "870" +sidebar_position: "880" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/eaton-ups" slug: "/network-performance-monitoring/device-metrics/integrations/eaton-ups" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Exagrid.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Exagrid.mdx index b0a70c8d4..39e2b70be 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Exagrid.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Exagrid.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [exagrid, snmp, storage, npm] description: "Monitor ExaGrid storage metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "880" +sidebar_position: "890" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/exagrid" slug: "/network-performance-monitoring/device-metrics/integrations/exagrid" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Extreme Switching.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Extreme Switching.mdx index fba71263a..e0cbdc86e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Extreme Switching.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Extreme Switching.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [extreme, switching, snmp, switch, npm] description: "Monitor Extreme Switching (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "890" +sidebar_position: "900" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/extreme-switching" slug: "/network-performance-monitoring/device-metrics/integrations/extreme-switching" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/F5 BIG IP.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/F5 BIG IP.mdx index 65da00cba..6807fc059 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/F5 BIG IP.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/F5 BIG IP.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [f5, big, ip, snmp, loadbalancer, npm] description: "Monitor F5 BIG IP (loadbalancer) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "900" +sidebar_position: "910" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/f5-big-ip" slug: "/network-performance-monitoring/device-metrics/integrations/f5-big-ip" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fireeye.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fireeye.mdx index 48d2531eb..ee281136f 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fireeye.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fireeye.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [fireeye, snmp, network device, npm] description: "Monitor Fireeye (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "910" +sidebar_position: "920" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/fireeye" slug: "/network-performance-monitoring/device-metrics/integrations/fireeye" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Appliance.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Appliance.mdx index e1b7b47cf..67f3091bd 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Appliance.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Appliance.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [fortinet, appliance, snmp, network device, npm] description: "Monitor Fortinet Appliance (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "930" +sidebar_position: "940" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/fortinet-appliance" slug: "/network-performance-monitoring/device-metrics/integrations/fortinet-appliance" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortigate.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortigate.mdx index 984ad3907..d212047de 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortigate.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortigate.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [fortinet, fortigate, snmp, network device, npm] description: "Monitor Fortinet Fortigate (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "940" +sidebar_position: "950" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/fortinet-fortigate" slug: "/network-performance-monitoring/device-metrics/integrations/fortinet-fortigate" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortiswitch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortiswitch.mdx index 2d2dbb16f..0ef210c41 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortiswitch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet Fortiswitch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [fortinet, fortiswitch, snmp, switch, npm] description: "Monitor Fortinet Fortiswitch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "950" +sidebar_position: "960" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/fortinet-fortiswitch" slug: "/network-performance-monitoring/device-metrics/integrations/fortinet-fortiswitch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet.mdx index 0abafa53d..96ee16868 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Fortinet.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [fortinet, snmp, network device, npm] description: "Monitor Fortinet (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "920" +sidebar_position: "930" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/fortinet" slug: "/network-performance-monitoring/device-metrics/integrations/fortinet" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic SNMP Device.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic SNMP Device.mdx index 6ecbc3aae..9a896fed0 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic SNMP Device.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic SNMP Device.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [generic, snmp, device, snmp, network device, npm] description: "Monitor Generic SNMP Device (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "960" +sidebar_position: "970" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/generic-snmp-device" slug: "/network-performance-monitoring/device-metrics/integrations/generic-snmp-device" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic UPS UPS-MIB.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic UPS UPS-MIB.mdx index f222185a1..42702b1f1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic UPS UPS-MIB.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Generic UPS UPS-MIB.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [generic, ups, (ups-mib), snmp, ups, npm] description: "Monitor Generic UPS (UPS-MIB) (ups) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "970" +sidebar_position: "980" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/generic-ups-ups-mib" slug: "/network-performance-monitoring/device-metrics/integrations/generic-ups-ups-mib" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Gigamon.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Gigamon.mdx index e3a4d173f..2014f46a7 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Gigamon.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Gigamon.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [gigamon, snmp, network device, npm] description: "Monitor Gigamon (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "980" +sidebar_position: "990" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/gigamon" slug: "/network-performance-monitoring/device-metrics/integrations/gigamon" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP H3C Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP H3C Switch.mdx index 74d5b3d62..54e8c7013 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP H3C Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP H3C Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hp, h3c, switch, snmp, switch, npm] description: "Monitor HP H3C Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "990" +sidebar_position: "1000" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hp-h3c-switch" slug: "/network-performance-monitoring/device-metrics/integrations/hp-h3c-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ICF Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ICF Switch.mdx index bb967d8ab..42563789b 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ICF Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ICF Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hp, icf, switch, snmp, switch, npm] description: "Monitor HP ICF Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1000" +sidebar_position: "1010" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hp-icf-switch" slug: "/network-performance-monitoring/device-metrics/integrations/hp-icf-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ILO.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ILO.mdx index 649144b6e..86912bbd9 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ILO.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP ILO.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hp, ilo, snmp, server, npm] description: "Monitor HP iLO server hardware metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1010" +sidebar_position: "1020" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hp-ilo" slug: "/network-performance-monitoring/device-metrics/integrations/hp-ilo" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP Ilo4.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP Ilo4.mdx index a8f78e7f9..6e58793d0 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HP Ilo4.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HP Ilo4.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hp, ilo4, snmp, server, npm] description: "Monitor HP iLO 4 server hardware metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1020" +sidebar_position: "1030" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hp-ilo4" slug: "/network-performance-monitoring/device-metrics/integrations/hp-ilo4" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Bladesystem Enclosure.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Bladesystem Enclosure.mdx index 2555200f4..5d993e4d0 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Bladesystem Enclosure.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Bladesystem Enclosure.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hpe, bladesystem, enclosure, snmp, network device, npm] description: "Monitor HPE Bladesystem Enclosure (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1030" +sidebar_position: "1040" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hpe-bladesystem-enclosure" slug: "/network-performance-monitoring/device-metrics/integrations/hpe-bladesystem-enclosure" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE MSA.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE MSA.mdx index 2a53c361f..16357fa80 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE MSA.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE MSA.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hpe, msa, snmp, storage, npm] description: "Monitor HPE MSA storage metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1040" +sidebar_position: "1050" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hpe-msa" slug: "/network-performance-monitoring/device-metrics/integrations/hpe-msa" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Nimble.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Nimble.mdx index 3f559b95e..255d81983 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Nimble.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Nimble.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hpe, nimble, snmp, storage, npm] description: "Monitor HPE Nimble (storage) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1050" +sidebar_position: "1060" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hpe-nimble" slug: "/network-performance-monitoring/device-metrics/integrations/hpe-nimble" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Proliant.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Proliant.mdx index 6b757995a..461cf2fa2 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Proliant.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/HPE Proliant.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [hpe, proliant, snmp, network device, npm] description: "Monitor HPE Proliant (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1060" +sidebar_position: "1070" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/hpe-proliant" slug: "/network-performance-monitoring/device-metrics/integrations/hpe-proliant" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Access Controllers.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Access Controllers.mdx index 3e995048e..311114aac 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Access Controllers.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Access Controllers.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [huawei, access, controllers, snmp, accesspoint, npm] description: "Monitor Huawei Access Controllers (accesspoint) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1080" +sidebar_position: "1090" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/huawei-access-controllers" slug: "/network-performance-monitoring/device-metrics/integrations/huawei-access-controllers" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Routers.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Routers.mdx index 958d741e7..c0e4323d4 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Routers.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Routers.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [huawei, routers, snmp, router, npm] description: "Monitor Huawei Routers (router) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1090" +sidebar_position: "1100" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/huawei-routers" slug: "/network-performance-monitoring/device-metrics/integrations/huawei-routers" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Switches.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Switches.mdx index b90731f91..4cd94d64f 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Switches.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei Switches.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [huawei, switches, snmp, switch, npm] description: "Monitor Huawei Switches (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1100" +sidebar_position: "1110" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/huawei-switches" slug: "/network-performance-monitoring/device-metrics/integrations/huawei-switches" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei.mdx index a00ddc7c2..fc88996e8 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Huawei.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [huawei, snmp, network device, npm] description: "Monitor Huawei (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1070" +sidebar_position: "1080" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/huawei" slug: "/network-performance-monitoring/device-metrics/integrations/huawei" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Datapower Gateway.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Datapower Gateway.mdx index 50e07f712..c197a6ea0 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Datapower Gateway.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Datapower Gateway.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ibm, datapower, gateway, snmp, network device, npm] description: "Monitor IBM Datapower Gateway (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1120" +sidebar_position: "1130" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ibm-datapower-gateway" slug: "/network-performance-monitoring/device-metrics/integrations/ibm-datapower-gateway" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Lenovo Server.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Lenovo Server.mdx index 935f3dff6..313b9c112 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Lenovo Server.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM Lenovo Server.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ibm, lenovo, server, snmp, server, npm] description: "Monitor IBM Lenovo Server (server) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1130" +sidebar_position: "1140" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ibm-lenovo-server" slug: "/network-performance-monitoring/device-metrics/integrations/ibm-lenovo-server" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM.mdx index 4fd3bc32f..691fd7089 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/IBM.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ibm, snmp, network device, npm] description: "Monitor IBM (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1110" +sidebar_position: "1120" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ibm" slug: "/network-performance-monitoring/device-metrics/integrations/ibm" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/IDRAC.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/IDRAC.mdx index 33edbfa0d..18a2c195b 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/IDRAC.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/IDRAC.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [idrac, snmp, server, npm] description: "Monitor Dell iDRAC server hardware metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1140" +sidebar_position: "1150" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/idrac" slug: "/network-performance-monitoring/device-metrics/integrations/idrac" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Infinera Coriant Groove.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Infinera Coriant Groove.mdx index 9367a6fd5..7b612e2eb 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Infinera Coriant Groove.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Infinera Coriant Groove.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [infinera, coriant, groove, snmp, network device, npm] description: "Monitor Infinera Coriant Groove (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1150" +sidebar_position: "1160" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/infinera-coriant-groove" slug: "/network-performance-monitoring/device-metrics/integrations/infinera-coriant-groove" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Infoblox Ipam.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Infoblox Ipam.mdx index 613dea9c7..ebfa33157 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Infoblox Ipam.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Infoblox Ipam.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [infoblox, ipam, snmp, network device, npm] description: "Monitor Infoblox Ipam (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1160" +sidebar_position: "1170" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/infoblox-ipam" slug: "/network-performance-monitoring/device-metrics/integrations/infoblox-ipam" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations Page 2.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations Page 2.mdx index f4d48f53b..5263d3a89 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations Page 2.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations Page 2.mdx @@ -17,6 +17,9 @@ description: "Browse Netdata integrations for Device Metrics / Integrations and import { Grid, Box, GridPagination } from '@site/src/components/Grid_integrations'; + + + diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations.mdx index 59abac068..9383f77f7 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Integrations.mdx @@ -207,6 +207,9 @@ import { Grid, Box, GridPagination } from '@site/src/components/Grid_integration + + + @@ -540,9 +543,6 @@ import { Grid, Box, GridPagination } from '@site/src/components/Grid_integration - - - diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Isilon.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Isilon.mdx index 77e83383d..9d50e7a47 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Isilon.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Isilon.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [isilon, snmp, storage, npm] description: "Monitor Dell Isilon storage metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1170" +sidebar_position: "1180" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/isilon" slug: "/network-performance-monitoring/device-metrics/integrations/isilon" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ixsystems Truenas.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ixsystems Truenas.mdx index 921c26103..7dec6425e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ixsystems Truenas.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ixsystems Truenas.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ixsystems, truenas, snmp, storage, npm] description: "Monitor Ixsystems Truenas (storage) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1180" +sidebar_position: "1190" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ixsystems-truenas" slug: "/network-performance-monitoring/device-metrics/integrations/ixsystems-truenas" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper EX.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper EX.mdx index 817f7da9d..6f2ec2a86 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper EX.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper EX.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [juniper, ex, snmp, switch, npm] description: "Monitor Juniper EX (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1200" +sidebar_position: "1210" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/juniper-ex" slug: "/network-performance-monitoring/device-metrics/integrations/juniper-ex" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper MX.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper MX.mdx index d4e367659..322357bdf 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper MX.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper MX.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [juniper, mx, snmp, router, npm] description: "Monitor Juniper MX (router) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1210" +sidebar_position: "1220" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/juniper-mx" slug: "/network-performance-monitoring/device-metrics/integrations/juniper-mx" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper Pulse Secure.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper Pulse Secure.mdx index 7d5617af4..067ce89cd 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper Pulse Secure.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper Pulse Secure.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [juniper, pulse, secure, snmp, vpn, npm] description: "Monitor Juniper Pulse Secure (vpn) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1220" +sidebar_position: "1230" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/juniper-pulse-secure" slug: "/network-performance-monitoring/device-metrics/integrations/juniper-pulse-secure" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper QFX.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper QFX.mdx index db4293a5c..b3feefc84 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper QFX.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper QFX.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [juniper, qfx, snmp, switch, npm] description: "Monitor Juniper QFX (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1230" +sidebar_position: "1240" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/juniper-qfx" slug: "/network-performance-monitoring/device-metrics/integrations/juniper-qfx" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper SRX.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper SRX.mdx index e4373842a..5a4784b5c 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper SRX.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper SRX.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [juniper, srx, snmp, firewall, npm] description: "Monitor Juniper SRX (firewall) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1240" +sidebar_position: "1250" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/juniper-srx" slug: "/network-performance-monitoring/device-metrics/integrations/juniper-srx" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper.mdx index 3a3fb3b5c..144d88142 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Juniper.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [juniper, snmp, network device, npm] description: "Monitor Juniper (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1190" +sidebar_position: "1200" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/juniper" slug: "/network-performance-monitoring/device-metrics/integrations/juniper" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Kyocera Printer.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Kyocera Printer.mdx index 97b6a53a7..4bdb80f9e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Kyocera Printer.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Kyocera Printer.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [kyocera, printer, snmp, printer, npm] description: "Monitor Kyocera Printer (printer) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1250" +sidebar_position: "1260" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/kyocera-printer" slug: "/network-performance-monitoring/device-metrics/integrations/kyocera-printer" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Linksys.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Linksys.mdx index ca4a3aaf2..4e2ae4abb 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Linksys.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Linksys.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [linksys, snmp, network device, npm] description: "Monitor Linksys (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1260" +sidebar_position: "1270" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/linksys" slug: "/network-performance-monitoring/device-metrics/integrations/linksys" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Mcafee WEB Gateway.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Mcafee WEB Gateway.mdx index fedd38053..afe1c8c1e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Mcafee WEB Gateway.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Mcafee WEB Gateway.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [mcafee, web, gateway, snmp, network device, npm] description: "Monitor Mcafee WEB Gateway (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1270" +sidebar_position: "1280" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/mcafee-web-gateway" slug: "/network-performance-monitoring/device-metrics/integrations/mcafee-web-gateway" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Meraki.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Meraki.mdx index 3e0d2bb08..390979157 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Meraki.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Meraki.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [meraki, snmp, network device, npm] description: "Monitor Meraki (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1280" +sidebar_position: "1290" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/meraki" slug: "/network-performance-monitoring/device-metrics/integrations/meraki" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Router.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Router.mdx index baef1c4a2..dc803ef63 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Router.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Router.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [mikrotik, router, snmp, network device, npm] description: "Monitor MikroTik Router (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1290" +sidebar_position: "1300" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/mikrotik-router" slug: "/network-performance-monitoring/device-metrics/integrations/mikrotik-router" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Switch.mdx index ff23a0d82..4f3111085 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/MikroTik Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [mikrotik, switch, snmp, switch, npm] description: "Monitor MikroTik Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1300" +sidebar_position: "1310" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/mikrotik-switch" slug: "/network-performance-monitoring/device-metrics/integrations/mikrotik-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/NEC Univerge.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/NEC Univerge.mdx index 288f4cca7..26c961578 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/NEC Univerge.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/NEC Univerge.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [nec, univerge, snmp, network device, npm] description: "Monitor NEC Univerge (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1320" +sidebar_position: "1330" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/nec-univerge" slug: "/network-performance-monitoring/device-metrics/integrations/nec-univerge" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nasuni Filer.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nasuni Filer.mdx index f0a755d2f..2d7e19742 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nasuni Filer.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nasuni Filer.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [nasuni, filer, snmp, storage, npm] description: "Monitor Nasuni Filer (storage) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1310" +sidebar_position: "1320" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/nasuni-filer" slug: "/network-performance-monitoring/device-metrics/integrations/nasuni-filer" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Net-SNMP Host.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Net-SNMP Host.mdx index 25ced4ba5..c7087b974 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Net-SNMP Host.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Net-SNMP Host.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [net-snmp, host, snmp, network device, npm] description: "Monitor Net-SNMP Host (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1330" +sidebar_position: "1340" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/net-snmp-host" slug: "/network-performance-monitoring/device-metrics/integrations/net-snmp-host" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netapp.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netapp.mdx index 6cd327b87..2aea4895d 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netapp.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netapp.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [netapp, snmp, network device, npm] description: "Monitor Netapp (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1340" +sidebar_position: "1350" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/netapp" slug: "/network-performance-monitoring/device-metrics/integrations/netapp" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Access Point.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Access Point.mdx index 689c8a93d..b7af0bef8 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Access Point.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Access Point.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [netgear, access, point, snmp, access point, npm] description: "Monitor Netgear Access Point (access point) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1360" +sidebar_position: "1370" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/netgear-access-point" slug: "/network-performance-monitoring/device-metrics/integrations/netgear-access-point" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Readynas.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Readynas.mdx index f7a498130..c5f6eec3e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Readynas.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Readynas.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [netgear, readynas, snmp, storage, npm] description: "Monitor Netgear Readynas (storage) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1370" +sidebar_position: "1380" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/netgear-readynas" slug: "/network-performance-monitoring/device-metrics/integrations/netgear-readynas" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Switch.mdx index 7466b1cf0..ec399debb 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [netgear, switch, snmp, switch, npm] description: "Monitor Netgear Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1380" +sidebar_position: "1390" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/netgear-switch" slug: "/network-performance-monitoring/device-metrics/integrations/netgear-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear.mdx index c78178f08..7d46c6ac4 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Netgear.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [netgear, snmp, network device, npm] description: "Monitor Netgear (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1350" +sidebar_position: "1360" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/netgear" slug: "/network-performance-monitoring/device-metrics/integrations/netgear" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nokia Service Router OS.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nokia Service Router OS.mdx index b1d104da3..bb77211ba 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nokia Service Router OS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nokia Service Router OS.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [nokia, service, router, os, snmp, router, npm] description: "Monitor Nokia Service Router OS (router) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1390" +sidebar_position: "1400" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/nokia-service-router-os" slug: "/network-performance-monitoring/device-metrics/integrations/nokia-service-router-os" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Cumulus Linux Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Cumulus Linux Switch.mdx index 4deb69227..d46ab9588 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Cumulus Linux Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Cumulus Linux Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [nvidia, cumulus, linux, switch, snmp, switch, npm] description: "Monitor Nvidia Cumulus Linux Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1410" +sidebar_position: "1420" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/nvidia-cumulus-linux-switch" slug: "/network-performance-monitoring/device-metrics/integrations/nvidia-cumulus-linux-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Mellanox Switchx.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Mellanox Switchx.mdx index 8a2a8afbf..64981a2f9 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Mellanox Switchx.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia Mellanox Switchx.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [nvidia, mellanox, switchx, snmp, switch, npm] description: "Monitor Nvidia Mellanox Switchx (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1420" +sidebar_position: "1430" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/nvidia-mellanox-switchx" slug: "/network-performance-monitoring/device-metrics/integrations/nvidia-mellanox-switchx" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia.mdx index 84a99c612..ee810d895 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Nvidia.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [nvidia, snmp, network device, npm] description: "Monitor Nvidia (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1400" +sidebar_position: "1410" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/nvidia" slug: "/network-performance-monitoring/device-metrics/integrations/nvidia" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Omron CJ Ethernet IP.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Omron CJ Ethernet IP.mdx index 2c9e2bc51..e5590987a 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Omron CJ Ethernet IP.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Omron CJ Ethernet IP.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [omron, cj, ethernet, ip, snmp, network device, npm] description: "Monitor Omron CJ Ethernet IP (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1430" +sidebar_position: "1440" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/omron-cj-ethernet-ip" slug: "/network-performance-monitoring/device-metrics/integrations/omron-cj-ethernet-ip" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Console Manager.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Console Manager.mdx index 257f27604..d83060b1e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Console Manager.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Console Manager.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [opengear, console, manager, snmp, network device, npm] description: "Monitor Opengear Console Manager (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1440" +sidebar_position: "1450" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/opengear-console-manager" slug: "/network-performance-monitoring/device-metrics/integrations/opengear-console-manager" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Infrastructure Manager.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Infrastructure Manager.mdx index 1b62b64c8..36f708fe5 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Infrastructure Manager.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Opengear Infrastructure Manager.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [opengear, infrastructure, manager, snmp, network device, npm] description: "Monitor Opengear Infrastructure Manager (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1450" +sidebar_position: "1460" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/opengear-infrastructure-manager" slug: "/network-performance-monitoring/device-metrics/integrations/opengear-infrastructure-manager" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/PF Sense.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/PF Sense.mdx index 3bd83916a..e87aa90aa 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/PF Sense.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/PF Sense.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [pf, sense, snmp, network device, npm] description: "Monitor PF Sense (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1500" +sidebar_position: "1510" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/pf-sense" slug: "/network-performance-monitoring/device-metrics/integrations/pf-sense" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Cloudgenix.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Cloudgenix.mdx index 4827b129e..7199847d5 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Cloudgenix.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Cloudgenix.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [palo, alto, cloudgenix, snmp, sd-wan, npm] description: "Monitor Palo Alto Cloudgenix (sd-wan) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1470" +sidebar_position: "1480" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/palo-alto-cloudgenix" slug: "/network-performance-monitoring/device-metrics/integrations/palo-alto-cloudgenix" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Networks PAN-OS.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Networks PAN-OS.mdx index b00b22172..a95d005e8 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Networks PAN-OS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto Networks PAN-OS.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [palo alto, pan-os, panos, firewall, bgp, ha, ipsec, licenses] description: "This collector monitors Palo Alto Networks PAN-OS firewalls." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" -sidebar_position: "1480" +sidebar_position: "1490" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/palo-alto-networks-pan-os" slug: "/network-performance-monitoring/device-metrics/integrations/palo-alto-networks-pan-os" --- @@ -26,7 +26,7 @@ Module: panos ## Overview This collector monitors Palo Alto Networks PAN-OS firewalls. -It collects read-only XML API telemetry for BGP, system status, HA, environment sensors, licenses, and IPsec SAs. +It collects read-only XML API telemetry for BGP, system status, HA, environment sensors, licenses, IPsec SAs, tunnels, and gateways. It gathers metrics by periodically running PAN-OS XML API operational commands through the pango SDK. @@ -50,6 +50,14 @@ This collector does not auto-detect PAN-OS firewalls. A job must be configured w The default collection interval is 60 seconds to keep polling load conservative on the PAN-OS management plane. +IPsec states describe local VPN state, not end-to-end reachability. On-demand VPNs may have no SA until traffic triggers negotiation. +Gateway `up` means an IKE SA with establishment and expiration times was reported; `down` means no matching SA was reported in a valid response. +Failed queries and incomplete SA data leave gateway-state gaps. +Configured tunnel and gateway charts remain visible during telemetry failures. Confirmed inventory removals retire their charts immediately. + +Gateway and tunnel states are independent. An IKE gateway can be `up` before its tunnel leaves `init`, and an IKEv1 tunnel can remain `active` after its parent IKE SA is cleared. +Tunnel flow states `active`, `inactive`, and `init` are preserved; `unknown` means an unrecognized nonempty state, and missing state data leaves a gap. + #### Performance Impact @@ -359,6 +367,42 @@ Metrics: | panos.ipsec.tunnel.sa_lifetime | IPsec Tunnel SA Remaining Lifetime | remaining_lifetime | seconds | +### Per IPsec tunnel state + +These metrics refer to one configured PAN-OS IPsec tunnel, whether or not it currently has an established SA. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| tunnel | Tunnel name. | +| tunnel_id | PAN-OS tunnel identifier. | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| panos.ipsec.tunnel.state | IPsec Tunnel State | active, inactive, init, unknown | state | + + +### Per IPsec gateway + +These metrics refer to one configured PAN-OS IKE gateway, whether or not it currently has an established IKE SA. + +Labels: + +| Label | Description | +|:-----------|:----------------| +| gateway | Gateway name. | +| ike_version | IKE version the gateway is configured for (`ikev1`, `ikev2`, or `unknown`). | + +Metrics: + +| Metric | Description | Dimensions | Unit | +|:------|:------------|:----------|:----| +| panos.ipsec.gateway.state | IPsec Gateway State | down, up | state | + + ### Per BGP peer These metrics refer to a single BGP peer on a PAN-OS virtual router or logical router. diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto.mdx index 1a3446a12..813a6d0b1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Palo Alto.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [palo, alto, snmp, firewall, npm] description: "Monitor Palo Alto (firewall) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1460" +sidebar_position: "1470" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/palo-alto" slug: "/network-performance-monitoring/device-metrics/integrations/palo-alto" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Peplink.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Peplink.mdx index a01e56a13..03cfb7cac 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Peplink.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Peplink.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [peplink, snmp, router, npm] description: "Monitor Peplink router metrics over SNMP with automatic profile recognition and no manual OID configuration." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1490" +sidebar_position: "1500" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/peplink" slug: "/network-performance-monitoring/device-metrics/integrations/peplink" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Raritan Dominion.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Raritan Dominion.mdx index f3a4b3d86..33615dd9a 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Raritan Dominion.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Raritan Dominion.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [raritan, dominion, snmp, network device, npm] description: "Monitor Raritan Dominion (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1510" +sidebar_position: "1520" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/raritan-dominion" slug: "/network-performance-monitoring/device-metrics/integrations/raritan-dominion" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Interceptor.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Interceptor.mdx index c927cff38..359c156e4 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Interceptor.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Interceptor.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [riverbed, interceptor, snmp, network device, npm] description: "Monitor Riverbed Interceptor (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1530" +sidebar_position: "1540" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/riverbed-interceptor" slug: "/network-performance-monitoring/device-metrics/integrations/riverbed-interceptor" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Steelhead.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Steelhead.mdx index 2f9e3d8dd..caf1b28cd 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Steelhead.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed Steelhead.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [riverbed, steelhead, snmp, network device, npm] description: "Monitor Riverbed Steelhead (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1540" +sidebar_position: "1550" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/riverbed-steelhead" slug: "/network-performance-monitoring/device-metrics/integrations/riverbed-steelhead" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed.mdx index cf736b4d6..8223994fe 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Riverbed.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [riverbed, snmp, network device, npm] description: "Monitor Riverbed (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1520" +sidebar_position: "1530" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/riverbed" slug: "/network-performance-monitoring/device-metrics/integrations/riverbed" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus Unleashed.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus Unleashed.mdx index a6ac88f8c..413ad286e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus Unleashed.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus Unleashed.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ruckus, unleashed, snmp, wireless lan controller, npm] description: "Monitor Ruckus Unleashed (wireless lan controller) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1560" +sidebar_position: "1570" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ruckus-unleashed" slug: "/network-performance-monitoring/device-metrics/integrations/ruckus-unleashed" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus WAP.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus WAP.mdx index e429fbdf2..fb3236d6c 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus WAP.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus WAP.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ruckus, wap, snmp, access point, npm] description: "Monitor Ruckus WAP (access point) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1570" +sidebar_position: "1580" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ruckus-wap" slug: "/network-performance-monitoring/device-metrics/integrations/ruckus-wap" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus.mdx index 2e100806a..1ecc95006 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ruckus.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ruckus, snmp, network device, npm] description: "Monitor Ruckus (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1550" +sidebar_position: "1560" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ruckus" slug: "/network-performance-monitoring/device-metrics/integrations/ruckus" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/SNMP devices.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/SNMP devices.mdx index 53dbcb910..cfdbc6c06 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/SNMP devices.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/SNMP devices.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [snmp, mib, oid, network, router, switch, firewall, ap, access point, wireless controller, wlc, wifi, vpn, pdu, ups, nas, san, printer, bgp, ospf, ucd, 3com, a10, alcatel, lucent, nokia, anue, apc, netbotz, arista, aruba, audiocodes, avaya, avocent, avtech, roomalert, barracuda, bluecat, brocade, cumulus, brother, chatsworth, checkpoint, chrysalis, cisco, cisco asa, cisco asr, cisco catalyst, cisco nexus, cisco ironport, cisco ics, cisco wlc, cisco ucs, meraki, citrix, netscaler, cradlepoint, cyberpower, dell, dell emc, poweredge, sonicwall, dialogic, dlink, d-link, eaton, exagrid, extreme, f5, big-ip, fireeye, bluecoat, proxysg, sgos, symantec, fortinet, fortigate, fortiswitch, gigamon, hp, hewlett packard, hp ilo, ilo, ilo4, hp h3c, hp icf, hpe, proliant, huawei, 3com huawei, ibm, datapower, lenovo, idrac, dell idrac, infinera, coriant, infoblox, isilon, ixsystems, truenas, juniper, junos, kyocera, linksys, mcafee, mikrotik, mellanox, nasuni, nec, net-snmp, netsnmp, netapp, netgear, readynas, omron, opengear, palo alto, cloudgenix, peplink, raritan, riverbed, ruckus, serveriron, server-iron, servertech, silverpeak, silver peak, edgeconnect, sinetica, sophos, synology, diskstation, tp-link, tplink, tripplite, tripp lite, ubiquiti, unifi, velocloud, vertiv, liebert, watchguard, western digital, wd, mycloud, zebra, zyxel] description: "This collector discovers and monitors any SNMP-enabled network device." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml FILE" -sidebar_position: "1640" +sidebar_position: "1650" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/snmp-devices" slug: "/network-performance-monitoring/device-metrics/integrations/snmp-devices" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Server Iron Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Server Iron Switch.mdx index 4782e03d2..db7a80c20 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Server Iron Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Server Iron Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [server, iron, switch, snmp, load balancer, npm] description: "Monitor Server Iron Switch (load balancer) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1580" +sidebar_position: "1590" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/server-iron-switch" slug: "/network-performance-monitoring/device-metrics/integrations/server-iron-switch" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu3.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu3.mdx index aab5036ea..a89169b5a 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu3.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu3.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [servertech, pdu3, snmp, pdu, npm] description: "Monitor Servertech Pdu3 (pdu) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1600" +sidebar_position: "1610" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/servertech-pdu3" slug: "/network-performance-monitoring/device-metrics/integrations/servertech-pdu3" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu4.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu4.mdx index 091b7908c..bb76fa8d0 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu4.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech Pdu4.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [servertech, pdu4, snmp, pdu, npm] description: "Monitor Servertech Pdu4 (pdu) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1610" +sidebar_position: "1620" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/servertech-pdu4" slug: "/network-performance-monitoring/device-metrics/integrations/servertech-pdu4" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech.mdx index 858f918eb..99abe3bb4 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Servertech.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [servertech, snmp, network device, npm] description: "Monitor Servertech (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1590" +sidebar_position: "1600" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/servertech" slug: "/network-performance-monitoring/device-metrics/integrations/servertech" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Silverpeak Edgeconnect.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Silverpeak Edgeconnect.mdx index 633f9291d..7ec92b67e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Silverpeak Edgeconnect.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Silverpeak Edgeconnect.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [silverpeak, edgeconnect, snmp, sd-wan, npm] description: "Monitor Silverpeak Edgeconnect (sd-wan) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1620" +sidebar_position: "1630" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/silverpeak-edgeconnect" slug: "/network-performance-monitoring/device-metrics/integrations/silverpeak-edgeconnect" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Sinetica Eagle I.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Sinetica Eagle I.mdx index eec4b6565..350321580 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Sinetica Eagle I.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Sinetica Eagle I.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [sinetica, eagle, i, snmp, network device, npm] description: "Monitor Sinetica Eagle I (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1630" +sidebar_position: "1640" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/sinetica-eagle-i" slug: "/network-performance-monitoring/device-metrics/integrations/sinetica-eagle-i" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Sophos XGS Firewall.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Sophos XGS Firewall.mdx index 8000958c3..cf8ba9f78 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Sophos XGS Firewall.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Sophos XGS Firewall.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [sophos, xgs, firewall, snmp, firewall, npm] description: "Monitor Sophos XGS Firewall (firewall) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1650" +sidebar_position: "1660" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/sophos-xgs-firewall" slug: "/network-performance-monitoring/device-metrics/integrations/sophos-xgs-firewall" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Synology Disk Station.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Synology Disk Station.mdx index 83c84c675..2bb16c89f 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Synology Disk Station.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Synology Disk Station.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [synology, disk, station, snmp, storage, npm] description: "Monitor Synology Disk Station (storage) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1660" +sidebar_position: "1670" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/synology-disk-station" slug: "/network-performance-monitoring/device-metrics/integrations/synology-disk-station" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/TP Link.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/TP Link.mdx index 6b3607dda..4f9af2ee0 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/TP Link.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/TP Link.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [tp, link, snmp, network device, npm] description: "Monitor TP Link (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1670" +sidebar_position: "1680" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/tp-link" slug: "/network-performance-monitoring/device-metrics/integrations/tp-link" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite PDU.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite PDU.mdx index 20ae16d2f..e91c44c86 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite PDU.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite PDU.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [tripplite, pdu, snmp, pdu, npm] description: "Monitor Tripplite PDU (pdu) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1690" +sidebar_position: "1700" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/tripplite-pdu" slug: "/network-performance-monitoring/device-metrics/integrations/tripplite-pdu" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite UPS.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite UPS.mdx index 9e821f844..b13155d4c 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite UPS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite UPS.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [tripplite, ups, snmp, ups, npm] description: "Monitor Tripplite UPS (ups) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1700" +sidebar_position: "1710" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/tripplite-ups" slug: "/network-performance-monitoring/device-metrics/integrations/tripplite-ups" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite.mdx index 307451d10..06839246a 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Tripplite.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [tripplite, snmp, network device, npm] description: "Monitor Tripplite (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1680" +sidebar_position: "1690" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/tripplite" slug: "/network-performance-monitoring/device-metrics/integrations/tripplite" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Net-SNMP Devices.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Net-SNMP Devices.mdx index 31bc2e603..1afd01a22 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Net-SNMP Devices.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Net-SNMP Devices.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ubiquiti, net-snmp, devices, snmp, network device, npm] description: "Monitor Ubiquiti Net-SNMP Devices (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1710" +sidebar_position: "1720" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ubiquiti-net-snmp-devices" slug: "/network-performance-monitoring/device-metrics/integrations/ubiquiti-net-snmp-devices" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi Security Gateway.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi Security Gateway.mdx index 80d5ee3c5..a16fcdb0f 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi Security Gateway.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi Security Gateway.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ubiquiti, unifi, security, gateway, snmp, network device, npm] description: "Monitor Ubiquiti Unifi Security Gateway (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1730" +sidebar_position: "1740" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ubiquiti-unifi-security-gateway" slug: "/network-performance-monitoring/device-metrics/integrations/ubiquiti-unifi-security-gateway" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi.mdx index c318fc297..411559a9c 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Ubiquiti Unifi.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [ubiquiti, unifi, snmp, network device, npm] description: "Monitor Ubiquiti Unifi (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1720" +sidebar_position: "1730" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/ubiquiti-unifi" slug: "/network-performance-monitoring/device-metrics/integrations/ubiquiti-unifi" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Velocloud Edge.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Velocloud Edge.mdx index f720dc97c..3864ffa8d 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Velocloud Edge.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Velocloud Edge.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [velocloud, edge, snmp, sd-wan, npm] description: "Monitor Velocloud Edge (sd-wan) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1740" +sidebar_position: "1750" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/velocloud-edge" slug: "/network-performance-monitoring/device-metrics/integrations/velocloud-edge" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Liebert AC.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Liebert AC.mdx index f9bc0d71b..b0df7d4c3 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Liebert AC.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Liebert AC.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [vertiv, liebert, ac, snmp, network device, npm] description: "Monitor Vertiv Liebert AC (network device) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1750" +sidebar_position: "1760" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/vertiv-liebert-ac" slug: "/network-performance-monitoring/device-metrics/integrations/vertiv-liebert-ac" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Watchdog.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Watchdog.mdx index 8156543b4..f438a1eaa 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Watchdog.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Vertiv Watchdog.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [vertiv, watchdog, snmp, sensor, npm] description: "Monitor Vertiv Watchdog (sensor) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1760" +sidebar_position: "1770" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/vertiv-watchdog" slug: "/network-performance-monitoring/device-metrics/integrations/vertiv-watchdog" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Vmware ESX.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Vmware ESX.mdx index 715b92ee5..6aa4ae321 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Vmware ESX.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Vmware ESX.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [vmware, esx, snmp, server, npm] description: "Monitor Vmware ESX (server) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1770" +sidebar_position: "1780" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/vmware-esx" slug: "/network-performance-monitoring/device-metrics/integrations/vmware-esx" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Watchguard.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Watchguard.mdx index 2aafc1295..66c020cd8 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Watchguard.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Watchguard.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [watchguard, snmp, firewall, npm] description: "Monitor Watchguard (firewall) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1780" +sidebar_position: "1790" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/watchguard" slug: "/network-performance-monitoring/device-metrics/integrations/watchguard" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Western Digital Mycloud EX2 Ultra.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Western Digital Mycloud EX2 Ultra.mdx index 4015f75f4..ac0b2a16e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Western Digital Mycloud EX2 Ultra.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Western Digital Mycloud EX2 Ultra.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [western, digital, mycloud, ex2, ultra, snmp, storage, npm] description: "Monitor Western Digital Mycloud EX2 Ultra (storage) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1790" +sidebar_position: "1800" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/western-digital-mycloud-ex2-ultra" slug: "/network-performance-monitoring/device-metrics/integrations/western-digital-mycloud-ex2-ultra" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Zebra Printer.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Zebra Printer.mdx index 410e0cc40..9875ed3c1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Zebra Printer.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Zebra Printer.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [zebra, printer, snmp, printer, npm] description: "Monitor Zebra Printer (printer) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1800" +sidebar_position: "1810" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/zebra-printer" slug: "/network-performance-monitoring/device-metrics/integrations/zebra-printer" --- diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Zyxel Switch.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Zyxel Switch.mdx index edc8b9626..c21f8eaa1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Zyxel Switch.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Zyxel Switch.mdx @@ -6,7 +6,7 @@ learn_rel_path: "Network Performance Monitoring/Device Metrics/Integrations" keywords: [zyxel, switch, snmp, switch, npm] description: "Monitor Zyxel Switch (switch) with Netdata over SNMP." message: "DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE" -sidebar_position: "1810" +sidebar_position: "1820" learn_link: "https://learn.netdata.cloud/docs/network-performance-monitoring/device-metrics/integrations/zyxel-switch" slug: "/network-performance-monitoring/device-metrics/integrations/zyxel-switch" --- diff --git a/docs/Welcome to Netdata/Monitor Anything.mdx b/docs/Welcome to Netdata/Monitor Anything.mdx index 015d071d1..ee5383562 100644 --- a/docs/Welcome to Netdata/Monitor Anything.mdx +++ b/docs/Welcome to Netdata/Monitor Anything.mdx @@ -685,6 +685,7 @@ Need a dedicated integration? [Submit a feature request](https://github.com/netd | [Cisco ISR 4431](/docs/network-performance-monitoring/device-metrics/integrations/cisco-isr-4431) | Monitor Cisco ISR 4431 (router) with Netdata over SNMP. | | [Cisco Legacy WLC](/docs/network-performance-monitoring/device-metrics/integrations/cisco-legacy-wlc) | Monitor Cisco Legacy WLC (wireless lan controller) with Netdata over SNMP. | | [Cisco Load Balancer](/docs/network-performance-monitoring/device-metrics/integrations/cisco-load-balancer) | Monitor Cisco Load Balancer (server load balancer) with Netdata over SNMP. | +| [Cisco Meraki](/docs/network-performance-monitoring/device-metrics/integrations/cisco-meraki) | Monitor device availability, switch port traffic and uplink traffic in a Cisco Meraki organization, with each device shown as its own Netdata node. | | [Cisco Meraki (Cloud Controller)](/docs/network-performance-monitoring/device-metrics/integrations/cisco-meraki-cloud-controller) | Monitor Cisco Meraki (Cloud Controller) (sd-wan) with Netdata over SNMP. | | [Cisco NCS](/docs/network-performance-monitoring/device-metrics/integrations/cisco-ncs) | Monitor Cisco NCS (router) with Netdata over SNMP. | | [Cisco Nexus](/docs/network-performance-monitoring/device-metrics/integrations/cisco-nexus) | Monitor Cisco Nexus (switch) with Netdata over SNMP. | diff --git a/ingest/generated_map.yaml b/ingest/generated_map.yaml index 1a5776bf0..d625a2d7d 100644 --- a/ingest/generated_map.yaml +++ b/ingest/generated_map.yaml @@ -1002,6 +1002,14 @@ description: .nan meta_yaml: .nan message: .nan +- custom_edit_url: https://github.com/netdata/netdata-cloud-onprem/edit/master/docs/learn.netdata.cloud/high-availability-and-disaster-recovery.md + sidebar_label: High Availability and Disaster Recovery + learn_status: Published + learn_rel_path: Netdata Cloud On-Prem + keywords: null + description: .nan + meta_yaml: .nan + message: .nan - custom_edit_url: https://github.com/netdata/netdata/edit/master/src/collectors/README.md sidebar_label: Collecting Metrics learn_status: Published @@ -6889,6 +6897,17 @@ meta_yaml: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/snmp/npm-catalog/metadata.yaml message: DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE NPM CATALOG metadata.yaml FILE +- custom_edit_url: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/meraki/README.md + sidebar_label: Cisco Meraki + learn_status: Published + learn_rel_path: Network Performance Monitoring/Device Metrics/Integrations + keywords: '[''cisco meraki'', ''meraki'', ''meraki dashboard'', ''meraki api'', + ''dashboard api'', ''cisco'']' + description: Monitor device availability, switch port traffic and uplink traffic + in a Cisco Meraki organization, with each device shown as its own Netdata node. + meta_yaml: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/meraki/metadata.yaml + message: DO NOT EDIT THIS FILE DIRECTLY, IT IS GENERATED BY THE COLLECTOR'S metadata.yaml + FILE - custom_edit_url: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/snmp/npm-catalog/integrations/cisco_meraki_cloud_controller.md sidebar_label: Cisco Meraki (Cloud Controller) learn_status: Published diff --git a/ingest/generated_sidebar_order.json b/ingest/generated_sidebar_order.json index eb85051c0..22ba40955 100644 --- a/ingest/generated_sidebar_order.json +++ b/ingest/generated_sidebar_order.json @@ -1,8 +1,8 @@ { "schema_version": 1, "source": "netdata/docs/.map/map.yaml", - "source_sha256": "5c613e8fa52bfee42b4c57d2ad18bf26ad3c1865ca5a5654eca0c66042d0c280", - "source_corpus_sha256": "b53976e3edd8e0efa7b18b4a2fb2378f5ef143f4cfddebbd6f7d3732c1efd348", + "source_sha256": "558fbc459bc4aa78c310e4685b8d937d0b49cffad6180303a1e12b701d8eaa2a", + "source_corpus_sha256": "9bb6acd1a441ce3c6703663b959f850af5c0d097cf6984d7e1364bbdf38be1ca", "order": [ { "parent_path": "Alerts & Notifications", @@ -1274,6 +1274,11 @@ "child_name": "Release Notes", "position": 90 }, + { + "parent_path": "Netdata Cloud On-Prem", + "child_name": "High Availability and Disaster Recovery", + "position": 100 + }, { "parent_path": "Netdata Cloud/Authentication & Authorization", "child_name": "Enterprise SSO Authentication", @@ -1810,5 +1815,5 @@ "position": 190 } ], - "full_ingest_identity_sha256": "48320677b9aed60f9545c60fb53cf7e11da693bcf844aedeafae6c7cbdf609d5" + "full_ingest_identity_sha256": "f5ebbba4d751644db267857325ff232e8cec66b7bb827a4dcb6f60bcb49568fc" } diff --git a/ingest/generated_sidebar_order.json.sha256 b/ingest/generated_sidebar_order.json.sha256 index 4873108c7..fcf6d13a7 100644 --- a/ingest/generated_sidebar_order.json.sha256 +++ b/ingest/generated_sidebar_order.json.sha256 @@ -1 +1 @@ -c83b0bf20a364de8401185bef7302223dfaacce39e3ea04af8c94319b472af56 generated_sidebar_order.json +f21cd0e4362d0afb744cd3aaab558f2a92d62b1bf045e915043bbd0e0dd38258 generated_sidebar_order.json diff --git a/ingest/one_commit_back_file-dict.yaml b/ingest/one_commit_back_file-dict.yaml index 30426af2b..1f6f539c9 100644 --- a/ingest/one_commit_back_file-dict.yaml +++ b/ingest/one_commit_back_file-dict.yaml @@ -12,6 +12,8 @@ learn_path: /docs/netdata-cloud-on-prem/mirroring-image-registry - custom_edit_url: https://github.com/netdata/netdata-cloud-onprem/edit/master/docs/learn.netdata.cloud/hardening-guide.md learn_path: /docs/netdata-cloud-on-prem/security-hardening-guide +- custom_edit_url: https://github.com/netdata/netdata-cloud-onprem/edit/master/docs/learn.netdata.cloud/high-availability-and-disaster-recovery.md + learn_path: /docs/netdata-cloud-on-prem/high-availability-and-disaster-recovery - custom_edit_url: https://github.com/netdata/netdata-cloud-onprem/edit/master/docs/learn.netdata.cloud/image-signature-verification.md learn_path: /docs/netdata-cloud-on-prem/container-image-signature-verification - custom_edit_url: https://github.com/netdata/netdata-cloud-onprem/edit/master/docs/learn.netdata.cloud/installation.md @@ -1268,6 +1270,8 @@ learn_path: /docs/collecting-metrics/collectors/storage-and-filesystems/megacli-megaraid - custom_edit_url: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/memcached/README.md learn_path: /docs/collecting-metrics/collectors/databases/memcached +- custom_edit_url: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/meraki/README.md + learn_path: /docs/network-performance-monitoring/device-metrics/integrations/cisco-meraki - custom_edit_url: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/mongodb/README.md learn_path: /docs/collecting-metrics/collectors/databases/mongodb - custom_edit_url: https://github.com/netdata/netdata/edit/master/src/go/plugin/go.d/collector/monit/README.md diff --git a/static/llms.txt b/static/llms.txt index f000fb14e..0a4dd604b 100644 --- a/static/llms.txt +++ b/static/llms.txt @@ -136,6 +136,7 @@ This index lists the Netdata documentation on learn.netdata.cloud in sidebar ord - [Mirroring image registry](https://learn.netdata.cloud/docs/netdata-cloud-on-prem/mirroring-image-registry): Mirror Netdata Cloud On-Prem container images from Amazon ECR into a private registry for restricted environments. - [Troubleshooting](https://learn.netdata.cloud/docs/netdata-cloud-on-prem/troubleshooting) - [Release Notes](https://learn.netdata.cloud/docs/netdata-cloud-on-prem/release-notes) +- [High Availability and Disaster Recovery](https://learn.netdata.cloud/docs/netdata-cloud-on-prem/high-availability-and-disaster-recovery) ## Collecting Metrics