What Oppex Nova can answer
Oppex Nova answers questions about the incident data of the workspace you are in. This page lists what it can read, how it interprets common words, and what it cannot do.
What Nova can read
| Topic | Examples of what you can ask about |
|---|---|
| Incidents | When incidents were created, acknowledged and resolved, how long that took, their severity and priority, who they are assigned to, and the counts of notes, calls, text messages and emails. |
| Root cause analysis (RCA) | Which incidents have an RCA, whether the fix was permanent, and the details recorded in it. |
| Services | Incident volume and response times for each service. |
| People | How many incidents each person was assigned at each escalation level, how many at night, and how many they acknowledged and resolved. |
| Recurring patterns | Alert patterns that repeat, with their counts over the last 1, 7, 30 and 90 days. |
| Calls and text messages | How many phone calls and text messages Oppex sent for incidents. |
| Workspace variables | Counts and groupings by a workspace variable, such as the cluster or the region. |
| Muted and snoozed incidents | Which incidents were muted or snoozed, how often, and for how long. |
Nova answers only from the current workspace. It cannot read billing data.
Questions to try
| Question | What you get |
|---|---|
| How many incidents were created last week, and how does that compare to the week before? | Two numbers and the change between them. |
| Which 5 services had the most incidents in the last 30 days? | A table with one row for each service. |
| List the 10 most recent incidents that are still open, with their service and severity. | A table of incidents. |
| How many incidents were resolved last week? | One number that opens a list of the incidents. |
| What percentage of incidents breached the acknowledgement target last month? | A percentage with the number of incidents behind it. |
| Which people were assigned the most incidents at escalation level 1 last week, and how many were at night? | A table with one row for each person. |
| How many incidents were muted or snoozed last month? | Counts of muted and snoozed incidents. |
How Nova reads your words
Dates
- "This week" and "this month" run from the start of the calendar period to today.
- "Last week" and "last month" mean the previous complete calendar period.
- Nova states the dates it used under Assumptions.
- Dates use UTC. "Night" means 22:00 to 06:00 UTC.
- If your question needs a period and you did not give one, Nova asks you to choose.
Averages and medians
Nova calculates an average time to acknowledge or resolve unless your question says median, MTTA, MTTR or P50. In that case it uses the median, and the label tells you which one it used. Nova leaves out the rare incidents whose calculated time is negative.
Response targets
Nova compares incidents with the acknowledge and resolve targets in your workspace settings. If you do not name a percentile, it uses P50 and says which target it used. See Set SLA targets for reports. An incident that was never acknowledged or resolved is not counted as a target miss.
Muted and snoozed incidents
Nova includes muted and snoozed incidents in counts and response times, and calls them out. Tables get Muted and Snoozed columns. Ask for them to be left out, for example "excluding muted incidents", and Nova leaves them out and says so. A muted incident is resolved automatically, so its resolve time does not describe a real response.
What Nova cannot do
- Show the query behind an answer.
- Change incidents, settings or users, or send an email.
- Answer about another workspace. Nova replies that it can see only your current workspace.
- Answer in a language other than English.
- Answer from a field that Oppex does not track. Nova asks which field you mean, or says which one is missing.
How current the data is
Oppex rebuilds the reporting data every night. A question about today can miss incidents that arrived since the last refresh, so Nova adds a caution and may also show yesterday.