Notification Settings in ObserveOps
Notification settings let you decide who gets told, and through which channel, when ObserveOps detects a problem with its own platform components or with the database backup job. You configure each event category once. Every future alert of that type is routed to the recipients, chat channels, and ITSM tools you selected here.
Prerequisites
- Mail Server Settings and SMS Server Settings already configured under System Settings if you want email or SMS delivery.
- A Microsoft Teams or Slack integration profile if you plan to use those collaboration channels. Configure it under Settings > Integration.
- An integration profile for Atlassian Jira, ServiceNow, Motadata ServiceOps, Syslog, or SNMP Trap if you want ObserveOps to raise a ticket or forward the alert.
- A user profile created under User Settings if you want to address recipients as
#UserProfileinstead of individual users.
How It Works
Every card on this page maps to one internal event category that ObserveOps monitors on its own. When any trigger inside that category fires, ObserveOps sends the alert to every recipient listed in the card, posts it to the linked Teams or Slack workspace, and hands it to every selected integration profile so an ITSM ticket is created or a Syslog or SNMP Trap message is forwarded. Recipients and integration profiles are stored per category, so Platform Health and Database Backup can go to different people. Changes take effect the next time an event of that category fires and stay in effect until you select Save with new values.
Where to Find It
Go to Menu. Select Settings 
. Expand System Settings in the left sidebar and select Notification at the bottom of the list.
It opens the System Health tab. Each collapsible card on the tab represents one event category. Select the chevron on the top-right of a card header to collapse it or expand it back.
Event Categories on the System Health Tab
| Card | What Triggers a Notification |
|---|---|
| Platform Health | Self-monitoring of the ObserveOps App, DB, observer, and collector components. Covers disk usage, service availability, heartbeat, clock, and license conditions. |
| Database Backup | Scheduled backup job outcomes and the storage location for backups. |
Select the Notifications link inside the description of any card to open the Notification Information drawer on the right. The drawer lists every event that can fire inside that category and the exact reason ObserveOps raises each one.
Platform Health Triggers
| Event | When ObserveOps Raises It |
|---|---|
| Disk Usage % | Disk space consumption crosses configured thresholds, risking application or OS failure. |
| Disk Write Latency | Disk write operations are slower than expected, potentially causing data pipeline delays. |
| Observer Service Down | The Observer service is stopped or unreachable, creating a monitoring blind spot. |
| Observer Heartbeat Missing | The expected Observer heartbeat is not received within the defined interval. |
| Clock Drift | A component clock drifts from the reference time, which skews metric timestamps and alert correlation. |
| Licence Quota | Monitored-object usage approaches or exceeds the licensed quota, after which new objects stop being polled. |
Database Backup Triggers
| Event | When ObserveOps Raises It |
|---|---|
| Backup Not Configured | No backup schedule exists, leaving the deployment with no recovery point. |
| Backups On Local Storage Only | Every backup target is local, so the loss of the host takes the backups with it. |
Configure the Notification Channel
Both cards use the same three-part Notification channel block. Fill it in for every category you want alerts from.
Recipients
The people who receive the alert. The three icons next to the Recipients label show which delivery methods a recipient can be reached through: email, in-app user, and mobile.
| Input | What to Type | What Happens |
|---|---|---|
| User | Type @ and select a username from the list, for example @admin. | The user receives the alert through every method their profile permits, including email and in-app. |
| Email address | Type the full email address, for example oncall@company.com. | Delivered as an email through the configured mail server. |
| Mobile number | Type the mobile number in international format. | Delivered as an SMS through the configured SMS server. |
| User profile | Type # and select a user profile from the list. | Every user in that profile receives the alert. |
After you type a recipient, select the green check icon next to the field or press Enter to add it as a tag. Separate multiple recipients with a comma or press Enter after each. Select the × on a tag to remove that recipient. @admin is added by default and can be removed the same way.
If no user profile exists yet, the # picker shows an empty state. Create a user profile under User Settings first, then return here.
Collaboration Channels
The team chat workspace the alert is posted to. Both channels are optional and independent.
| Button | Where It Takes You | What You Set Up There |
|---|---|---|
| Integrate MS-Teams | Settings > Integration > Microsoft Teams | A credential profile for the Teams tenant, a connection time-out, and an auto-sync toggle. Save the profile to activate the channel. |
| Integrate Slack | Settings > Integration > Slack | A four-step wizard that signs you in to Slack, uploads the manifest file, selects a credential profile, and configures auto-sync and proxy options. Save the profile to activate the channel. |
Once the Teams or Slack integration profile is saved, alerts for the linked category post to the workspace automatically. Return to Notification to attach the profile through the Select Integration Profile dropdown.
Select Integration Profile
The integration profile that turns the alert into a ticket in your ITSM tool or forwards it as a Syslog or SNMP Trap message. Leave the field empty if you do not want any ticket or forwarded message.
Select the field to open the profile picker. The picker is a searchable, multi-select table with three columns.
| Column | What It Shows |
|---|---|
| Integration Profile Name | The profile name you set when you created it. Select the column header to sort ascending or descending. |
| Description | The optional description you entered at creation time, blank if none. |
| Integration Type | The destination system, for example ServiceNow, Atlassian Jira, Motadata ServiceOps, Syslog, or SNMP Trap. |
Type in the search box to filter the list. Select the checkbox on every profile you want to attach. Attach as many as you need, so a Platform Health alert can raise a ServiceNow incident and a Jira ticket at the same time.
If the dropdown is empty, no integration profile has been created yet. Go to Settings > Integration to create one, then reopen this page.
Select Save to apply the changes for both Platform Health and Database Backup.
Select Reset to discard unsaved changes.
Example
A NOC lead wants the on-call engineer to hear about platform trouble on Slack and get an incident ticket in ServiceNow, and wants only the backup admin paged about backup gaps. In the Platform Health card, the lead adds #oncall-engineers as the recipient, selects the Slack integration profile in the picker, and also selects the ServiceNow integration profile. In the Database Backup card, the lead adds the backup admin's email and leaves Select Integration Profile empty. From that point, Observer heartbeat, disk, and clock alerts wake up the on-call engineer, post to Slack, and open a ServiceNow ticket. A missing backup schedule only emails the backup admin.