@cryptotaxi247 / netdata-1 / commits / 8115e2a1d

docs: clarify alert behavior for non-existent mount points (#22038)

* docs: clarify alert behavior for non-existent mount points Add guidance explaining that alerts based on chart labels require the underlying chart to exist. Disk space alerts won't trigger for mount points that don't exist (e.g., CIFS mount failures after reboot). Suggests alternative approaches: systemd mount unit monitoring and filecheck collector for monitoring mount failures. * docs: add Useful resources section to disk_space_usage guide Add links to relevant documentation for disk space monitoring: - Netdata disk space collector documentation - Linux disk usage commands guide - systemd mount unit troubleshooting for mount failures * docs: remove unnecessary Useful resources section from disk_space_usage guide * docs: add Useful resources section with CTA links to disk_space_usage.md * docs: replace plain bullet points with CTA links in REFERENCE.md chart labels admonition * docs: use clean CTA links in disk_space_usage Useful resources section * docs: use CTA links in REFERENCE.md chart labels admonition * docs: replace internal /src/ links with external URLs in disk space and REFERENCE guides * docs: remove external link from alert chart labels note * docs: add Collectors overview link to chart labels admonition * Remove vague external links from health guides Per reviewer feedback: - Both files are not on Learn (not in docs/.map/map.yaml) - External CTA links (Red Hat guide, freedesktop.org) are vague and not specific - Removed Useful resources sections since no useful internal link candidates exist * docs: remove link from chart labels important note Remove the Collectors overview link from the alert chart labels :::important block in REFERENCE.md. The block's content explaining that CIFS mount failures prevent disk.space chart creation already satisfies the guidance; the link violated the no-links acceptance criteria. Fixes feedback: links to non-Learn files should not be added. * Apply suggestions from code review Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> * Update REFERENCE.md * Apply suggestions from code review Co-authored-by: Fotis Voutsas <fotis@netdata.cloud> --------- Co-authored-by: nedi-app[bot] <bot@netdata.cloud> Co-authored-by: Fotis Voutsas <fotis@netdata.cloud>

nedi-app[bot] committed Apr 6, 2026 at 08:54 UTC 8115e2a1da6f9d966d19b415c9faab25a6e11ed3
3 files changed +6 -8
src/health/REFERENCE.md
+4 -1
@@ -802,11 +802,14 @@ chart labels: mount_point=/mnt/disk1 device=sda
802
803 This requires BOTH conditions to be true (AND logic).
804
805 -**Important Notes:**
805 +:::important
806
807 - Space-separated list with [simple patterns](/src/libnetdata/simple_pattern/README.md) support
808 - If a specified label doesn't exist on the chart, the chart won't match
809 - Multiple labels use AND logic
810 +- Alerts based on `chart labels` require the underlying chart to exist. For example, a `disk.space` chart is only created when a mount point is present and collected. For example, if a CIFS mount fails to mount after a system reboot, no `disk.space` chart will exist for that mount point, and the alert will not activate
811 +
812 +:::
813
814 #### Alert Line `summary`
815
src/health/guides/disks/disk_space_usage.md
+2 -1
@@ -16,4 +16,5 @@ If your storage device is full and the alert is raised, there are two paths you
16
17 - If your workflow requires all the space that is currently used, then you might want to look into upgrading the disk that raised the alarm, because its capacity is small for your demands.
18
19 -Netdata strongly suggests that you are careful when cleaning up drives, and removing files, make sure that you are certain that you delete only unnecessary files.
\ No newline at end of file
19 +Netdata strongly suggests that you are careful when cleaning up drives, and removing files, make sure that you are certain that you delete only unnecessary files.
20 +
src/health/guides/systemdunits/systemd_mount_unit_failed_state.md
-6
@@ -46,9 +46,3 @@ A `failed state` indicates that there was an issue with mounting the filesystem,
46 - Seek technical support
47
48 If the issue persists, consider reaching out to support, as there might be an underlying issue that needs to be addressed.
49 -
50 -### Useful resources
51 -
52 -1. [systemd.mount - Mount unit configuration](https://www.freedesktop.org/software/systemd/man/systemd.mount.html)
53 -2. [systemctl - Control the systemd system and service manager](https://www.freedesktop.org/software/systemd/man/systemctl.html)
54 -3. [journalctl - Query the systemd journal](https://www.freedesktop.org/software/systemd/man/journalctl.html)
\ No newline at end of file