From cab5b5205b0de9d86f9792921e5f450742de91f7 Mon Sep 17 00:00:00 2001 From: netdatabot <43409846+netdatabot@users.noreply.github.com> Date: Thu, 20 Aug 2026 15:52:29 +0000 Subject: [PATCH] Ingest new documentation --- .../Collectors/Databases/ClickHouse.mdx | 2 +- .../Databases/Microsoft SQL Server.mdx | 176 +++++++++++++++--- .../Ceph Prometheus.mdx | 23 ++- .../Installation/Linux/Linux.mdx | 2 +- .../Installation/Windows/Windows.mdx | 62 +++++- docs/Netdata Agent/Versions & Platforms.mdx | 27 +-- docs/Netdata Cloud On-Prem/Release Notes.mdx | 28 +++ .../Configuration/SNMP Profile Format.mdx | 41 +++- .../Integrations/Cisco 3850.mdx | 13 +- .../Device Metrics/Integrations/Cisco ASA.mdx | 13 +- .../Device Metrics/Integrations/Cisco ASR.mdx | 13 +- .../Integrations/Cisco Access Point.mdx | 13 +- .../Integrations/Cisco Catalyst WLC.mdx | 13 +- .../Integrations/Cisco Catalyst.mdx | 15 +- .../Integrations/Cisco Csr1000V.mdx | 13 +- .../Device Metrics/Integrations/Cisco ICM.mdx | 13 +- .../Integrations/Cisco ISR 4431.mdx | 13 +- .../Device Metrics/Integrations/Cisco ISR.mdx | 13 +- .../Integrations/Cisco Load Balancer.mdx | 13 +- .../Device Metrics/Integrations/Cisco NCS.mdx | 15 +- .../Integrations/Cisco Nexus.mdx | 13 +- .../Device Metrics/Integrations/Cisco SB.mdx | 13 +- .../Integrations/Cisco UC Virtual Machine.mdx | 13 +- .../Integrations/Cisco WAN Optimizer.mdx | 13 +- .../Device Metrics/Integrations/Cisco.mdx | 13 +- .../Integrations/SNMP devices.mdx | 16 +- .../Topologies/Discovery Methods.mdx | 4 +- ingest/generated_sidebar_order.json | 4 +- ingest/generated_sidebar_order.json.sha256 | 2 +- 29 files changed, 351 insertions(+), 261 deletions(-) diff --git a/docs/Collecting Metrics/Collectors/Databases/ClickHouse.mdx b/docs/Collecting Metrics/Collectors/Databases/ClickHouse.mdx index f8151ccf61..954e24d4b2 100644 --- a/docs/Collecting Metrics/Collectors/Databases/ClickHouse.mdx +++ b/docs/Collecting Metrics/Collectors/Databases/ClickHouse.mdx @@ -289,7 +289,7 @@ Metrics: | clickhouse.io_seeks | lseek function calls | lseek | ops/s | | clickhouse.io_file_opens | File opens | file_open | ops/s | | clickhouse.replicated_parts_current_activity | Replicated parts current activity | fetch, send, check | parts | -| clickhouse.replicas_max_absolute_dela | Replicas max absolute delay | replication_delay | seconds | +| clickhouse.replicas_max_absolute_delay | Replicas max absolute delay | replication_delay | seconds | | clickhouse.replicated_readonly_tables | Replicated tables in readonly state | read_only | tables | | clickhouse.replicated_data_loss | Replicated data loss | data_loss | events | | clickhouse.replicated_part_fetches | Replicated part fetches | successful, failed | fetches/s | diff --git a/docs/Collecting Metrics/Collectors/Databases/Microsoft SQL Server.mdx b/docs/Collecting Metrics/Collectors/Databases/Microsoft SQL Server.mdx index 70599713b7..9b7bb27eee 100644 --- a/docs/Collecting Metrics/Collectors/Databases/Microsoft SQL Server.mdx +++ b/docs/Collecting Metrics/Collectors/Databases/Microsoft SQL Server.mdx @@ -259,14 +259,14 @@ The following options can be defined globally: update_every, autodetection_retry | **Functions** | functions.top_queries.disabled | Disable the [top-queries](#top-queries) function. | no | no | | | functions.top_queries.timeout | Query timeout for top-queries function (seconds). Uses collector timeout if not set. | | no | | | functions.top_queries.limit | Maximum number of queries to return in the top-queries response. | 500 | no | -| | functions.top_queries.time_window_days | Number of days of Query Store data to analyze. Set to 0 to include all available data. Smaller values improve query performance but show less history. | 7 | no | +| | functions.top_queries.time_window_days | Number of days of Query Store data to analyze. Set to 0 to use the default (7), or -1 to include all available data. Smaller positive values improve query performance but show less history. | 7 | no | | | functions.deadlock_info.disabled | Disable the [deadlock-info](#deadlock-info) function. | no | no | | | functions.deadlock_info.timeout | Query timeout for deadlock-info function (seconds). Uses collector timeout if not set. | | no | -| | functions.deadlock_info.use_ring_buffer | Use ring_buffer instead of event_file for system_health session.

WARNING: Not recommended for production:
• Data cleared on failover/restart
• 4 MB capacity limit
• High CPU load during queries

Use only for Azure SQL Database without Blob Storage or testing. | no | no | +| | functions.deadlock_info.use_ring_buffer | Use the ring_buffer target instead of event_file for the built-in system_health session on SQL Server or Azure SQL Managed Instance.

WARNING:
• Data is cleared on failover/restart
• Capacity is limited
• XML parsing can increase query CPU

Azure SQL Database is not supported by deadlock-info because it has no built-in system_health session. | no | no | | | functions.error_info.disabled | Disable the [error-info](#error-info) function. | no | no | | | functions.error_info.timeout | Query timeout for error-info function (seconds). Uses collector timeout if not set. | | no | | | functions.error_info.session_name | Extended Events session name capturing error_reported events.
Must be created by administrator with event_file (recommended) or ring_buffer target. | netdata_errors | no | -| | functions.error_info.use_ring_buffer | Use ring_buffer instead of event_file for error events.

WARNING: Not recommended for production:
• Data cleared on failover/restart
• 4 MB capacity limit
• High CPU load during queries

Use only for Azure SQL Database without Blob Storage or testing. | no | no | +| | functions.error_info.use_ring_buffer | Use ring_buffer instead of event_file for error events.

WARNING:
• The session must remain running
• Data is cleared on failover/restart
• Capacity is limited
• XML parsing can increase query CPU

Useful when persistent event_file storage is unavailable, including Azure SQL Database without Blob Storage. | no | no | | **Virtual Node** | vnode | Associates this data collection job with a [Virtual Node](https://learn.netdata.cloud/docs/netdata-agent/configuration/organize-systems-metrics-and-alerts#virtual-nodes). | | no | @@ -380,7 +380,9 @@ jobs: ###### Azure SQL with service principal -Use Microsoft Entra service principal authentication for Azure SQL. +Use Microsoft Entra service principal authentication for Azure SQL. `top-queries` and `error-info` +operate in the database selected in the DSN; `deadlock-info` is unavailable on Azure SQL Database. +
Config @@ -403,7 +405,9 @@ jobs: ###### Azure SQL with managed identity -Use managed identity authentication (system-assigned by default). +Use managed identity authentication (system-assigned by default). `top-queries` and `error-info` +operate in the database selected in the DSN; `deadlock-info` is unavailable on Azure SQL Database. +
Config @@ -801,37 +805,58 @@ Query text is truncated at 4096 characters for display purposes. Columns are dyn |:-------|:------------| | Name | `Mssql:top-queries` | | Require Cloud | yes | -| Performance | Executes dynamic SQL to aggregate Query Store data across all enabled databases:
• Execution time depends on Query Store workload and number of monitored databases
• Default limit of 500 rows balances completeness with performance | +| Performance | On SQL Server and Azure SQL Managed Instance, executes dynamic SQL across all user databases with Query Store enabled.
On Azure SQL Database, queries only the database selected in the DSN.
• Execution time depends on Query Store workload, history window, and number of queried databases
• Default limit of 500 rows balances completeness with performance | | Security | Query text may contain unmasked literal values including potentially sensitive data:
• Personal information in WHERE clauses or INSERT values
• Business data and internal identifiers
• Access should be restricted to authorized personnel only | -| Availability | Available when:
• The collector has successfully connected to SQL Server
• Query Store is enabled on at least one user database
• Returns HTTP 503 if collector is still initializing
• Returns HTTP 500 if the query fails
• Returns HTTP 504 if the query times out | +| Availability | Available when:
• The collector has successfully connected to an engine that exposes Query Store (SQL Server 2016 (13.x) and later, Azure SQL Managed Instance, or Azure SQL Database)
• On SQL Server/Managed Instance, Query Store is enabled on at least one user database; on Azure SQL Database, it is enabled in the database selected in the DSN
• Returns HTTP 403 when required permissions are missing
• Returns HTTP 499 when the caller cancels the request
• Returns HTTP 503 if the collector is still initializing, the server does not expose Query Store, or no applicable database has Query Store enabled
• Returns HTTP 500 if the query fails
• Returns HTTP 504 if the query times out | #### Prerequisites ##### Enable Query Store -Query Store must be enabled on each database you want to monitor. +Query Store must be enabled on each database you want to inspect. SQL Server and Azure SQL Managed +Instance query all enabled user databases. Azure SQL Database queries only the database selected in +the collector DSN. -1. Verify Query Store is enabled on your databases: +1. Verify Query Store state: ```sql + -- SQL Server and Azure SQL Managed Instance SELECT name, is_query_store_on FROM sys.databases WHERE name NOT IN ('master', 'tempdb', 'model', 'msdb'); + + -- Azure SQL Database (run in the database selected in the DSN) + SELECT actual_state_desc + FROM sys.database_query_store_options; ``` -2. Enable Query Store on databases where it is disabled: +2. Enable Query Store where it is disabled: ```sql ALTER DATABASE [YourDatabaseName] SET QUERY_STORE = ON; ``` -3. Enable the function in Netdata collector config: +3. Grant the monitoring account the permissions required by your engine: + + On SQL Server/Managed Instance, map the login to a database user in every queried user database + before granting the database permission. On Azure SQL Database, grant the permission to the + database principal used by the collector connection. - ```yaml - jobs: - - name: local - dsn: "sqlserver://user:pass@localhost:1433" - query_store_function_enabled: true + ```sql + -- SQL Server 2022+ and Azure SQL Managed Instance 2022+ + GRANT VIEW SERVER PERFORMANCE STATE TO [netdata_user]; + USE [YourDatabaseName]; + CREATE USER [netdata_user] FOR LOGIN [netdata_user]; -- once per database + GRANT VIEW DATABASE PERFORMANCE STATE TO [netdata_user]; + + -- SQL Server 2016-2019 and corresponding Managed Instance versions + GRANT VIEW SERVER STATE TO [netdata_user]; + USE [YourDatabaseName]; + CREATE USER [netdata_user] FOR LOGIN [netdata_user]; -- once per database + GRANT VIEW DATABASE STATE TO [netdata_user]; + + -- Azure SQL Database (run in the database selected in the DSN) + GRANT VIEW DATABASE PERFORMANCE STATE TO [netdata_user]; ``` :::info @@ -839,6 +864,7 @@ Query Store must be enabled on each database you want to monitor. - Query Store is available in SQL Server 2016+ and Azure SQL Database - Requires ALTER DATABASE permission to enable Query Store - System databases (master, tempdb, model, msdb) are excluded from queries +- `top-queries` is enabled by default; set `functions.top_queries.disabled: true` only to disable it ::: @@ -943,9 +969,9 @@ Query text and wait resource strings are truncated at 4096 characters for displa |:-------|:------------| | Name | `Mssql:deadlock-info` | | Require Cloud | yes | -| Performance | Executes on-demand queries against the `system_health` ring buffer:
• Not part of regular metric collection
• Overhead is limited to function execution time and XML parsing | +| Performance | Executes on-demand queries against the selected `system_health` event_file or ring_buffer target:
• Not part of regular metric collection
• Overhead is limited to function execution time and XML parsing | | Security | Query text and wait resource strings may include unmasked literal values including sensitive data (PII/secrets):
• SQL literals such as emails, IDs, or tokens
• Schema and table names that may be sensitive in some environments
• Restrict dashboard access to authorized personnel only | -| Availability | Available when:
• The collector has successfully connected to SQL Server
• `deadlock_info_function_enabled` is true
• The account has `VIEW SERVER STATE` permission
• Returns HTTP 200 with empty data when no deadlock is found
• Returns HTTP 403 when permission is missing
• Returns HTTP 500 if the query fails
• Returns HTTP 561 when the deadlock graph cannot be parsed
• Returns HTTP 503 if the collector is still initializing or the function is disabled
• Returns HTTP 504 if the query times out | +| Availability | Available on SQL Server and Azure SQL Managed Instance when:
• The collector has successfully connected
• `functions.deadlock_info.disabled` is false
• SQL Server 2022+ has `VIEW SERVER PERFORMANCE STATE`; older versions have `VIEW SERVER STATE`
• Azure SQL Database returns HTTP 503 because it has no built-in `system_health` session
• Returns HTTP 200 with empty data when no deadlock is found
• Returns HTTP 403 when permission is missing
• Returns HTTP 499 when the caller cancels the request
• Returns HTTP 500 if the query fails
• Returns HTTP 561 when the deadlock graph cannot be parsed
• Returns HTTP 503 if the collector is still initializing, the function is disabled, or the engine is Azure SQL Database
• Returns HTTP 504 if the query times out | #### Prerequisites @@ -979,9 +1005,10 @@ Parsed deadlock participants from the latest detected deadlock event. Each row r Retrieves recent SQL errors from a user-managed Extended Events session that captures `sqlserver.error_reported` with both the `sql_text` and `query_hash` actions. -The session must be created by an administrator and include an `event_file` target. Netdata reads the event file -and returns recent error events with error number, message, and SQL text. The `query_hash` action is required for -reliable mapping into `top-queries` (query text fallback is best-effort). +The session must be created by an administrator and include either an `event_file` target (the default) or a +`ring_buffer` target when `functions.error_info.use_ring_buffer` is enabled. Netdata returns recent error events +with error number, message, and SQL text. The `query_hash` action is required for reliable mapping into +`top-queries` (query text fallback is best-effort). Use cases: - Identify recent query errors and their messages @@ -993,31 +1020,116 @@ Use cases: |:-------|:------------| | Name | `Mssql:error-info` | | Require Cloud | yes | -| Performance | Executes on-demand queries against the configured Extended Events event file:
• Not part of regular metric collection
• Overhead is limited to function execution time | +| Performance | Executes on-demand queries against the configured Extended Events target:
• Not part of regular metric collection
• event_file reads scan and parse all retained files before returning the newest rows
• The recommended 6 MB file size and three rollover files keep the conservative filesystem scan envelope near 24 MB (current file plus rollovers)
• Existing operator-managed sessions keep their own retention settings; the collector does not alter or reject them | | Security | Error messages and query text may include unmasked literal values including sensitive data (PII/secrets):
• Restrict dashboard access to authorized personnel only | -| Availability | Available when:
• The collector has successfully connected to SQL Server
• `error_info_function_enabled` is true
• The Extended Events session exists and has an event_file target
• The account has `VIEW SERVER STATE` permission
• Returns HTTP 200 with empty data when no errors are found
• Returns HTTP 403 when permission is missing
• Returns HTTP 500 if the query fails
• Returns HTTP 503 if the session is not enabled or the function is disabled
• Returns HTTP 504 if the query times out | +| Availability | Available on SQL Server, Azure SQL Managed Instance, and Azure SQL Database when:
• The collector has successfully connected
• `functions.error_info.disabled` is false
• The session is server-scoped on SQL Server/Managed Instance and database-scoped in the Azure SQL Database selected in the DSN
• When `functions.error_info.use_ring_buffer` is false, the session has an event_file target. Its configured `filename` is resolved from catalog metadata, so it need not match the session name or be running
• When `functions.error_info.use_ring_buffer` is true, the session is running and has a ring_buffer target
• SQL Server 2022+/Managed Instance 2022+ has `VIEW SERVER PERFORMANCE STATE`; older SQL Server has `VIEW SERVER STATE`; Azure SQL Database event_file has `VIEW DATABASE PERFORMANCE STATE`, while ring_buffer has `VIEW DATABASE STATE`
• Returns HTTP 200 with empty data when no errors are found
• Returns HTTP 403 when permission is missing
• Returns HTTP 499 when the caller cancels the request
• Returns HTTP 500 if the query fails
• Returns HTTP 503 if the selected target is unavailable or the function is disabled
• Returns HTTP 504 if the query times out | #### Prerequisites ##### Create Extended Events session for error capture -Create an Extended Events session that captures `sqlserver.error_reported` with `sql_text` and `query_hash` actions: +Create an Extended Events session that captures `sqlserver.error_reported` with `sql_text` and +`query_hash` actions. Choose the engine scope and target that match your deployment and +`functions.error_info.use_ring_buffer` setting. + +**SQL Server and Azure SQL Managed Instance — event_file (default):** ```sql --- Create the Extended Events session with event_file target CREATE EVENT SESSION [netdata_errors] ON SERVER ADD EVENT sqlserver.error_reported( ACTION(sqlserver.sql_text, sqlserver.query_hash) ) -ADD TARGET package0.event_file(SET filename=N'netdata_errors'); +ADD TARGET package0.event_file( + SET filename=N'netdata_errors', + max_file_size=6, + max_rollover_files=3 +); GO --- Start the session ALTER EVENT SESSION [netdata_errors] ON SERVER STATE = START; GO +``` + +Netdata resolves the configured filename from catalog metadata and can read retained event files +after the session stops. The 6 MB file size and three rollover files preserve recent history while +bounding the amount of retained XML that one request must scan. These settings affect only a session +created from this example; Netdata does not modify existing sessions. + +**SQL Server and Azure SQL Managed Instance — ring_buffer:** + +```sql +CREATE EVENT SESSION [netdata_errors] ON SERVER +ADD EVENT sqlserver.error_reported( + ACTION(sqlserver.sql_text, sqlserver.query_hash) +) +ADD TARGET package0.ring_buffer +WITH (STARTUP_STATE = ON); +GO + +ALTER EVENT SESSION [netdata_errors] ON SERVER STATE = START; +GO +``` + +Set `functions.error_info.use_ring_buffer: true`. The session starts automatically after restart or +failover, but events previously held in memory are lost. + +**Azure SQL Database — event_file (default):** + +Create the required database-scoped credential and grant the Database Engine access to an Azure +Storage container first. See Microsoft's [event_file setup guide](https://learn.microsoft.com/en-us/azure/azure-sql/database/xevent-code-event-file). + +```sql +-- Run in the database selected in the collector DSN. +CREATE EVENT SESSION [netdata_errors] ON DATABASE +ADD EVENT sqlserver.error_reported( + ACTION(sqlserver.sql_text, sqlserver.query_hash) +) +ADD TARGET package0.event_file( + SET filename=N'https://.blob.core.windows.net//netdata_errors.xel', + max_file_size=6, + max_rollover_files=3 +); +GO + +ALTER EVENT SESSION [netdata_errors] ON DATABASE STATE = START; +GO +``` --- Grant required permission +Azure Storage rollover retention is currently a preview feature and requires creating a new event +session with `max_rollover_files`. Existing sessions are not migrated automatically. + +**Azure SQL Database — ring_buffer:** + +```sql +-- Run in the database selected in the collector DSN. +CREATE EVENT SESSION [netdata_errors] ON DATABASE +ADD EVENT sqlserver.error_reported( + ACTION(sqlserver.sql_text, sqlserver.query_hash) +) +ADD TARGET package0.ring_buffer +WITH (STARTUP_STATE = ON); +GO + +ALTER EVENT SESSION [netdata_errors] ON DATABASE STATE = START; +GO +``` + +Set `functions.error_info.use_ring_buffer: true`. The database-scoped session starts automatically +after restart, failover, or maintenance, but events previously held in memory are lost. + +```sql +-- SQL Server 2022+ and Azure SQL Managed Instance 2022+ +GRANT VIEW SERVER PERFORMANCE STATE TO [netdata_user]; + +-- SQL Server 2019 and earlier GRANT VIEW SERVER STATE TO [netdata_user]; + +-- Azure SQL Database (run in the database selected in the DSN) +-- event_file target +GRANT VIEW DATABASE PERFORMANCE STATE TO [netdata_user]; + +-- ring_buffer target (also satisfies the catalog permission) +GRANT VIEW DATABASE STATE TO [netdata_user]; ``` If you use a different session name, set it in the collector config: @@ -1026,7 +1138,9 @@ If you use a different session name, set it in the collector config: jobs: - name: local dsn: "sqlserver://user:pass@localhost:1433" - error_info_session_name: your_session_name + functions: + error_info: + session_name: your_session_name ``` @@ -1131,5 +1245,5 @@ Ensure SQL Server is configured for mixed mode authentication if using SQL login ### Permission denied -The monitoring user needs VIEW SERVER STATE permission. -Grant it with: `GRANT VIEW SERVER STATE TO netdata_user;` +Base metric collection needs `VIEW SERVER STATE`. Functions can require additional version-specific +permissions; see each Function's prerequisites below. diff --git a/docs/Collecting Metrics/Collectors/Storage and Filesystems/Ceph Prometheus.mdx b/docs/Collecting Metrics/Collectors/Storage and Filesystems/Ceph Prometheus.mdx index 9e1442edb4..d92ffb81be 100644 --- a/docs/Collecting Metrics/Collectors/Storage and Filesystems/Ceph Prometheus.mdx +++ b/docs/Collecting Metrics/Collectors/Storage and Filesystems/Ceph Prometheus.mdx @@ -34,14 +34,17 @@ The built-in profile separates cluster-wide MGR health, quorum, capacity, placem from host-local `ceph-exporter` daemon availability and MON, MGR, OSD, and RGW performance. Optional branches cover CephFS/MDS and CephFS Mirror, RBD images, RBD Mirror, SMB, NVMe-oF, RGW user/bucket/topic/cache/multisite and dmClock scheduling, RocksDB binned caches, external block devices, and Ceph client I/O across Reef 18.2.8, Squid 19.2.5, -and Tentacle 20.2.2. PG state flags and RGW global/user/bucket views are overlapping diagnostic populations and are -not additive totals. Profile relabeling turns dynamic MDS-client, librbd ImageCtx/PWL, ObjectCacher, objecter, RocksDB -cache, Finisher, Throttle, KernelDevice, mClock, messenger, RDMA, DPDK, and service-identity family names into stable -profile inputs while preserving their source keys as identity labels. The source-complete profile materializes the -entire declared release/producer union with zero generic fallback. Unknown future Ceph families remain visible -through generic fallback until their source semantics can be curated; generic visibility is a forward-compatibility -guard, not evidence that a known source family was fully modeled. The profile drops only the source-proven -raw MGR RGW source-zone aliases because the stable normalized family is already charted. +and Tentacle 20.2.2. On Tentacle, the endpoints also expose primary-OSD PG-rebuild duration, while the MGR additionally +exposes cephadm node-proxy CPU, memory, storage, cooling, temperature, and per-component health metrics. Firmware +remains source metadata and is not charted because Ceph exposes it as an info family. PG state flags and RGW +global/user/bucket views are overlapping diagnostic populations and are not additive totals. Profile relabeling +turns dynamic MDS-client, librbd ImageCtx/PWL, ObjectCacher, objecter, RocksDB cache, Finisher, Throttle, KernelDevice, +mClock, messenger, RDMA, DPDK, and service-identity family names into stable profile inputs while preserving their +source keys as identity labels. The source-complete profile materializes the entire declared release/producer union +with zero generic fallback. Unknown future Ceph families remain visible through generic fallback until their source +semantics can be curated; generic visibility is a forward-compatibility guard, not evidence that a known source +family was fully modeled. The profile drops only the source-proven raw MGR RGW source-zone aliases because the stable +normalized family is already charted. The chart model follows the producer's source lifecycle rather than relying on Prometheus wire type alone. Current populations that Ceph increments and decrements remain absolute, while cumulative work published through gauges is @@ -102,7 +105,9 @@ UI configuration requires paid Netdata Cloud plan. Enable the [Ceph MGR Prometheus module](https://docs.ceph.com/en/latest/mgr/prometheus/) for cluster metrics or deploy the official `ceph-exporter` for host-local daemon performance metrics. The stock profile supports the default priority threshold and the complete priority-0 surface; use `exporter_prio_limit=0` when those diagnostic -counters are required and size the job limits for the resulting series count. +counters are required and size the job limits for the resulting series count. When cephadm node-proxy hardware +reporting is enabled, hardware series scale with the cluster-wide component inventory; size both +`max_time_series` and `max_time_series_per_metric` for that surface. diff --git a/docs/Netdata Agent/Installation/Linux/Linux.mdx b/docs/Netdata Agent/Installation/Linux/Linux.mdx index 5c31887498..0cf17bd15f 100644 --- a/docs/Netdata Agent/Installation/Linux/Linux.mdx +++ b/docs/Netdata Agent/Installation/Linux/Linux.mdx @@ -127,7 +127,7 @@ The user running the script needs write and execute permissions in the temporary Before running the installation script, you can verify its integrity using the following command: ```bash -[ "8c1033d55647703bcea79e2de95d3f04" = "$(curl -Ss https://get.netdata.cloud/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID" +[ "0643708c33f613ea078ee711b25801ae" = "$(curl -Ss https://get.netdata.cloud/kickstart.sh | md5sum | cut -d ' ' -f 1)" ] && echo "OK, VALID" || echo "FAILED, INVALID" ``` If the script is valid, this command will return `OK, VALID`. We recommend verifying script integrity before installation, especially in production environments. diff --git a/docs/Netdata Agent/Installation/Windows/Windows.mdx b/docs/Netdata Agent/Installation/Windows/Windows.mdx index 5e62fc7dcc..fe300cdc03 100644 --- a/docs/Netdata Agent/Installation/Windows/Windows.mdx +++ b/docs/Netdata Agent/Installation/Windows/Windows.mdx @@ -60,11 +60,15 @@ Use silent mode to deploy Netdata without user interaction. Run the command prom | `/qn` | Enables silent mode (no user interaction) | | `/i` | Specifies the path to the MSI installer | | `TOKEN=` | Claim token from your Netdata Cloud Space | -| `ROOMS=` | Comma-separated Room IDs for your node | +| `ROOMS=` | (Optional) Comma-separated Room IDs for your node | | `PROXY=` | (Optional) Proxy address if required | | `INSECURE=1` | (Optional) Allow insecure connections (hostname verification disabled) | | `REINSTALL=ALL` | (Optional) It forces a complete reinstallation of all Netdata components. | +`TOKEN=` is the only option required to connect the Agent to your Space. When you omit `ROOMS=`, the +node is added to your Space and appears under **All nodes**; you can move it into Rooms later from the +Netdata Cloud UI. + ### Example Command Install Netdata and connect to your Cloud Space: @@ -78,6 +82,12 @@ Replace: - `` with your claim token - `` with your Room ID(s) +To connect the node without assigning it to specific Rooms, pass the token alone: + +```bash +msiexec /qn /i netdata-x64.msi TOKEN="" +``` + ### Download & Install in One Command (PowerShell) ```powershell @@ -97,8 +107,8 @@ During the wizard you'll see a **Connect to the Cloud** dialog. These fields reg | Field | What it's for | |-------------|---------------------------------------------------------------------------------------------------| -| Claim Token | The claim token from your Netdata Cloud Space. | -| Rooms ID(s) | The Room(s) you want to add this Agent to. | +| Claim Token | The claim token from your Netdata Cloud Space. This is the only required field. | +| Rooms ID(s) | (Optional) The Room(s) you want to add this Agent to. Leave empty to use **All nodes**. | | Proxy URL | (Optional) A proxy address, if your network requires one to reach Netdata Cloud. | | Cloud URL | The Netdata Cloud endpoint. Defaults to `https://app.netdata.cloud`. | | Insecure | (Optional) Disables TLS hostname verification when the Agent contacts the Netdata Cloud endpoint. | @@ -121,6 +131,52 @@ See the [Parent-Child Configuration Reference](/docs/netdata-parents/parent-chil ::: +### Where the claim settings are stored + +The values you enter in the claim dialog (or pass to `msiexec`) are written to: + +```text +C:\Program Files\Netdata\etc\netdata\claim.conf +``` + +The Agent reads this file on startup and connects to your Space. After a successful connection it also +records the resulting identity in `C:\Program Files\Netdata\var\lib\netdata\cloud.d\cloud.conf`. + +### Connect a node that was installed without a token + +If the Agent is installed but not connected — no `claim.conf` exists, or it was installed without a +token — you don't need to uninstall or reboot. Create the file yourself and restart the service. + +1. Open Notepad **as Administrator**. +2. Create `C:\Program Files\Netdata\etc\netdata\claim.conf` with this content, replacing + `` with your claim token: + + ```text + [global] + url = https://app.netdata.cloud + token = + # rooms = + # proxy = + insecure = no + ``` + + Set `rooms` to a comma-separated list of Room IDs if you want the node placed in specific Rooms, and + set `proxy` if your network requires one to reach Netdata Cloud. Both lines are optional — leave them + commented out to connect with defaults. + +3. Restart the Agent from an Administrator PowerShell prompt: + + ```powershell + Restart-Service Netdata + ``` + +The node should appear in your Space within a few seconds. If it does not, the Agent reports the +claiming result to the Windows Event Log — a rejected or expired token is reported there: + +```powershell +Get-WinEvent -LogName 'Netdata/Daemon' -MaxEvents 50 | Where-Object { $_.Message -match 'CLAIM' } +``` + ## Offline (Air-gapped) Installation Use this method to install Netdata on a Windows system with no internet access. diff --git a/docs/Netdata Agent/Versions & Platforms.mdx b/docs/Netdata Agent/Versions & Platforms.mdx index 7b132ad49a..92aa6cc127 100644 --- a/docs/Netdata Agent/Versions & Platforms.mdx +++ b/docs/Netdata Agent/Versions & Platforms.mdx @@ -80,8 +80,6 @@ Our [static builds](#static-builds) are expected to work on these platforms if a | Alma Linux | 9.x | x86\_64, AArch64 | Also includes support for Rocky Linux and other ABI compatible RHEL derivatives | | Alma Linux | 8.x | x86\_64, AArch64 | Also includes support for Rocky Linux and other ABI compatible RHEL derivatives | | Amazon Linux | 2023 | x86\_64, AArch64 | | -| Amazon Linux | 2 | x86\_64, AArch64 | | -| CentOS | 7.x | x86\_64 | | | 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 | | @@ -93,14 +91,13 @@ Our [static builds](#static-builds) are expected to work on these platforms if a | Oracle Linux | 10.x | x86\_64, AArch64 | | | Oracle Linux | 9.x | x86\_64, AArch64 | | | Oracle Linux | 8.x | x86\_64, AArch64 | | +| Red Hat Enterprise Linux | 10.x | x86\_64, AArch64 | | | Red Hat Enterprise Linux | 9.x | x86\_64, AArch64 | | | Red Hat Enterprise Linux | 8.x | x86\_64, AArch64 | | -| Red Hat Enterprise Linux | 7.x | x86\_64 | | | 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.04 | x86\_64, AArch64, ARMv7 | | -| Ubuntu | 25.10 | x86\_64, AArch64, ARMv7 | | | Ubuntu | 24.04 | x86\_64, AArch64, ARMv7 | | | Ubuntu | 22.04 | x86\_64, ARMv7, AArch64 | | @@ -184,15 +181,19 @@ Platforms that meet these criteria will be immediately transitioned to the **Pre This is a list of platforms that we have supported in the recent past but no longer officially support: -| Platform | Version | Notes | -|----------|-----------|----------------------| -| Debian | 10.x | EOL as of 2024-07-01 | -| Fedora | 42 | EOL as of 2026-05-13 | -| Fedora | 41 | EOL as of 2025-12-15 | -| openSUSE | Leap 15.6 | EOL as of 2026-04-30 | -| Ubuntu | 25.04 | EOL as of 2026-01-17 | -| Ubuntu | 20.04 | EOL as of 2025-05-31 | -| Ubuntu | 18.04 | EOL as of 2023-04-02 | +| Platform | Version | Notes | +|--------------------------|-----------|----------------------| +| Amazon Linux | 2 | EOL as of 2026-06-30 | +| CentOS | 7.x | EOL as of 2026-06-30 | +| Debian | 10.x | EOL as of 2024-07-01 | +| Fedora | 42 | EOL as of 2026-05-13 | +| Fedora | 41 | EOL as of 2025-12-15 | +| openSUSE | Leap 15.5 | EOL as of 2024-12-31 | +| Red Hat Enterprise Linux | 7.x | EOL as of 2026-06-30 | +| Ubuntu | 18.04 | EOL as of 2023-04-02 | +| Ubuntu | 25.04 | EOL as of 2026-01-17 | +| Ubuntu | 20.04 | EOL as of 2025-05-31 | +| Ubuntu | 18.04 | EOL as of 2023-04-02 | ## Static builds diff --git a/docs/Netdata Cloud On-Prem/Release Notes.mdx b/docs/Netdata Cloud On-Prem/Release Notes.mdx index 9f09964e93..ec0c6de1ee 100644 --- a/docs/Netdata Cloud On-Prem/Release Notes.mdx +++ b/docs/Netdata Cloud On-Prem/Release Notes.mdx @@ -10,6 +10,34 @@ slug: "/netdata-cloud-on-prem/release-notes" # Release notes +## 2.6.0 (2026-08-20) + +### Features + +- Introduced AI features on on-prem, powered by the new `cloud-insights-service`: conversations grounded in your charts and alerts, generated investigation reports, and MCP client support +- Home page revamp with nodes grouped into hexagons, selectable grouping and sorting, and significantly faster loading +- Introduced Nodes fleet operations views for inspecting and acting on the fleet at scale +- Introduced alerts history and detection of misconfigured alerts +- Silencing rules improvements: timezone selector, active/inactive distinction, automatic deletion on expiration, and correct handling of multi-day recurring windows +- Custom dashboards: import/export, playlist mode, and new cards including state timeline and alert count +- New visualizations: heatmap charts, a geomap of node locations, topology maps with network flows, and an SNMP overview tab +- Added Group Email notification integration, a space-wide channel delivering alert notifications to a single mailing-list address +- Alert and reachability notifications now include host labels, and Slack/Mattermost notifications show message previews +- Scaling and performance: Nodes and Alerts now handle rooms of up to 50,000 nodes, and data queries use less memory and return faster +- New cronjobs notify about misconfigured alerts and clean up expired silencing rules +- Replaced the Help & Resources panel with the Nedi AI assistant +- Improved the global date picker +- SCIM filter matching and sorting are now case-insensitive, per RFC +- Hardened rate limiting for Agent authentication + +### Bug fixes + +- Dyncfg: fixed job list corruption with slashes in names, invalid request timeouts, and checkbox rendering +- Fixed percentage aggregation returning incorrect values on empty points and on multi-agent queries +- Fixed joining a space from an invitation link +- SCIM: SSO-to-SCIM mapping now compares emails case-insensitively, and `idp-default` attributes are accepted +- Node recreation flow stability improvements + ## 2.5.0 (2026-03-13) ### Features diff --git a/docs/Network Performance Monitoring/Device Metrics/Configuration/SNMP Profile Format.mdx b/docs/Network Performance Monitoring/Device Metrics/Configuration/SNMP Profile Format.mdx index 0f1f66c285..45a849acf3 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Configuration/SNMP Profile Format.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Configuration/SNMP Profile Format.mdx @@ -429,9 +429,19 @@ topology: - `kind` is required and must be one of the closed topology kinds below. - Topology row symbol names must not start with `_`. +- For table rows, each configured row symbol is a structural presence anchor. + When its PDU exists, the collector emits the tagged topology observation with + an internal neutral value of `0`; it does not convert the PDU value to a + number. Choose a readable column that is present for every usable row. This + allows OctetString columns such as an ARP physical address to anchor a row. + Scalar topology symbols retain their ordinary value semantics. - Topology rows do not use chart/export-only fields such as `chart_meta`, `metric_type`, `mapping`, `transform`, `scale_factor`, `format`, or `constant_value_one` on the row value symbol. +- Table topology row symbols also reject `extract_value`, `match_pattern`, and + `match_value` because structural presence mode intentionally ignores the + anchor PDU value. These transformations remain valid for scalar topology + symbols and for `metric_tags`. - `metric_tags` inside a topology row work like table metric tags and identify or enrich the topology row. - `systemUptime` stays under `metrics:` for regular SNMP collection. It is not a @@ -458,12 +468,39 @@ stp_port vtp_vlan arp_entry arp_legacy_entry +ospf_neighbor ``` Topology mixins can be inherited through `extends` just like metric mixins. When two inherited topology rows collide, the identity is `kind + table identity + symbol name`, matching regular table metric merge behavior. +#### Stock topology composition + +Stock profiles compose topology capabilities independently: + +- `_std-topology-ip-mib.yaml` provides IPv4 address, interface-index, and + netmask facts used for L3 subnet topology. `generic-device.yaml` and + `generic-ups.yaml` extend it as their baseline. The legacy `ipAddrTable` + address is derived from the row index, so the readable ifIndex and netmask + columns are sufficient. +- `_std-topology-interface-mib.yaml` provides interface identity and status. +- `_std-topology-bridge-base-mib.yaml`, `_std-topology-fdb-mib.yaml`, + `_std-topology-q-bridge-mib.yaml`, `_std-topology-stp-mib.yaml`, and + `_std-topology-arp-mib.yaml` are attached only to profiles or topology role + selectors whose device role and available MIB rows justify those walks. + +Profile matching is additive: every matching selector contributes its inherited +capabilities. A job with no usable `sysObjectID` resolves only the profiles +listed in `manual_profiles`. To retain the standard IPv4 topology baseline in +that case, include `generic-device` explicitly alongside the device profile: + +```yaml +manual_profiles: + - vendor-profile + - generic-device +``` + #### Scalar symbol fallbacks You can express “try this OID, otherwise try that OID” by declaring **multiple scalar metrics with the same** `symbol.name`, each pointing to a different OID. At runtime the collector **GETs** all declared scalar OIDs, marks missing ones, and **emits** the metric from whichever OID returns data. Missing OIDs are skipped cleanly. @@ -1463,7 +1500,7 @@ They work the same in **both** places: - `format` ```yaml symbol: - OID: 1.3.6.1.2.1.17.1.1 + OID: 1.3.6.1.2.1.17.1.1.0 name: dot1dBaseBridgeAddress format: hex ``` @@ -1499,7 +1536,7 @@ metadata: fields: bridge_base_address: symbol: - OID: 1.3.6.1.2.1.17.1.1 + OID: 1.3.6.1.2.1.17.1.1.0 name: dot1dBaseBridgeAddress format: hex ``` diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco 3850.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco 3850.mdx index 4a48d09cc9..cc3e1abde1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco 3850.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco 3850.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco 3850 profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**159 metrics** in 21 groups; each row is a chart context usable in alerts. +**150 metrics** in 21 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -155,7 +155,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -399,15 +399,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASA.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASA.mdx index f537f4f66a..04f4c0b1a2 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASA.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASA.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco ASA profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**156 metrics** in 21 groups; each row is a chart context usable in alerts. +**147 metrics** in 21 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -155,7 +155,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -396,15 +396,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASR.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASR.mdx index 6114a600c8..2c1edc0c9e 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASR.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ASR.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco ASR profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**146 metrics** in 20 groups; each row is a chart context usable in alerts. +**137 metrics** in 20 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -154,7 +154,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -380,15 +380,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Access Point.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Access Point.mdx index 19e78024ed..a997d91525 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Access Point.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Access Point.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Access Point profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**155 metrics** in 20 groups; each row is a chart context usable in alerts. +**146 metrics** in 20 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -154,7 +154,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -389,15 +389,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst WLC.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst WLC.mdx index 02c448aeb7..b20a68ffeb 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst WLC.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst WLC.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Catalyst WLC profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**171 metrics** in 22 groups; each row is a chart context usable in alerts. +**162 metrics** in 22 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -156,7 +156,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -417,15 +417,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst.mdx index 9d4623c6d7..eb6b95fe29 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Catalyst.mdx @@ -27,7 +27,7 @@ Module: snmp ## Overview -Monitor Cisco Catalyst (switch) with Netdata over SNMP. Netdata recognizes the device automatically by its `sysObjectID` (recognized across 446 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration. +Monitor Cisco Catalyst (switch) with Netdata over SNMP. Netdata recognizes the device automatically by its `sysObjectID` (recognized across 448 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration. Netdata's SNMP collector matches the device to the **cisco-catalyst.yaml** profile via `sysObjectID`/`sysDescr`, then polls the OIDs it declares. @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Catalyst profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**165 metrics** in 22 groups; each row is a chart context usable in alerts. +**156 metrics** in 22 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -156,7 +156,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -411,15 +411,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Csr1000V.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Csr1000V.mdx index cbcab190aa..1f68136545 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Csr1000V.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Csr1000V.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Csr1000V profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**146 metrics** in 20 groups; each row is a chart context usable in alerts. +**137 metrics** in 20 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -154,7 +154,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -380,15 +380,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ICM.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ICM.mdx index f320c61273..595dedb44b 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ICM.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ICM.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco ICM profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**173 metrics** in 26 groups; each row is a chart context usable in alerts. +**164 metrics** in 26 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -155,7 +155,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Process | 3 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | | Voice / CCA | 4 | | Voice / CVP | 8 | | Voice / DialPeer | 6 | @@ -394,15 +394,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR 4431.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR 4431.mdx index db0fb63744..fe991e85f2 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR 4431.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR 4431.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco ISR 4431 profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**173 metrics** in 26 groups; each row is a chart context usable in alerts. +**164 metrics** in 26 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -155,7 +155,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Process | 3 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | | Voice / CCA | 4 | | Voice / CVP | 8 | | Voice / DialPeer | 6 | @@ -394,15 +394,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR.mdx index beb13c08bc..79e4011658 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco ISR.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco ISR profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**146 metrics** in 20 groups; each row is a chart context usable in alerts. +**137 metrics** in 20 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -154,7 +154,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -380,15 +380,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Load Balancer.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Load Balancer.mdx index 947e4ccc1c..42382f4a08 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Load Balancer.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Load Balancer.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Load Balancer profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**183 metrics** in 21 groups; each row is a chart context usable in alerts. +**174 metrics** in 21 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -155,7 +155,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -423,15 +423,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | 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 3f62f0fa44..06b283f50f 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco NCS.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco NCS.mdx @@ -27,7 +27,7 @@ Module: snmp ## Overview -Monitor Cisco NCS (router) with Netdata over SNMP. Netdata recognizes the device automatically by its `sysObjectID` (recognized across 1 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration. +Monitor Cisco NCS (router) with Netdata over SNMP. Netdata recognizes the device automatically by its `sysObjectID` (recognized across 2 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration. Netdata's SNMP collector matches the device to the **cisco-ncs.yaml** profile via `sysObjectID`/`sysDescr`, then polls the OIDs it declares. @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco NCS profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**146 metrics** in 20 groups; each row is a chart context usable in alerts. +**137 metrics** in 20 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -154,7 +154,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -380,15 +380,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | 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 be659955ad..584f3f7032 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Nexus.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco Nexus.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco Nexus profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**184 metrics** in 27 groups; each row is a chart context usable in alerts. +**175 metrics** in 27 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -161,7 +161,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / NX-OS | 6 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -460,15 +460,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | 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 5067cdb633..de2e185339 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco SB.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco SB.mdx @@ -131,14 +131,14 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco SB profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**27 metrics** in 4 groups; each row is a chart context usable in alerts. +**18 metrics** in 4 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| | Network / Interface | 4 | | System / CPU | 1 | | System / Uptime | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Network / Interface @@ -165,15 +165,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | 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 1b55e5b61a..9936c7603b 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 @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco UC Virtual Machine profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**173 metrics** in 26 groups; each row is a chart context usable in alerts. +**164 metrics** in 26 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -155,7 +155,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Process | 3 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | | Voice / CCA | 4 | | Voice / CVP | 8 | | Voice / DialPeer | 6 | @@ -394,15 +394,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | 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 7d53ff898d..d7a3b7ba69 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 @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco WAN Optimizer profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**164 metrics** in 23 groups; each row is a chart context usable in alerts. +**155 metrics** in 23 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -157,7 +157,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 23 | +| Uncategorized | 14 | ### Hardware / FRU @@ -414,15 +414,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_hrStorageSize` | `By` | per storage_index, rm:storage_type, rm:storage_alloc_unit | | | `snmp.device_prof_hrStorageUsed` | `By` | per storage_index, rm:storage_type, rm:storage_alloc_unit | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | diff --git a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco.mdx b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco.mdx index 6bd5a6f15d..115a43efce 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/Cisco.mdx @@ -131,7 +131,7 @@ There are no alerts configured by default for this integration. On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration — interfaces, system, IP/TCP/UDP, host resources), this Cisco profile adds the metrics below. Each is collected **only where the device exposes the matching OID** — inclusion means the profile requests it; availability depends on the device model and software. -**146 metrics** in 20 groups; each row is a chart context usable in alerts. +**137 metrics** in 20 groups; each row is a chart context usable in alerts. | Group | Metrics | |---|---| @@ -154,7 +154,7 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | System / Memory | 4 | | System / Uptime | 1 | | System / VirtualSwitch | 1 | -| Uncategorized | 21 | +| Uncategorized | 12 | ### Hardware / FRU @@ -380,15 +380,6 @@ On top of the **generic SNMP baseline** (the *Generic SNMP Device* integration | Metric (chart context) | Unit | Scope | Description | |---|---|---|---| -| `snmp.device_prof_cdpGlobalDeviceId` | — | device | | -| `snmp.device_prof_cdpGlobalDeviceIdFormat` | — | device | | -| `snmp.device_prof_cdpGlobalHoldTime` | — | device | | -| `snmp.device_prof_cdpGlobalLastChange` | — | device | | -| `snmp.device_prof_cdpGlobalMessageInterval` | — | device | | -| `snmp.device_prof_cdpGlobalRun` | — | device | | -| `snmp.device_prof_cdpInterfaceEnable` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceMessageInterval` | — | per cdp_if_index | | -| `snmp.device_prof_cdpInterfaceName` | — | per cdp_if_index | | | `snmp.device_prof_lldpStatsRemTablesAgeouts` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDeletes` | — | device | | | `snmp.device_prof_lldpStatsRemTablesDrops` | — | device | | 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 c625335c2b..5c7e5dc5e1 100644 --- a/docs/Network Performance Monitoring/Device Metrics/Integrations/SNMP devices.mdx +++ b/docs/Network Performance Monitoring/Device Metrics/Integrations/SNMP devices.mdx @@ -208,7 +208,7 @@ The following options can be defined globally: update_every, autodetection_retry | | ping.privileged | Use raw ICMP (privileged). If false, unprivileged mode is used. | yes | no | | | ping.packets | Number of ping packets to send per iteration. | 3 | no | | | ping.interval | Interval between sending ping packets. | 100ms | no | -| **Profiles** | manual_profiles | A list of profiles to force-apply when auto-detection cannot be used. | [] | no | +| **Profiles** | manual_profiles | A list of profiles to use when `sysObjectID`-based auto-detection cannot be used. To retain baseline IPv4 topology for a device without a usable `sysObjectID`, include `generic-device` alongside its vendor profile. | [] | no | | **Virtual node** | create_vnode | If set, the collector will create a Netdata Virtual Node for this SNMP device, which will appear as a separate Node in Netdata. | true | no | | | vnode_device_down_threshold | Number of consecutive failed data collections before marking the device as down. | 3 | no | | | vnode.guid | A unique identifier for the Virtual Node. If not set, a GUID will be automatically generated from the device's IP address. | | no | @@ -395,9 +395,9 @@ jobs: ```
-###### BGP router with forced profile +###### BGP router without sysObjectID detection -Use `manual_profiles` when auto-detection cannot safely distinguish the device, or when you want to force a specific vendor BGP profile during testing. +Use `manual_profiles` when the device does not expose a usable `sysObjectID`. List the vendor profile for its BGP data and `generic-device` for baseline IPv4 interface facts used by topology. This example targets a Cisco ASR router and keeps the optional ICMP latency charts enabled. @@ -413,6 +413,7 @@ jobs: community: public manual_profiles: - cisco-asr + - generic-device options: version: 2 @@ -688,10 +689,11 @@ Current BGP peer and peer-family details from cached normalized SNMP data. Each Provides the agent-wide SNMP topology view built from all currently running topology-enabled SNMP jobs. -This function reads cached LLDP/CDP, bridge, FDB, ARP, and STP data collected by the independent topology refresh loop and returns a netdata.topology.v1 payload with compact actor, link, evidence, and detail tables. No additional SNMP requests are triggered when calling this function. +This function reads cached interface/IP, LLDP/CDP, bridge, FDB, ARP, STP, OSPF, and BGP data collected by the independent topology refresh loop and returns a netdata.topology.v1 payload with compact actor, link, evidence, and detail tables. Ordinary automatically detected SNMP devices contribute IPv4 interface and netmask facts for logical subnet membership; bridge and neighbor tables remain device-role scoped. No additional SNMP requests are triggered when calling this function. Use cases: - Discover Layer 2 neighbors and link mapping +- See managed devices that share an IPv4 subnet - Validate cabling and port connections - Identify adjacent devices that are discovered but not monitored @@ -700,9 +702,9 @@ Use cases: |:-------|:------------| | Name | `Snmp:topology` | | Require Cloud | no | -| Performance | Uses cached SNMP data only, no additional SNMP requests are triggered:
• Responses are instantaneous from memory cache
• Large devices with many discovered neighbors may return many rows | +| Performance | Uses cached SNMP data only; calling the function triggers no additional SNMP requests.
• Each request builds and renders a topology snapshot from the current cache
• CPU time, allocations, and payload size scale with cached devices, interfaces, FDB entries, neighbors, segments, and links
• Large or concurrent requests can require materially more processing even though no device walk occurs | | Security | Exposes discovered device identifiers, interface/port identifiers, and management addresses only:
• No packet payloads or authentication credentials are exposed
• No device configuration details are exposed | -| Availability | Available when:
• The collector has completed at least one successful topology refresh cycle
• LLDP/CDP topology data is present in cache from the last successful topology refresh
• Returns HTTP 503 if topology cache is not ready yet | +| Availability | Available when:
• At least one topology-enabled SNMP job has a fresh successful snapshot
• That snapshot contains enough device identity to render a managed actor; LLDP/CDP rows are not required
• Returns HTTP 503 if no current renderable topology snapshot is available | #### Prerequisites @@ -713,7 +715,7 @@ No additional configuration is required. | Parameter | Type | Description | Required | Default | Options | |:---------|:-----|:------------|:--------:|:--------|:--------| | Nodes Identity | select | Choose actor identity strategy. `ip` collapses nodes by management IP and removes non-IP inferred actors. `mac` keeps MAC-oriented identities. | yes | ip | IP (default), MAC | -| Map | select | Select the topology map mode. Defaults to the managed-device LLDP/CDP view. Other modes progressively include inferred devices and lower-confidence links. | yes | lldp_cdp_managed | LLDP/CDP/Managed Devices Map (default), High Confidence Inferred Map, All Devices (Low Confidence) | +| Map | select | Select the topology map mode. The default Managed Fabric Map keeps monitored devices, direct LLDP/CDP and managed STP links, and qualified FDB broadcast-domain paths. Logical L3 subnet, OSPF, and BGP relationships remain visible with distinct presentation. Legacy and broader inferred views remain selectable. | yes | managed_fabric | Managed Fabric Map (default), LLDP/CDP/Managed Devices Map, High Confidence Inferred Map, All Devices (Low Confidence) | | Infer Strategy | select | Select the inference algorithm used for FDB/STP/CDP correlation. | yes | fdb_minimum_knowledge | FDB Minimum-Knowledge (Baseline) (default), STP Parent Tree, FDB Pairwise Minimum-Knowledge, STP + FDB Correlated, CDP + FDB Hybrid | | Focus On | multiselect | Limit depth filtering to selected managed SNMP roots. The static default is `all_devices`; additional `ip:
` options are supplied dynamically from the current managed SNMP jobs. | yes | all_devices | All Devices (default) | | Focus Depth | select | Limit topology expansion hops from the focus roots. `all` disables depth filtering. | yes | all | All (default), 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 | diff --git a/docs/Network Performance Monitoring/Topologies/Discovery Methods.mdx b/docs/Network Performance Monitoring/Topologies/Discovery Methods.mdx index b20e041041..ca1fcc9757 100644 --- a/docs/Network Performance Monitoring/Topologies/Discovery Methods.mdx +++ b/docs/Network Performance Monitoring/Topologies/Discovery Methods.mdx @@ -28,7 +28,7 @@ Netdata builds your topology by reading, over SNMP, what your devices already kn - **BGP** — the BGP peering relationships between your routers (neighbor and remote AS), drawn as router-to-router links. - **OSPF** — the OSPF adjacencies between your routers. -- **Connected subnets** — point-to-point router links inferred from interface IP addresses that share a `/30` or `/31` subnet, catching the router-to-router links that aren't carried by BGP or OSPF (directly-connected or statically-routed links). +- **Connected subnets** — direct router links inferred from two interfaces sharing a `/30` or `/31`, plus logical subnet segments for managed devices sharing a `/24` through `/29`. These are rendered as logical Layer 3 relationships rather than physical links. ## How they come together @@ -39,7 +39,7 @@ Netdata fuses these per device into one live graph: LLDP and CDP give the links, The device topology is served by the **`topology:snmp`** function — open it from the topology view to see the fabric. A few controls shape what you see, so you can move between a high-trust overview and the complete picture: - **Nodes identity** — show actors by **IP** (the default, which collapses duplicates and drops non-IP inferred nodes) or by **MAC**. -- **Map** — choose **LLDP/CDP/Managed Devices Map** (the default — the links your monitored devices advertise directly over LLDP and CDP; "managed" devices are the ones Netdata polls over SNMP), **High Confidence Inferred Map** (adds links Netdata infers with strong evidence), or **All Devices (Low Confidence)** (everything seen, including weakly-inferred links). +- **Map** — choose **Managed Fabric Map** (the default — all monitored SNMP devices, direct LLDP/CDP and managed STP links, and FDB paths through qualified broadcast-domain segments), the legacy **LLDP/CDP/Managed Devices Map**, **High Confidence Inferred Map**, or **All Devices (Low Confidence)**. Logical Layer 3 subnet, OSPF, and BGP relationships remain visible in every mode with their distinct dashed presentation. - **Infer strategy** — how Netdata reconstructs links the devices don't advertise directly, from **FDB Minimum-Knowledge (Baseline)** (the default) through **STP Parent Tree**, **FDB Pairwise Minimum-Knowledge**, **STP + FDB Correlated**, and **CDP + FDB Hybrid**. Different strategies suit different fabrics. - **Focus on** and **Focus depth** — pick one or more devices as roots and limit the map to a number of hops out from them, to zoom into one part of a large network. diff --git a/ingest/generated_sidebar_order.json b/ingest/generated_sidebar_order.json index 13fdd1c4d5..a7b5f50797 100644 --- a/ingest/generated_sidebar_order.json +++ b/ingest/generated_sidebar_order.json @@ -2,7 +2,7 @@ "schema_version": 1, "source": "netdata/docs/.map/map.yaml", "source_sha256": "169ec6b8d7adc04fa72c3d8e22708e629fa0e03e30e80fbc9ca6eb09b6231d39", - "source_corpus_sha256": "68b00a86c9df68db962cb0bdaa0b6b129df75168a610c5959ac343a8519dc656", + "source_corpus_sha256": "d70b95867fb3d419a8afa60a571f326339881e5eb4887a64e999384d4b3b5ce6", "order": [ { "parent_path": "Alerts & Notifications", @@ -1715,5 +1715,5 @@ "position": 170 } ], - "full_ingest_identity_sha256": "a5ab614084c59c8f0002221db8f64223b48086ebfb7c97b814ab1b4dd80ab997" + "full_ingest_identity_sha256": "727b4b007e752663d5d6e5838c3196719e4b113c90368fd52c8719f060436d25" } diff --git a/ingest/generated_sidebar_order.json.sha256 b/ingest/generated_sidebar_order.json.sha256 index ff359490fc..d658d40787 100644 --- a/ingest/generated_sidebar_order.json.sha256 +++ b/ingest/generated_sidebar_order.json.sha256 @@ -1 +1 @@ -711c2a948c0b91545857fc1d8566a407fd14b363dc7dfc076c249d9d796acb1d generated_sidebar_order.json +8b04645e325683377b36f6f5e9b167bd2d240492a39368c2d1d74f0cd042faac generated_sidebar_order.json