No. Unfortunately, the Delphix appliance does not have a fully featured granular event distribution management workflow where all possible events can be viewed.
This stems from the fact that there is no such thing as a single monolithic event log, but four event handling mechanisms.
- actions
Things that users do or automated things a user configured the system to do. - job and job events
Things that change the state of data on the Delphix appliance like creating new VDBs, or taking manual Snapshots. All jobs are also actions. - faults
Anything that can be considered an error system-wide - alerts
Subset of all of the above and can also be configured to output to remote Syslog, SNMP, and SMTP targets.
The behavior of these can be broken down as follows...
- Every JOB starts as an ACTION. If it fails before the ACTION spawns a JOB, You may get a FAILED ACTION status with minimal (or none) details.
- Generally, an ACTION will then spawn a JOB. If a JOB fails, more details will be in the JOB events (extracted from the API or seen in the GUI). Some errors though do not result in FAILED jobs but just appear as warnings.
- Some types of failures for either ACTION or JOBs can result in FAULTs. But FAULTs can also arise at runtime outside of the context of any ACTION or JOB
- ALERTs may contain a subset of both FAULTs, ACTION, or JOB events and some events may only get triggered as ALERTs.
Generally, users will simply configure alerts to the designed severity level and act on those on a case-by-case basis. Alternatively, you can mine all events periodically from all 4 places via the CLI or API (though only the API will give Job events).