Configuration
Choose which HTTP responses count as successful calls.
Settings → Configuration holds settings that change how KubeSense reads your data, for everyone on the installation. Each section on the page is its own permission, so a role can be given one section without the others.
Today the page has one section, Traces.
Traces: which HTTP responses count as success
An HTTP call ends with a status code, and whether a code counts as a success or an error depends on your services. A 404 from a lookup API is often a normal answer, while a 404 from a checkout page is a problem. The Traces section lets you decide this per status code range.
Each range has a Success / Error switch:
| Range | Meaning | Default |
|---|---|---|
| 2xx | Success | Success |
| 3xx | Redirection | Success |
| 4xx | Client errors | Success |
| 5xx | Server errors | Error |
Calls over other protocols, such as gRPC, database or messaging calls, are not affected. They keep their own success or error status.
Changing it
- Open Settings → Configuration.
- In Traces, set each range to Success or Error.
- Click Save.
At least one range must be Success; with none, Save stays disabled. Discard changes drops edits you have not saved, and Reset to default brings back the defaults above. You still have to click Save after a reset.
The setting applies to every user. It changes how numbers are calculated, not the data that is stored, so it applies to past time ranges as well as new ones.
What follows it
On a service's detail view, the Overview tab's Success Rate and Successful Calls charts are calculated from this setting, so the two always agree. Successful Calls is split by protocol. See Overview.
For example, with the defaults, a service that answered 900 calls with 200, 80 with 404 and 20 with 500 shows a Success Rate of 98%. Switch 4xx to Error and save, and the same service shows 90%.
Who can see and change it
The Traces section is controlled by the Trace Configuration module, in the Traces card of the role form under Trace Management. Viewer sees the section, and Editor can change it. See Role Access.
On upgrade, every role that could open Settings → General gets Trace Configuration at the same level, so whoever could change settings before can change this too.
A role without the module does not see the Configuration tab or find it in the command palette.
Availability
Configuration must be enabled for your installation. If the tab is not visible to an administrator, ask whoever runs your KubeSense installation to enable it.