Skip to content

Events

The event feed is the last section of the dashboard, under the heading Event feed. The card is titled Real-time events. It updates as events arrive.

Every role can read the feed. Admins and members can dismiss events and raise tickets. Viewers see those buttons greyed out.

The same feed is also available as a full page at /workspaces/{workspace ID}/events. That page is not in the sidebar. The Identiguard Event Link in a ticket opens it.

The chip beside Real-time events shows the state of the live connection.

Chip Colour Meaning
Connected Green The feed is live
Connecting… Amber, with a spinner The page is opening the connection. The table area reads Connecting to event feed…
Closed Red The connection dropped. The table area reads Connection closed.
Error Red The connection could not be opened. The table area reads Connection error.

While the chip reads Closed or Error, the table, the filter results and the page controls are hidden.

The page tries to reconnect every 5 seconds by itself. Each time it reconnects, the feed is cleared and loaded again, so events that someone else dismissed while you were disconnected disappear.

The page does not retry when the problem is permission, a locked workspace, or a connection that the server closed for a security reason. See Fix a feed that is not live.

Column Meaning
Origin The platform the event came from
Tenant The tenant name
Event Type The provider’s name for what happened
Severity DEBUG, INFO, WARN, ERROR or CRITICAL. See Severity and risk rating.
Source The first part of the tenant’s host name, for example the Okta subdomain, or Microsoft Graph
Actor Who or what did it
Target Who or what it was done to
Message The provider’s description
Timestamp When Identiguard received the event, in your local time, for example Today, 02:15 PM, Yesterday, 02:15 PM or Mar 4, 02:15 PM
Risk Rating 1 (low) to 5 (high), shown as {n}/5 with a coloured dot
Actions The buttons for this event

Things to know about the table:

  • The newest event is first.
  • Select a column heading to sort by it. The first click sorts from high to low (or Z to A). The second click reverses it. Every column except Actions sorts. Severity sorts by level, not by alphabet.
  • The table shows 15 rows on each page. The footer reads Showing {a} to {b} of {n} events and has a Page drop-down, arrows and numbered page buttons.
  • Long values in Source, Actor, Target and Message are cut short. Hover over the cell to read the full value.
  • On a narrow screen the table scrolls sideways.
  • The legend above the table reads Risk Rating: 1 2 3 4 5 (1: Low Risk, 5: High Risk). The colours are green, lime, orange, red and purple.
  • The feed has no export, copy or download for events or payloads.

When a priority rule set matches an event, the row has a coloured left border. Risk Rating shows your score with a small flag icon. Hover over the flag to read Priority set by rule set {name}. The Severity column still shows the provider’s severity.

Control What it does
Search event types… Matches the event type and the source. It ignores capital letters. It does not search the actor, the target or the message.
The tenant drop-down Narrows the feed to one tenant. The default is All Tenants.
History How many recent events to load: 100, 200, 500 or 1000. The default is 100.
From and To A date range. Each date is a whole day in your local time, from 00:00:00 to 23:59:59.
Flagged only Shows only events that a priority rule set matched, with any score from 1 to 5

Any change to a filter returns you to page 1.

The information icon beside the filters reads Loads up to {History} recent events. Set a date range to filter. While history loads you see Loading history….

What you see Meaning
No events found. Waiting for new events… No active events are loaded
No events match the current filters. with Clear filters Events are loaded, but the filters hide all of them

Clear filters resets the search, the tenant and the dates. It does not untick Flagged only and it does not change History.

See Find only prioritised events.

Each row has these buttons in Actions:

Button What it does Who
View Opens Event Details Every role
Ask Alex AI Asks the assistant to explain this event Every role
Raise Ticket Creates a ticket for this event. Shown only when ticketing is connected. Admin, member. Viewers see it greyed out.
Dismiss Dismisses this event straight away Admin, member. Viewers see it greyed out.

Choose View on a row to open Event Details. The subtitle reads Detailed information about the selected event.

The dialog shows these fields:

Field Notes
Event Type
Severity The provider’s severity
Analyst priority Shown only when a priority rule set matched: {n}/5 set by rule set {name}
Source
Actor
Target
Tenant The tenant ID
Tenant Name
Timestamp
Event ID
Message
Payload The raw event as JSON. Scroll to read all of it.

The buttons at the bottom appear only when they apply, in this order:

