Monitor Alerts
What are Alerts?
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 post-detection of any issues within the bot configuration or data ingestion.
How to navigate?
- Open Moveworks setup via Studio home of your org.
- Navigate to Alerts menu item within 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
- Only last 2 months of archived alerts are available in setup
Applicable Alerts within Moveworks Setup
| Module | Alert Name | Alert Type | Alert Description |
|---|---|---|---|
| Connector | Integration Failure - {{integration name}} | System Alert | System is failing to connect with {{integration name}}. Please check credentials and the authentication system used |
| Connector | Microsoft Teams - Message Authentication Failure | System Alert | Failure to authenticate Microsoft Teams inbound messages |
| 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. |
| 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'). |
| Connector | Ticketing - Error reading from external ITSM system | Configuration Alert | Write action is invalid due to permissions or credentials. |
| Connector | Ticketing - Error writing to external ITSM system | Configuration Alert | Read action is invalid due to permissions or credentials. |
| Internal Knowledge | Knowledge Ingestion - Large drop in articles | Configuration Alert | Seeing a large drop in ingested knoweldge articles for {{ integration }} - {{ domain }}. Please check configuration for internal knowledge. |
| Ticketing | Invalid configuration(s) of create/update ticket method(s) | Configuration Alert | Encountered ticket attributes mapping error when trying to process request. |
| 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. |
| Ticketing | Missing configuration(s) for create/update ticket method(s) | Configuration Alert | Missing mapping for a create or update ticketing payload. |
| Ticketing | Invalid ticketing state configuration | Configuration Alert | Invalid state mapping, an internal state is likely not mapped. |
| 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. |
| Identity | User validation failed | Configuration Alert | User identity validation failed. |
| 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. |
| Access Software | Access Software - Group does not exist in source system | Configuration Alert | Group name does not exist in external system. Software provisioning will fail for this application. |
| Chat | Microsoft Teams Bot is unable to self-install | External Alert | Microsoft Teams bot doesn't have permissions to install itself for users |
| 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. |
| 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. |
| 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. |
| Agent | Agent disconnected | External Alert | There are no Moveworks on-prem agents connected. |
Updated 3 months ago