Monitor Alerts
What is the Alerts module for?
The Alerts module in Moveworks serves as a critical tool for monitoring the system's health. It provides timely notifications when a bot skill malfunctions or a configuration error occurs. In a reactive fashion, these alerts are triggered when issues are detected within the bot configuration or as part of data ingestion.
How to navigate?
- Open Moveworks Setup.
- Navigate to the Alerts menu item nested within the Command Center section.
Understanding columns in Alerts home screen
- Module: The segment of the system where the alert originates.
- Alert ID: A unique identifier assigned to each alert.
- Alert Name: The title that describes the essence of the alert.
- Alert Description: A brief explanation providing context to the alert.
- Alert Type: The category that the alert falls into, typically indicating its severity or nature.
- Last Fired at: The most recent time and date when the alert was last triggered.
- Total Times fired: Count of times the same alert was fired.
- Active Since: Time from which a specific alert is active.
- Acknowledged By: User who is acknowledging an active alert in the UI.
There are 3 states a alert can be present in
- Active - These are the active alerts that are currently being fired from your system.
- Acknowledged - These are the active alerts that are currently being fired from your system and an MW setup admin has read and acknowledged the alert. The user who has acknowledged can be found in the acknowledged by column in the alerts table
- Archived - These are historical alerts that were fired from your system.
Key highlights
- The integration failure alerts are only raised for the systems that are configured in identity module. But these failures also impact other downstream Movework's Services.
- Only last 2 months of archived alerts are available in setup
Applicable Alerts within Moveworks Setup
| Module | Alert Name | Alert Type | Alert Description | Downstream Alert Impact |
|---|---|---|---|---|
| Connector | Integration Failure - Active Directory | System Alert | System is failing to connect with Active Directory. Please check credentials and the authentication system used | Import Users, Account Access, Group Access, Employee Comms |
| Connector | Integration Failure - ServiceNow | System Alert | System is failing to connect with ServiceNow. Please check credentials and the authentication system used | Import Users, Knowledge Ingestion, Forms Ingestion, Resource Permissions Ingestion, Ticketing, Approvals |
| Connector | Integration Failure - Microsoft Graph | System Alert | System is failing to connect with Microsoft Graph. Please check credentials and the authentication system used | Import Users, Knowledge Ingestion, Forms Ingestion, Group Access, Account Access, ChatBot Functionality |
| Connector | Integration Failure - Okta | System Alert | System is failing to connect with Okta. Please check credentials and the authentication system used | Import Users, Account Access, Employee Comms |
| Connector | Microsoft Teams - Message Authentication Failure | System Alert | Failure to authenticate Microsoft Teams inbound messages | Bot Unresponsive to user/users in the Chat Interaction Platform. |
| Connector | Chat credentials expired | System Alert | Chat system responded with "401 - Unauthorized". This means that the existing credentials are no longer valid and the bot is unable to send messages to the users. | Bot Unresponsive to user/users in the Chat Interaction Platform. |
| Connector | ServiceNow Service Account Timezone Mismatch | System Alert | The timezone of the ServiceNow service account configured as a Moveworks connector does not match one of the expected timezones ('GMT', 'GMT0', 'UTC', 'America/Danmarkshavn'). | In Ticketing > Ticket Polling would be unable to poll tickets due to the invalid timezone. |
| Connector | Ticketing - Error reading from external ITSM system | Configuration Alert | Read action is invalid due to permissions or credentials. | In Ticketing > Ticket Polling would fail, Approvals > Approvals polling would fail |
| Connector | Ticketing - Error writing to external ITSM system | Configuration Alert | Write action is invalid due to permissions or credentials. | In Ticketing > Ticket Creation & Ticket Updation would fail, Approvals > Approve/Reject action would fail |
| Internal Knowledge | Knowledge Ingestion - Large drop in articles | Configuration Alert | Seeing a large drop in ingested knowledge articles for {{ integration }} - {{ domain }}. Please check configuration for internal knowledge. | Internal Knowledge would have a gap in content. |
| Ticketing | Invalid configuration(s) of create/update ticket method(s) | Configuration Alert | Encountered ticket attributes mapping error when trying to process request. | In Ticketing > Ticket Creation & Ticket Updation would fail, Approvals > Approve/Reject action would fail |
| Ticketing | Current configuration of create/update ticket payload considered invalid by external ITSM system | Configuration Alert | Invalid mapping for a create or update ticketing payload. | In Ticketing > Ticket Creation & Ticket Updation would fail, Approvals > Approve/Reject action would fail |
| Ticketing | Missing configuration(s) for create/update ticket method(s) | Configuration Alert | Missing mapping for a create or update ticketing payload. | In Ticketing > Ticket Creation & Ticket Updation would fail, Approvals > Approve/Reject action would fail |
| Ticketing | Invalid ticketing state configuration | Configuration Alert | Invalid state mapping, an internal state is likely not mapped. | In Ticketing > Ticket Polling & Ticket update notifications would be impacted. |
| Ticketing | Ticketing - Tickets are not passing the Universal ticket filter | Configuration Alert | No tickets have passed universal filter. Check ticket filters (particularly Universal ticket fetching filter) to make sure it is correct. | Tickets will not be considered by the AI Assistant for Resolution. |
| Identity | User validation failed | Configuration Alert | User identity validation failed. | If not fixed over time this will impact : Import Users, Ticketing, Knowledge Search, File Search, Account Access, Group Access, Employee Comms |
| Identity | Identity Ingestion - Large drop in ingested users (Upcoming) | Data Alert | Identity User drop Alert description - Seeing a large drop in ingested users. Please check configuration for identity. | Existing users who are no longer being ingested due to the drop will loose Bot access after 7 days. |
| Chat | Microsoft Teams Bot is unable to self-install | External Alert | Microsoft Teams bot doesn't have permissions to install itself for users | Bot Unavailable to user/users in the Chat Interaction Platform. |
| Chat | Bot has been disabled by admin | External Alert | The bot has been disabled and is unable to send messages to users and/or users may be unable to locate the bot in their chat client. Please reach out to your Microsoft Teams admin to get the bot re-enabled in your Teams admin console. This may also require modifying the app's Permission Policy. | Bot Unavailable to user/users in the Chat Interaction Platform. |
| File Search | File Ingestion - Exceeded limit of files to ingest | Data Alert | Recent File Search ingestion exceeded file limit. No new files were ingested, please refer to Control Center to identify new files causing limit overload. | Files Ingestion impacted. |
| File Search | File Ingestion – Failed to ingest certain files | Configuration Alert | Recent File Search ingestion had failed libraries, and certain files were not ingested. Please check your configurations and validate each attempted configuration. | Certain Files are missing from the ingested set. |
| Agent | Agent disconnected | External Alert | There are no Moveworks on-prem agents connected. | Import Users, Account Access, Group Access, Employee Comms |
Updated 8 days ago