Button When it appears What it does
View incident Only when the event belongs to an incident Opens that incident
Explore correlations When the event has a tenant Opens Correlations for this tenant and event
Raise Ticket Only when ticketing is connected Creates a ticket. It reads Raising… while it works. Greyed out for viewers.
View in Okta Okta events that carry an Okta event ID Opens the Okta admin System Log search for this event in a new tab. You need admin access to that Okta org.
Dismiss Event Always Dismisses the event and closes the dialog. Greyed out for viewers.

The dialog has no Ask Alex AI button. Use the one on the row. To close the dialog, use the X, press Esc, or click outside it.

Go from an event to its incident, its correlations or the Okta log

Section titled “Go from an event to its incident, its correlations or the Okta log”
  1. Choose View on the row.
  2. Choose one of:
    • View incident, if the button is there.
    • Explore correlations. See Run a correlation.
    • View in Okta, for an Okta event.

Ask Alex AI is on every row and works for every role.

  1. In Real-time events, choose Ask Alex AI on the row.
  2. The Alex panel opens and sends a question for you. The question asks what happened, whether it is a risk in this workspace, and what to do next.
  3. Ask follow-up questions in the same thread. They stay on that event.

Alex receives the event’s severity and, when a priority rule set matched, your priority score and the rule set name. It quotes the same score that you see in the feed. See Ask Alex.

Raise Ticket appears on each row and in Event Details only when ticketing is connected for the workspace. One click creates the ticket. There is no form.

See Raise a ticket from an event for the steps and for what the ticket contains.

Dismissing an event marks it as dealt with. It leaves the feed and the active count.

Admins and members can dismiss. Viewers see the buttons greyed out.

Button Where Confirmation
Dismiss On the row None. It happens when you click.
Dismiss Event In Event Details None. The dialog closes straight away.
Dismiss All In the table footer, left of the Page drop-down A dialog: Dismiss all {N} events? with Cancel and Dismiss all

There is no success message. The row disappears.

While a dismissal is in progress, every Dismiss button and Dismiss All are disabled.

Okta and Auth0 events are dismissed over the live connection, so the chip must read Connected. Entra ID events are dismissed by a separate request. They can be dismissed while the chip is not Connected, but that request can be rate limited.

  • The number in the dialog, Dismiss all {N} events?, is the number of events loaded. It can be higher than the number in Showing {a} to {b} of {n} events when the search box or Flagged only is in use.
  • It covers every page, not only the 15 rows on screen.
  • The tenant drop-down and the From and To dates do limit which past events are loaded. New live events from any tenant are still added to the loaded list.
  • History limits how many events are loaded, to a maximum of 1000. In a busy workspace you may need to use Dismiss All more than once.
  • Dismiss All is disabled when the filtered list is empty.

The dialog text reads Every event currently in the feed will be marked as dismissed. This cannot be undone.

If some events could not be dismissed, they stay on screen and a message tells you how many. See Troubleshooting.

  • The event leaves the feed of every user in the workspace, straight away.
  • The event is not deleted. It is stored as dismissed, with the email address of the person who dismissed it and the time. It stays until event retention removes it.
  • A dismissed event does not come back when you reload the page.
  • Active events on the dashboard goes down. Total Tracked Events does not change, because it counts dismissed events too.
  • The tenant card loses its {n} Events badge and returns to All clear when its last active event is dismissed.
  • Avg dismissal time uses the time from when the event was received to when it was dismissed.
  • Dismissing an event does not close an incident. Close incidents on the Incidents page.

For the steps, see Dismiss events.

A sound plays in your browser for each new live event.

  • It plays only while a page with the feed is open: the dashboard or the full-page feed.
  • Loading history does not play a sound. An update to an existing Entra ID event does not play a sound.
  • Browsers can block sound until you have clicked or typed on the page. When this happens there is no message.
  • There are six sounds: Notification Beep (the default) and Alert 1 to Alert 5.
  • An admin chooses the sound, or switches on Mute alert sounds, under Policies. Both are available on every plan. See Change retention and policies.
  • Mute alert sounds applies to everyone in the workspace. There is no setting for one user.
  • A change takes effect the next time the feed loads. Reload the page.
  1. Read the chip beside Real-time events.
  2. If it reads Connecting… or Closed, wait up to 10 seconds. The page retries every 5 seconds.
  3. If it is still not Connected, read the message that appeared:
    • A message about permission: sign in again, or ask an admin to check that you are still a member.
    • This workspace is locked until its billing is resolved.: an admin must resolve billing. See Manage billing.
    • Any other message: reload the page.
  4. If it never connects, check that your network, VPN or proxy allows WebSocket connections to dash.identiguard.app.
  5. When the chip reads Connected, the feed loads again by itself.
