mirror/librenms-librenms
1
0
Fork 0
mirror of https://github.com/librenms/librenms.git synced 2024-10-07 16:52:45 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update Health-Information.md

Browse Source 
A few details on how the entPhysicalIndex column should be currently used
This commit is contained in:
PipoCanaja
2024-03-11 20:28:48 +01:00
committed by GitHub
parent d7c31e0ae3
commit 7bf6a5aa3c
1 changed files with 5 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
doc/Developing/os/Health-Information.md
+5 -4
View File
@@ -117,10 +117,11 @@ are as follows:
over (see note below).
- `skip_value_lt` (optional): If sensor value is less than this, skip the discovery.
- `skip_value_gt` (optional): If sensor value is greater than this, skip the discovery.
- `entPhysicalIndex` (optional): If the sensor belongs to a physical
entity then you can specify the index here.
- `entPhysicalIndex_measured` (optional): If the sensor belongs to a
physical entity then you can specify the entity type here.
- `entPhysicalIndex` and `entPhysicalIndex_measured` (optional) : If the
sensor belongs to a physical entity then you can link them here. The currently
supported variants are :
- `entPhysicalIndex` contains the entPhysicalIndex from entPhysical table, and `entPhysicalIndex_measured` is NULL
- `entPhysicalIndex` contains "ifIndex" value of the linked port and `entPhysicalIndex_measured` contains "ports"
- `user_func` (optional): You can provide a function name for the
sensors value to be processed through (i.e. Convert fahrenheit to
celsius use `fahrenheit_to_celsius`)