Read a workspace setting
Tool: oppex.admin.getConfig
Reads the current value of one incident-handling setting for your connection's workspace, such as whether a root cause analysis (RCA) is required before resolving. The assistant checks the RCA setting on its own before it resolves an incident. The tool only reads settings. Change them in Oppex.
What you provide
| Input | Required | Description |
|---|---|---|
| Setting | Yes | The setting to read, from the table below. |
Settings you can read
| Setting | Type | Default | What it controls |
|---|---|---|---|
system.enable.mandatory.rca | Yes or no | No | Whether an incident needs an RCA before it can be resolved. |
workspace.incidents.maxSnoozeDurationMinutes | Minutes | 1440 | The longest an incident can be snoozed. |
workspace.incidents.ackTimeoutMinutes | Minutes | 60 | How long an acknowledged incident waits before the acknowledgement times out. |
workspace.incidents.escalateAfterAckTimeoutEnabled | Yes or no | No | Whether Oppex escalates again when the acknowledgement times out. |
workspace.incidents.slaAckBreachThresholdSecondsP50 and ...P90 | Seconds | 1800 and 3600 | The acknowledgement time targets used in reporting. |
workspace.incidents.slaResolveBreachThresholdSecondsP50 and ...P90 | Seconds | 86400 and 259200 | The resolution time targets used in reporting. |
Example prompts
- "Do we need an RCA before resolving incidents in this workspace?"
- "What's the longest I can snooze an incident here?"
- "Does an acknowledged incident escalate again if nobody resolves it?"
Who can use it
Anyone, whatever their role.
What you get back
The setting's current value and its type, the default value, and where the value comes from: your workspace, your organization, or the Oppex default.
Limits and errors
| Message | Meaning |
|---|---|
| "Unknown config key: <key>" | The setting is not one of those listed above. |