What you see Why What to do
Connecting… and Connecting to event feed… The page is opening the live connection Wait a few seconds. If it never reads Connected, check that your network, VPN or proxy allows WebSockets to dash.identiguard.app, then reload.
Closed, Connection closed. and Connection closed (Code: {code}). Retrying… The connection dropped, for example a network break or a product update. The page retries every 5 seconds. Wait. It reconnects and reloads the feed. Reload the page if it continues.
Error, Connection error. and WebSocket connection error., Failed to initiate WebSocket connection. or Failed to get WebSocket ticket ({status}) The connection could not be opened. The page retries every 5 seconds. Check your network. Reload the page. Sign in again if your session expired.
You do not have permission to view real-time events for this workspace. The chip reads Closed and does not retry. Your session expired, or you were removed from the workspace Sign in again. Ask an admin to confirm you are a member.
This workspace is locked until its billing is resolved. The chip reads Closed and does not retry. The workspace is paused An admin resolves billing. See Plans and billing.
Connection closed: {reason}, with no retry The server closed the connection for a policy or sign-in reason Reload the page and sign in again
Failed to process server message. The page received a message it could not read Reload the page. Report it if it repeats.
Failed to load event history: {detail} The request for past events failed. The detail can be a permission message, a service error or a rate limit. Change History or reload to try again. If the detail mentions too many requests, wait a minute.
Too many requests. Try again in 60 seconds. You reached the request limit for one user Wait 60 seconds. Avoid many open tabs that refresh at the same time.
Could not load event feed component: Missing required data. or Could not load necessary data (workspace or user information) for the event feed. The page loaded without the workspace or your sign-in details Reload the page. Sign in again.
No events found. Waiting for new events… Nothing active is loaded: the tenant is not sending, everything is dismissed, or the dates exclude the events Check Tenant health. Clear the dates. Raise History.
No events match the current filters. with Clear filters The search, tenant, dates or Flagged only hide everything Choose Clear filters. Untick Flagged only.
Flagged only is greyed out and reads (priority rules unavailable) The priority rules could not be loaded. Hover text: Priority rules could not be loaded. Reload the page, or switch to another browser tab and back. The feed still works, with ratings from severity.
No sound for new events The workspace is muted, the browser blocked the sound, or the feed is not open Click anywhere on the page. Ask an admin to check Mute alert sounds under Policies. Reload after a change.
What you see Why What to do
Dismiss, Dismiss Event and Dismiss All are greyed out You are a viewer, or another dismissal is in progress Wait a moment. If you are a viewer, ask an admin for the member role.
Your role does not allow dismissing events. Contact an admin for help. or Your role does not allow dismissing events. You are a viewer Ask an admin for the member role. See Members and roles.
Cannot dismiss event: Connection not active. An Okta or Auth0 event needs the live connection, and it is not open Wait for Connected, then try again
Cannot dismiss event: user information unavailable. or Cannot dismiss events: user information unavailable. The page does not have your sign-in details Reload the page. Sign in again.
Cannot dismiss event: event not found. The event was already removed, usually because someone else dismissed it Nothing. Reload if the row is still there.
Failed to dismiss Entra event: {message}, for example Forbidden or Too many requests. Try again in 60 seconds. The request to dismiss an Entra ID event failed Try again after a minute. Check your role.
Failed to dismiss Entra event: the server did not confirm it. The server did not confirm that event. It may already be dismissed. Reload the page
Failed to dismiss event: {detail} or Failed to dismiss events: {detail} An unexpected error in the page Reload the page and try again
No events to dismiss. You chose Dismiss All with nothing loaded Nothing
Dismissed {n} events. {m} failed. Some events were not dismissed. The live connection was not open, or an Entra ID request failed. Check the chip reads Connected, then choose Dismiss All again. The events that failed are still on screen.
Dismissed {n} events. {m} left - too many requests, try again in a minute. Entra ID events reached the rate limit Wait a minute, then choose Dismiss All again
Failed to process message The dismissal failed on the server Try again. Report it if it repeats.
Dismiss All left events in the feed, with no message More active events exist than History loads Choose Dismiss All again
You dismissed an event by mistake There is no undo and no view of dismissed events Find the event in the provider’s own log. If the record must be recovered, raise it with the product team.

For ticket messages, see Raise a ticket from an event. For priority rule sets, see Event priorities.