Scheduled Incident Generation
Introduction | Property 2.1 | Generate Incidents Flag | Priority Flag
Introduction
Incident Generation can be automatically triggered after a Scheduled Troubleshooting is completed.
Every Troubleshooting that is scheduled references the Scheduled Troubleshooting Name (with the prefix: Scheduled Job) in the Initiated By Attribute on the Troubleshooting Form.
Refer to the Attribute >>> Initiated By
See the value >>> Scheduled Job: ALL US
Property 2.1: generate_incident.scheduled_troubleshooting
We can control if we want Discovery Admin to automatically trigger Incident Generation.
NOTE: This Property does not apply to any Troubleshooting that is triggered Manually (i.e. without Scheduled Troubleshooting).
All Manually initiated Troubleshooting requires the Incident Generation to also be Manually initiated via the { Generate Incident } UI Action.
Detailed instructions about this Property, along with how to configure it, (referenced in the screenshot above) can be done on the Discovery Admin Properties Page via: Discovery Admin > Properties
In summary:
true = enables auto-generation of Incidents via Scheduled Troubleshooting
false = disables auto-generation of Incidents via Scheduled Troubleshooting
Generate Incidents Flag (on Scheduled Troubleshooting Form) [v9.3]
The Scheduled Troubleshooting can be configured to automatically Generate Incident(s) after the Analysis is Executed, using the 'Generate Incidents' flag (provided Discovery Admin Property 2.1 discussed in the next section is enabled) on the Scheduled Troubleshooting Form.
This allows additional control for Incident Generation at the granularity of the Scheduled Troubleshooting enabling consistent reporting to be used for Incident Generation as well as Reporting.
Priority Flag  (on Scheduled Troubleshooting Form) [v9.3]
Incident Generation on Scheduled Troubleshooting can also be configured to use a separate prioritized background queue using the 'Priority' flag on the Scheduled Troubleshooting Form.
This enables Discovery Admin to run up to two Scheduled Troubleshootings in parallel.