How to use Incident analytics

What this section is for

Shows incident trends, open/critical/resolved counts and handling time.

Before you start

You need access to IAM.Secure, the correct tenant/workspace and permission to read this data. Prepare a non-sensitive example value such as 30d.

Buttons and forms

Control	What it does
Period	Performs the action named in the interface. Review the resulting state or message before continuing.
Filters	Narrows the visible list without changing server-side objects.
Refresh analytics	Reloads data from the server and keeps the current page context.

Primary path in the interface

Open the application link above and sign in with the least-privileged role required for this section.
Select the intended tenant or workspace. Do not continue while the header shows a different tenant.
In the navigation, click Incident analytics. The expected address is https://app.iamsecure.ru/incident-analytics.
Click Filters. Enter the documented safe values: 30d. Do not paste a production secret into a free-text field.
Review every field before the final Save, Run, Publish or Confirm action. If a preview or validation control exists, run it first.
Review the validation message or changed row. The result must match this purpose: Shows incident trends, open/critical/resolved counts and handling time.
Only then continue to the next dependent section. Copy the request/correlation ID when the interface shows one.

Second path: direct link and CLI/API

Open the deep link https://app.iamsecure.ru/incident-analytics instead of navigating through the sidebar.
Confirm the tenant/workspace after the page loads; a deep link must not silently switch scope.
Before automating the API path, run this product-specific read-only or validation command. It proves reachability but does not bypass application permissions:

export IAM_SECURE_URL=https://api.iamsecure.ru
curl --fail --silent --show-error "$IAM_SECURE_URL/healthz"

How to verify the result

Period and filters agree with KPI cards and detail rows.

If it did not work

Symptom	What to do
401 / sign-in screen	Sign in again, then return to this page. Do not put a session token in a URL.
403	Check the selected tenant and request the documented role; retrying with the same role will not help.
404	Verify the exact path and whether the feature is enabled in this environment.
409	Search for an object named `30d`; continue with it or choose a unique name.
422 / validation error	Correct only the highlighted fields. Keep identifiers lowercase unless the form explicitly allows otherwise.
429	Wait for the displayed retry interval or reduce the request scope; do not start parallel retries.
5xx / timeout	Refresh once after the server has recovered; do not repeat a destructive action while its result is unknown. Save the correlation ID and timestamp for support.