Alerts are how Eido sends issues it detects to other tools such as Slack or ServiceNow, meaning that you don’t have to live in Eido to understand the state of your Intune estate and can simply manage the issues as they arise
Alerts can be configured to send issues to the below destinations and are created by clicking the Create Alert button. When creating an Alert you will always need to configure the following
- Friendly name – simply to identify the Alert in the list of Alerts
- Alert Type – whether to alert on either
o Device issues, including issues relating to Compliance policies, Config policies, Managed App issues
o Certificate issues, issues related to Apple device certificates, visible under the Certificates node
- Alert On – whether to alert on Amber or Red alerts, note if Amber is selected then Red issues will be sent in addition to Amber ones
The only additional property required to configure email alerts is the address that eido alerts are sent from (the Email property)
Mails are sent from no-repy@eido.cloud via our SMTP servers automatically, no additional setup steps are needed. Custom mail routing is not possible at this time.
Teams alerts require a Webhook URL to the teams channel that will be used to receive Eido alerts and details on Webhook authorization headers if required
To create a Webhook URL for a specific channel within Microsoft Teams follow these steps:
Click the three dots next to the channel you want to connect and click Manage Channel
Click Edit under the Connectors section on the Settings screen that is displayed
Find “Incoming Webhook” in the list and click configure
For more information on how to create an Inbound Webhook in Microsoft Teams see their product documentation: Create an Incoming Webhook - Teams | Microsoft Learn
Give the connector a name and customize its logo if you like, then click Create
When you have hit Create a Webhook URL is generated. Copy this to your clipboard for use in Eido then hit Done.
Slack alerts require a Webhook URL to the Slack channel that will be used to receive Eido alerts and details on Webhook authorization headers if required
To enable webhooks for a specific channel in Slack follow these steps on the Slack website Sending messages using incoming webhooks | Slack
Webhooks
If we have no native integration for the tool you are interested in connecting to, most modern tools will accept an inbound Webhook. Additional properties that require configuration are the Webhook URL and Authorization headers if the destination requires them.
Eido’s ServiceNow integration will insert Incidents directly into the Incident table. It requires:
- ServiceNow URL – this should follow the syntax of “https://<base url>/api/now/table/incident” for example “https://eido-servicenow.com/api/now/table/incident”. Note that without “/api/now/table/incident” our integration will not work
- An account of basic type with at least the ITIL and Web_admin roles (to allow Eido to connect to ServiceNow’s APIs and access the Incident table and CMDB to link Incidents to Cis)
- Account password
- Short Description – the Incident’s title in ServiceNow
- Description Template – the information that will be used for the body of the Incident
- Assignment Group – the Assignment group that will be set on Incidents raised. Must match a valid one within ServiceNow
There are also optional parameters as follows:
- Use Device Primary User as Caller – this option sets the Incident’s caller field to the devices primary user name. Doing this will mean that the devices end user will get any email notifications about the Incidents raised via Eido. If set a “Fallback Caller email” is also required incase the devices primary user cannot be found in ServiceNow, the email address provided must be linked to a ServiceNow account for this to work
- Assign to agent email – if you want Incidents assigned to a specific agent within ServiceNow se their email address here
- Impact– must match a valid Impact within your ServiceNow instance
- Urgency – must match a valid Urgency within your ServiceNow instance
The following parameters can be used within any field of the incident template, they will be replaced programmatically with the correct values by Eido for the Incident being raised. Note that they are case sensitive:
- IssueId – the Eido Issue ID
- IssueSeverity – the Eido Issue severity (red/amber)
- EidoDeviceLink – a link to the device within Eido that is experiencing the issue
- FriendlyIssueName - todo
- IssueName - todo
- IssueType – Whether the issue is a Device or Certificate issue
- IssueStart – the date/time stamp the issue was raised
- IssueEnd– the date/time stamp the issue was closed (if in a closed state, otherwise will be blank
- EidoCustomerName – the Customer that is experiencing the issue (MSP edition only)
- CertificateName – the name of the certificate (certificate type issues only)
- CertExpiryDate - the date/time stamp the certificate was raised (certificate type issues only)
- IssueUrl – link to the issue within Eido
- DeviceName – the name of the device that is experiencing the issue
- PrimaryUserEmail – the primary user of the device that is experiencing the issue’s email address
- DeviceOperatingSystem – the OS on the device experiencing the issue
- DeviceIntuneLastSync – the date/time stamp the device synced with Intune last
- DeviceSerialNumber – the serial number of the device experiencing the issue