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 Organization Details > Alerts
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 triggered and resolved.
Points to Note
- The integration failure alerts are only raised for the systems that are configured in identity module. But these failures also impact other downstream Moveworks' Services.
- An Alert gets moved to the Archived section if alert expression criteria is resolved internally.
- The archived alerts section contains a history of the last 2 months of alerts.
Applicable Alerts within Moveworks Setup
Module | Alert Name | Alert Type | Alert Description | Downstream Alert Impact |
---|---|---|---|---|
Connector | Integration Failure - {System} | System Alert | System is failing to connect with {System}. Please check credentials and the authentication system used | Import Users, Account Access, Group Access, Employee Comms |
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 |
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. |
Agent | Agent disconnected | External Alert | There are no Moveworks on-prem agents connected. | Import Users, Account Access, Group Access, Employee Comms |
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. |
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. |
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 | Microsoft Teams - Message Authentication Failure | System Alert | Failure to authenticate Microsoft Teams inbound messages | Bot Unresponsive to user/users in the Chat Interaction Platform. |
Updated 12 days ago