Skip to content

Dashboard

The dashboard is the first page of a workspace. It answers “is anything wrong right now?” from top to bottom.

Every role can open the dashboard: admin, member and viewer. The sections appear in this order:

  1. Needs attention (only when automatic incidents are on)
  2. Workspace statistics
  3. Tenant status
  4. Tenant activity timeline
  5. Auth0 API metrics (only when the workspace has an Auth0 tenant)
  6. Event feed

A strip at the top of the page that summarises incidents. It appears only when automatic incidents are on for the workspace. It updates live.

On the left:

Item Meaning
Needs attention The heading of the strip
No open incidents. Shown when no incident is open or escalated
{x} escalated · {y} open · {z} closed this week The summary line
, {n} silenced A link after the summary line, shown only when incidents are silenced. It opens Incidents filtered to silenced incidents.
View all incidents Opens Incidents

When nothing needs attention, the strip also shows a coverage sentence, for example {a} of {b} detectors are evaluating across {n} tenants. The sentence can add that some detectors are blocked by missing telemetry, blocked by masked identities, or switched off for this workspace. With no tenants it reads No tenants are connected yet, so no detectors are evaluating.

On the right:

Item Meaning
{n} detectors armed How many detectors are working
, {n} blocked A link, shown only when a detector is blocked. It opens Incident settings.
The detector graphic Pulses when incident activity arrives
Up to three incident rows The most serious escalated incidents. Select one to open it.
Showing the top 3 of {n} escalated and View all escalated Shown only when more than three incidents are escalated

See Detectors for what each detector does, and Manage incidents for the tasks.

Four cards. They refresh by themselves when events arrive or are dismissed.

Card What it shows
Active events The large number is every event that is not yet dismissed, within the retention period. The status is All clear with No events requiring attention when the number is 0, or Needs Attention with Events requiring review across all tenants. A second line reads {n} events in last 24 hours.
Source distribution Total Tracked Events, then a bar with the count and percentage for Okta, Entra ID and Auth0. This total includes dismissed events.
Avg dismissal time Two figures: Last 24h and Last 7d. Each is the average time from when an event was received to when it was dismissed, for example 2h 5m. It reads N/A or No data available when nothing was dismissed in the period. This card appears only when a platform operator switches it on for the workspace.
Ingestion velocity 24-hour average rate in events/hr, then {n} total events ingested in the last 24 hours., 7d avg:, 30d avg: and Trend:.

The Trend: line compares the last 24 hours with the 7-day average:

Trend Meaning
▲ {x}% increase The 24-hour rate is more than 20% above the 7-day average
▼ {x}% decrease The 24-hour rate is more than 20% below the 7-day average
► Stable The rate is within 20% of the 7-day average

One card for each tenant, in groups headed Okta tenants, Auth0 tenants and Microsoft tenants.

Each card shows:

  • The tenant name and a customer badge.
  • All clear with No events requiring attention, or a badge {n} Events with the highest active severity (Critical, Error, Warning or Info) and Events requiring review in this tenant.
  • A card with active events pulses in the colour of its highest severity. It stops when the last active event is dismissed.

The cards themselves are not clickable.

If the workspace has no tenants, the section shows No Tenants Configured and the button Add New Tenant, which opens the Tenants page. See Managing tenants.

When Okta, Auth0 or Microsoft reports an incident or maintenance that affects a tenant, the card shows a one-line banner with the headline. The banner is a link to that provider’s status page.

Hover over the banner to see the incident titles. It can also show The provider reports authentication as affected. and one of these scope lines:

  • Reported against the whole provider platform, not this tenant specifically.
  • Reported against the Auth0 region this login domain sits in.
  • Reported against this tenant.
Banner colour Meaning
Blue Planned maintenance
Red A critical incident, or one that affects authentication
Amber Any other incident

See Status and advisories.

Okta cards with monitoring configured show two extra rows: AD Agents and LDAP Agents.

Each row has an overall result:

What you see Meaning
Healthy, Warning, Critical or Unknown The overall state, with counts such as 2 agents · 1 offline · 1 update
Pending… Monitoring is on, but no check has finished yet
Not Monitoring Agent monitoring is switched off for this tenant

Under the overall result there is one line for each agent:

  • The agent name, or its host name.
  • The version, shown as v{version}.
  • A status badge: Operational, Active, Online, Degraded, Disrupted, Inactive, Offline, Down, Error or Unknown.
  • Update Available or Up-to-date.
  • Last seen: {date}, or Last seen: Unknown.

Hover over the row to read the monitor’s summary.

  1. Open Dashboard and go to Tenant status, then Okta tenants.
  2. On the tenant card, read AD Agents and LDAP Agents: first the overall badge, then each agent’s version, status badge, update badge and Last seen.
  3. If the row reads Not Monitoring, switch agent monitoring on from the tenant’s Edit page. If it reads Pending…, wait for the next check.
  4. In Tenant activity timeline, hover over the square markers to see when an agent went down, came back or was updated.

See Tenant health for the connection states.

Okta cards have a Tenant details button. Auth0 and Entra ID cards do not have a details dialog.

