Thomas Vincent
a8c677137c
* docs: clarify device templates and imports in Cacti 1.2 Signed-off-by: Thomas Vincent <thomasvincent@gmail.com> * docs: align monitoring guides with released Cacti 1.2.31 Signed-off-by: Thomas Vincent <thomasvincent@gmail.com> * docs: correct SNMP setup and scalar OID examples Signed-off-by: Thomas Vincent <thomasvincent@gmail.com> * docs: preserve history when changing collection profiles Signed-off-by: Thomas Vincent <thomasvincent@gmail.com> * docs: correct maintenance template workflows and examples Signed-off-by: Thomas Vincent <thomasvincent@gmail.com> --------- Signed-off-by: Thomas Vincent <thomasvincent@gmail.com>
2.7 KiB
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.
These rules select indexed data-query graphs. Associated non-indexed graph templates have a separate automatic creation path controlled by Enable Automatic Graph Creation; they do not require a graph rule.
Device identification and graph selection are separate steps. A vendor or device template match does not prove that the device exposes every measurement in that template. Confirm SNMP access and the returned data-query rows before enabling a rule across a fleet. For queries with optional tables or components, select only the rows and graph types supported by the target devices.
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.
Use both Show matching devices and Show matching objects to review the scope. These previews show rule matches, not proof that each selected metric will poll successfully. Check the resulting graphs on representative devices as well.
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-2026 The Cacti Group