Docs > Configuration > Getting Started With Alerts
1. Getting Started with vuSmartMaps™
3. Console
5. Configuration
6. Data Management
9. Monitoring and Managing vuSmartMaps™
vuSmartMaps powerful alerting capabilities empower you to stay informed, take swift action, and optimize your operational efficiency. vuSmartMaps comes pre-packaged with standard alerts for standard infrastructure components. You can change the thresholds and other logic as per your needs. Stay in control and respond effectively to events with vuSmartMaps Alerting.
Key Features of vuSmartMaps Alerts:
Create an Alert Rule involves configuring 2 mandatory and 4 optional sections that enable you to tailor your alert rules according to your specific requirements.
You can set up a Simple Alert by entering the Basic Details and configuring a single Data Model.
1. Basic Details include a Summary and Description.
2. Data Models to be alerted on let you choose a Data Model, specify the evaluation timeframe, and create conditions based on the selected Data Model’s metrics and thresholds. You can add multiple Data Models in a single alert under different rules (R1. R2, etc).
Include the previous steps from Simple Alert Creation, that is, Basic Information and Data Models and continue to configure Logic Conditions explained further.
3. Logic Conditions You can use metric values to determine when to send notifications, change their content, and select recipients and channels, giving you control over when, what, and to whom alerts are sent.
Include the previous steps from Simple Alert Creation and Compound Alert Creation, that is, Basic Information, Data Models and Logic Conditions, and continue configuring the Evaluation Script and Alert Controls as explained further.
4. Evaluation Script provides advanced control over how your alert rules behave. You can define a list of condition blocks, each with conditions and actions, along with comparison rules. These scripts determine when alerts are generated, who receives them, and what the notifications contain, with rules executed one by one until a match is found.
5. Alert Controls help manage alert notification generation. You can schedule alert rule execution, enable or disable alarm mode to control notification timing, set up throttling for the non-alarm mode to prevent repetitive alerts, and configure when alerts should be active to avoid notifications during specific periods, such as weekends or non-business hours.
6. Alert Channels allow you to manage how notifications are delivered. You can use email, WhatsApp, SMS, Runbook Automation, Slack, and MS Teams for communication. Configure recipients, groups, and message content to tailor alert content to your needs.
💡Note:
The minimum requirement is to configure a Data Model and a Notification Channel.
Navigate to the Alerts section and create a new alert rule. Choose the Data Model and set the condition to trigger when CPU utilization exceeds 95%. Choose WhatsApp as the notification channel. Enter your mobile number or group for WhatsApp notifications. Save the alert rule and activate it.
Yes, by using Simple Alert creation. Fill in the Basic Details, choose the transaction volume data model, set your evaluation timeframe, and configure the condition to trigger when transaction volumes fall below 1,000 transactions per minute.
Create a Compound Alert. Start with Basic Details and Data Models (transaction failure rate and transaction duration). Then, use Logic Conditions to specify that both failure rates must be above 5% and transaction durations must exceed 10 seconds for the alert to trigger.
Yes, use Compound Alert creation. Input the Basic Details, select data models for transaction volumes and failure rates, and set up Logic Conditions to trigger an alert when transaction volumes exceed a certain threshold and failure rates increase.
Yes, with Programmable Alerts. After configuring Basic Details, Data Models, and Logic Conditions, use the Evaluation Script for detailed conditions and actions. Then, use Alert Controls to schedule alert execution and set active periods to avoid alerts during non-business hours.
Alert traffic or noise can be a significant issue, especially in high-volume environments. Enable throttling under the “Alert Control” option to prevent repeated notifications for the same condition within a specified interval. Adjust the severity and thresholds of your alerts to ensure you only receive critical notifications.
Yes, you can configure active periods for alert notifications under the Alert Control option to match your business hours or specific operational windows. This setup helps avoid unnecessary notifications during low activity periods.
vuSmartMaps supports mobile notifications via WhatsApp and SMS.
Start by reviewing the alert rule configuration to ensure conditions and thresholds are accurately set. Verify the data models used and adjust the alert conditions if necessary. If the issue persists, consult the support team for further assistance.
In non-alarm mode under Alert Controls, the system will continue generating notifications at regular intervals as long as the alert conditions remain true.
Implement a buffer in your evaluation script by setting a buffer range around your thresholds. Alerts will only be generated if the metric exceeds the threshold significantly, reducing alerts for minor fluctuations.
Sure! For example, you can create an alert rule with the following conditions:
By configuring these conditions, an alert will only trigger when both conditions are met, ensuring a more comprehensive alert.
If you receive a permission denied message when accessing some particular module, contact your system administrator. They can review and adjust your permissions to ensure you have the necessary access.
Browse through our resources to learn how you can accelerate digital transformation within your organisation.
VuNet’s Business-Centric Observability platform, vuSmartMaps™ seamlessly links IT performance to business metrics and business journey performance. It empowers SRE and IT Ops teams to improve service success rates and transaction response times, while simultaneously providing business teams with critical, real-time insights. This enables faster incident detection and response.