This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| configuration:monitoring:trigger [2019/07/22 10:48] – [Odbc] acruz | configuration:monitoring:trigger [2019/07/22 10:59] – [Odbc] acruz | ||
|---|---|---|---|
| Line 188: | Line 188: | ||
| ==== Odbc ==== | ==== Odbc ==== | ||
| + | Adding a trigger rule that check status as lines in odbc query: | ||
| * Name: odbc_query | * Name: odbc_query | ||
| * Priority: First | * Priority: First | ||
| * Continue: Continue after rule | * Continue: Continue after rule | ||
| * Conditions: x - Any | * Conditions: x - Any | ||
| - | * Action: x - Custom | + | * Action: x - Custom, odbc |
| - | * Destination: 192.168.10.1 | + | * ODBC: triggers. |
| - | * Version: x - SNMP V1/SNMP V2/SNMP V3 | + | * SQL: select * from lines where status = ' |
| - | * Trap OID: <OID> | + | |
| - | * Community: public | + | Adding a trigger rule that check response of the query and send one email to responsable: |
| - | * Uptime: 60 | + | * Name: check_odbc_query |
| - | * x – OID: OID: <OID> | + | * Priority: After: odbc_query |
| + | * Continue: Continue after rule | ||
| + | * Conditions: x - custom | ||
| + | * vairables main value: | ||
| + | | ||
| + | | ||
| + | * Action: | ||
| + | * to: ${odbc_responsable}. | ||
| + | * subject: ${odbc_name} line is down | ||
| + | * body: check status of ${odbc_name} because is down | ||
| ==== Attendance ==== | ==== Attendance ==== | ||