...
Expand | ||
---|---|---|
| ||
2. If your rule doesn’t show up, check for errors in /usr/share/indeni/logs/rules/general.log 3. If your custom rule shows up, but the alert is not triggering, change the monitoring_interval to 1 minute and reboot the Indeni service 4. If still no luck, check for errors in /usr/share/indeni-collector/logs/collector.log and /usr/share/indeni-collector/logs/devices/device_ip.log 5. Contact Indeni Support. We are more than happy to help you get your custom rules working! Please feel free to reach out to us. |
Expand | ||
---|---|---|
| ||
When you would like your code to be integrated eventually, you will need to place the above files under the correct path, and with the correct name convention. Otherwise, your script might not work properly. Script files (yaml + parser), will be placed under the location: /usr/share/indeni-knowledge/stable/ind/parsers/src/<Vendor>/…/<New folder to represent the ADE, in lower case>/ Rule files, will be placed under the location: /usr/share/indeni-knowledge/stable/rules/<Rule Type>/<Vendor>/ Example based on the files above: Important notes: 1. All folder names should have lower case letters. |