mirror of
https://github.com/Cacti/documentation.git
synced 2026-11-09 14:05:23 +09:00
Sean ManciniandTheWitness
8c4b97b8c2
* Update README.md Move spine documentation under the data collection section * Add files via upload Add Images for Automation discovered devices * Delete Discoverd devices add menu.JPG * Add files via upload * Add files via upload * Update Discovered-Devices.md Add image * Add files via upload * Update Discovered-Devices.md Update with more details * Update Discovered-Devices.md * Update README.md Fix trailing spaces * Update Discovered-Devices.md * Update Discovered-Devices.md Make travis happy * Update External-Links.md Added some wording * Device-Rules.md updated from https://stackedit.io/ * Device-Rules.md updated from https://stackedit.io/ * Device-Rules.md updated from https://stackedit.io/ * Update Device-Rules.md Fix formating * Device-Rules.md updated from https://stackedit.io/ * Update Device-Rules.md fix grammar * Device-Rules.md updated from https://stackedit.io/ * Delete Discovered devices.JPG * Delete discovered-device-add-menu.JPG * Add files via upload * Update Discovered-Devices.md update images from JPG to PNG * Delete automation-discovered-devices-dropdown.JPG * Add files via upload * Delete Discovered devices. Menu.JPG * Delete Discovered-devices-menu.png * Add files via upload * Delete discovered-devices-menu.png remove unneeded image * Update Device-Rules.md * Create Threshold-Plugin.md * Create Monitor-Plugin.md * Create Syslog-Plugin.md * Update README.md Add Cacti group created plugins * Update Graph-Rules.md * Update Graph-Rules.md * Delete Monitor-Plugin.md * Delete Threshold-Plugin.md * Delete Syslog-Plugin.md * Update README.md * Update Graph-Rules.md grammar Co-authored-by: TheWitness <thewitness@cacti.net>
40 lines
1.9 KiB
Markdown
40 lines
1.9 KiB
Markdown
# Automation Graph Rules
|
|
|
|
This section will describe **Graph Rules** in Cacti.
|
|
|
|
Graph rules are used by the Cacti automation process after a device has been identified and a template has been applied
|
|
the next step is graph creation. Graph rules are processed from top to bottom.
|
|
|
|
The graph rule matches the graph template by looking at the data fields chosen that are available in the data query
|
|
for example below we are creating graphs for interface traffic the data query has several fields available to match on.
|
|
|
|
You can see how these rules would take place by clicking the show matching objects link.
|
|
|
|
|
|
|
|
A practical example if you want to create graphs for interfaces that are in up/up status you would choose the ifOperstatus field and match
|
|
the status to UP this would tell automation to create the graph for that interface only if the data query discovers the operational status is equal
|
|
to up.
|
|
|
|
A device selection Criteria is also important Cacti needs a way to find which device it needs to match.
|
|
In the below example we are matching any device that has an interface that is up and is not a Windows server.
|
|
|
|
You can preview which devices this will apply to by clicking the Show matching devices link.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This output shows us which devices match our devices rules this can help with tweaking rules as needed.
|
|
|
|
|
|
|
|
This output shows which interfaces,drives,sensors etc will be graphed based on the graph rules.
|
|
|
|
|
|
|
|
---
|
|
Copyright (c) 2004-2021 The Cacti Group
|