The lookback window for this insight is 1 year (the date range for the data included).
INCIDENT_ID: Unique ID given to the incident
PROJECT_NAME: As defined externally
DATASET_NAME: As defined externally
INCIDENT_TYPE : The type of incident such as; anomalies / custom_rule_anomalies / deleted_tables / metric_anomalies / schema_changes
INCIDENT_CREATED_DATE : The date that the incident was created.
INCIDENT_CREATED_TIMESTAMP : The timestamp of when the incident was created.
N_EVENTS: A count of unique events
N_TABLES: A count of unique tables
N_KEY_ASSETS: A count of unique ‘important’ tables
LAST_FEEDBACK: The last given status of the incident
LAST_FEEDBACK_DATE: The date of LAST_FEEDBACK
LAST_FEEDBACK_TIMESTAMP: The timestamp of LAST_FEEDBACK
FIRST_FEEDBACK: The first given status of the incident
FIRST_FEEDBACK_TIMESTAMP: The timestamp of FIRST_FEEDBACK
MAX_IMPORTANCE_SCORE: The maximum importance score in the incident
AVG_IMPORTANCE_SCORE: the average importance score for the incident
INCIDENT_APP_URL: The link the to incident in the app
KEY_ASSETS_WITH_IMPORTANCE_SCORE: A list of important tables and their corresponding importance scores
NON_KEY_ASSETS_WITH_IMPORTANCE_SCORE: A list of non-important tables and their corresponding importance scores
OWNER : As defined in the UI
SEVERITY: As defined in the UI
SENT_VIA: A list of notification source e.g. Slack / teams
SENT_VIA_CHANNEL: A list of notification recipients
DOMAINS: As created by the user in the UI.
Updated 7 months ago