- Getting Started
- Users/Permissions/Roles
- Groups
- Scheduling
- Escalation Policies
- Integrations
- Prebuilt Integration
- Aveva
- Xitoring
- ServiceNow (Marketplace Application)
- N-Central
- Azure Monitor
- Airbrake
- Alerta
- AlertSite (SmartBear)
- API Fortress
- APImetrics
- Apica
- AppDynamics
- AppSignal
- Apteligent
- Aqua Security (SNS)
- Atatus
- Atlassian Confluence
- Auvik
- Automate.io
- AWS CloudTrail
- AWS Cloudwatch/SNS
- Axonize
- Azure
- Azure Logic Apps
- BMC Remedyforce
- BMC TrueSight Pulse
- Bitbucket
- BigPanda
- BPPM
- Bitrise
- BlazeMeter
- Bugsnag
- Cherwell
- Connectwise PSA™ Inbound & Outbound
- ConnectWise On-Premise Environments Requirements
- CircleCI
- Checkly
- Cisco Meraki
- CloudRadar
- CloudMonix
- Contrast Security
- Curity
- Dotcom-Monitor
- Datadog
- Dynatrace
- Datacake
- Datto RMM
- Detectify
- Devo (formerly Logtrust)
- Catchpoint
- Elastic-Kibana Watcher Integration
- Elecard Boro
- Errorception
- Epsagon
- Exoprise
- FreshDesk
- FreshDesk Outbound
- FreshService Outbound
- FreshService
- FireHydrant
- Flic
- Formant
- GitHub Issues
- Grafana
- Ghost Inspector
- GitGuardian
- GitLab
- Google Stackdriver
- Graylog
- HalolTSM
- HashiCorp Terraform Cloud
- Honeybadger
- Honeycomb.io
- Host-Tracker
- Hyperping
- Icinga
- Incinga1
- Inspector
- Instana
- IDERA
- Ixon Cloud
- BMS
- SyncroMSP
- Autotask Outbound 2025 New
- Healthchecks.io
- Autotask Inbound 2025 New
- Prebuilt Integrations Cont
- JitBit
- JIRA
- Jenkins
- Kayako
- Kentik
- Librato
- LibreNMS
- LogDNA
- Logentries
- Logtrust
- LogRocket
- Logz.io
- LogicMonitor
- Loggly
- Lightstep
- ManageEngine Service Desk Plus (Inbound)
- Manage Engine Service Desk Plus Outbound
- Microsoft Teams
- MongoDB Cloud
- Moogsoft
- Microsoft SCOM
- Monitis
- Nagios
- Nagios (API)
- Nodeping
- New Relic
- NetCrunch
- New Relic Legacy
- Observium
- Odown
- Orca Security
- OSNexus - QuantaStor
- Panopta
- Pingdom
- Pipedrive
- Power Admin(PA) Server Monitor
- Prometheus
- PRTG
- Prefect
- Pulsetic
- Quickbase
- Rackspace
- Radio Mast
- RapidSpike
- Raygun
- Redgate SQL Monitor
- Resmo
- Runscope
- Rollbar
- SearchStax - Managed Solr
- SecurityScorecard
- Segment
- Sematext
- Sentry
- Server Density
- ServerGuard24
- Scalyr
- Site24x7
- Slack
- Slack outbound
- SolarWinds
- SMAX Micro Focus
- Sumo Logic
- ServiceNow (Legacy Integration)
- ServiceNow Outbound
- Spiceworks
- Salesforce Case Management Outbound
- Salesforce Case Management (Inbound)
- Speedway
- Splunk
- Status.io
- Statuspage.io (Inbound)
- Status Page Outbound
- StatusDashboard
- Statuspal
- StatusHub
- StatusCast
- StatusCake
- Sysdig
- Terraform Cloud
- Travis CI
- Tideways
- ThousandEyes - Cisco
- Uptrends
- Updown.io
- Uptime.com
- Uptime Robot
- VMware
- VMware Tanzu (Wavefront)
- Webmon
- Webex Teams Outbound Integration
- Wormly
- Zabbix
- Zapier
- Zebrium
- Zendesk
- Zendesk Outbound
- Zoom
- Custom Integrations
- Inbound Integrations
- Outbound Integrations
- Integration Overview
- Prebuilt Integration
- Alert and Notification
- Workflows
- Workflows Overview
- Send a message using HTML
- Prebuilt Workflows
- Stop Delivery on Acknowledgement
- Acknowledge Alerts using Webhooks
- Direct alerts to different teams based on email keywords
- Run an Automation When an Alert is Created
- Run an Automation When an Alert is Closed
- Send a message to a specific user or group when an alert is created
- Send a message when an alert is assigned
- Send a message when an alert is closed
- Send a message when an alert closes automatically
- Send a message with update status every 30 minutes until an alert is closed
- Send a message when a custom field is modified
- ConnectWise PSA™ add Initial Descriptions to Alert Notifications
- Account Settings
- Live-Call Routing
- Analytics & Reporting
- Administration
- AlertOps Mobile App
- Product Updates
- Print
- Share
- DarkLight
- PDF
Email Integration Testing and Troubleshooting
- Updated on 17 Jul 2023
- 2 Minutes to read
- Print
- Share
- DarkLight
- PDF
Testing
Once your email integration is configured, you can test the integration's functionality by sending the following emails to the integration email address.
Send a Test Email
Using this template, send this email to open an alert in AlertOps.
Send an Email to Close the Alert
Send this test email to close the alert.
Troubleshooting
Once you have sent the test emails, we can view the inbound log to see if the signal has come through correctly.
Inbound Log
Use the Inbound Log to view all incoming alerts. This can be found at the bottom of the Integrations page.
- Id– Identifier for each alert
- Key Mapping Fields – Source, Source Name and Source Identifier show the data that was used in the message for mapping purposes.
- Integration– the integration to which the message was matched.
- Mapping – Mapped, Mapping Failed, Mapped Ignored, Pending, Processing, Mapped Appended
- Alert ID – link to the AlertOps alert detail.
Mapping Status | Descriptions |
Mapped Ignored | A new alert with a close status was received and there are no matching open alerts to be closed (possibly a user manually closed the alert, and the monitoring system detected the close and sent a new close alert), or an alert was received without a valid status value. |
Pending | Awaiting processing. This is a temporary state that can last up to one minute. |
Mapped | Successfully processed. This will occur for both new alerts when they are opened and existing alerts when they are closed. |
Processing | Currently processing. This is a temporary state that will appear only for a second. |
Mapped Appended | This can mean that a duplicate alert was received, such as receiving another Open status alert for an alert that is already open. |
Mapping Failed | Unable to match the message to an Integration. |
Common Problems
Problem: The message is not found in the Inbound Messages table.
Solution: Check to see if you have sent the email to the correct email address.
Problem: The message can be found in Inbound Messages, but the status is Mapping Failed.
Solution: Check that the Source Name data matches the Source Name in the Mapping Field.
Problem: The Status is Mapped but you did not receive any notifications.
Solution 1: Check that the Source Identifier data matches the Source Identifier in the Mapping Field.
Solution 2: Verify that the notifications were sent out by AlertOps. Click the AlertID link on the right to view the alert details. View the members that were notified to confirm. Click the first message in the Messages List to view the Notification Delivery details.