The dialog is titled Tenant details, with the subtitle Configuration and enabled Okta features. It shows:

Part Contents
Summary Tenant Name, Customer, Tenant ID, Type, Created, Updated
Okta Configuration An environment badge (Production or Development), Domain, Event Hook ID (or Not configured), Monitoring (Configured or Not configured) and Environment
Subscribed Event Types One badge for each event type the event hook sends, or No subscribed event types configured.
Enabled Features {n} Enabled, then each Okta feature with its name, description, stage and type
Disabled Features {n} Disabled, in the same layout

While the features load you see Loading Okta features…. An empty list reads No features are currently enabled for this tenant. or No disabled features found for this tenant.

  1. On the Okta tenant card, choose Tenant details.
  2. Read Okta Configuration: the domain, the Event Hook ID and the environment.
  3. Read Subscribed Event Types to see which events this tenant sends.
  4. Read Enabled Features and Disabled Features.
  5. Choose Close.

To change the subscribed event types, see Change event subscriptions.

A chart titled Tenant activity timeline, with the subtitle Alerting over retention period. It draws one coloured line for each tenant, with a legend.

Legend item Meaning
High-risk marker (risk 3+): {n} Round markers. Each is an event with a risk rating of 3 or more.
AD / LDAP monitor marker: {n} Square markers. Each is a change in an Okta agent: down, up again, update available or update installed.

Hover over a marker to read its details.

  1. Drag across the period you want to look at. The chart hint reads Drag to select and zoom.
  2. Hover over the markers for details.
  3. Choose Reset zoom to return to the full period. This button appears only while the chart is zoomed.

When there is no activity in the retention period the chart reads No events.

This card appears when the workspace has at least one Auth0 tenant. Its description reads API request volume and response type from every Auth0 tenant’s metric stream, combined.

It is the same explorer as each tenant’s API Metrics page, combined across all Auth0 tenants and grouped by tenant to start with. The range, group-by and filter controls work the same way. See Auth0 API metrics.

The last section, headed Event feed, holds the Real-time events card. This is the live feed. See Events.

Message Who sees it Meaning
Workspace created - your 30-day Super trial has started The person who created the workspace Shown once, after onboarding
{Tenant name} connection unhealthy, with Review settings Admins only A tenant’s credentials or monitoring are failing. Review settings opens the tenant’s Edit page. The message stays until you close it. It appears once for each tenant each time a page loads, on any workspace page.

The sidebar, the workspace switcher, the Plan card and the account menu are described in Finding your way. Alex at the bottom of the sidebar opens the Ask Alex panel.

What you see Why What to do
- in a card and the message Authentication required Your session expired Sign in again
- in a card and Access denied You are not a member of this workspace Ask a workspace admin to add you
- in a card and API error, API error ({status}), Invalid response format or Unable to load data The request for the statistics failed Reload the page. Report it if it continues.
No data available or N/A on Avg dismissal time Nothing was dismissed in that period Nothing. This is normal.
There is no Avg dismissal time card The card is not switched on for the workspace A platform operator switches it on
There is no Needs attention strip Automatic incidents are off for the workspace, or the plan does not include them See Incident settings
- in the strip and Could not load the incident summary. The request for the incident summary failed Reload the page
What you see Why What to do
Could not load tenant status grid: Missing workspace ID. The page loaded without a workspace Reload the page, or open the workspace again from the workspace switcher
Unable to load tenant configurations. or Unable to load active event statuses. A request for the tenant cards failed Reload the page
Authentication required for events Your session expired Sign in again
Access denied for events You are not a member of this workspace Ask a workspace admin to add you
Pending… on AD Agents or LDAP Agents Monitoring is on, but there is no check result yet Wait for the next check
Not Monitoring Agent monitoring is off for that tenant Switch it on from the tenant’s Edit page. See Managing tenants.
Monitoring requires attention or Status unavailable when you hover over an agent row The monitor reported a problem, or has no state Open the tenant’s Edit page and check the credentials. See Tenant health.
{Tenant name} connection unhealthy with Review settings (admins only) A tenant’s credentials or monitoring are failing Choose Review settings and fix the problem on the tenant’s Edit page
No Tenant details button on a card The tenant is Auth0 or Entra ID Nothing. The dialog exists for Okta tenants only.
What you see Why What to do
Okta scope okta.features.read is required to list features. The Okta integration does not have the okta.features.read scope Grant the scope to the integration in Okta. See Connect Okta.
Okta features were requested for this tenant moments ago. Try again in a minute. Identiguard limits how often it asks Okta for the feature list Wait a minute, then open the dialog again
Okta features have not been loaded for this tenant yet. They appear here once a workspace member has opened this tenant. A viewer opened the dialog before any member or admin had loaded the features Ask a member or an admin to open Tenant details once
Authentication required to load features. Your session expired Sign in again
Unable to load features. The call to Okta failed Try again. If it continues, check the tenant’s credentials. See Rotate credentials.
What you see Why What to do
Unable to load monthly tenant activity. The request for the chart failed Reload the page
No events No activity in the retention period Nothing. This is normal for a new or quiet workspace.

For problems with the feed itself, see Events: troubleshooting.