iLert Documentation
WebsiteAPI ReferenceLoginFree Trial
Search…
Getting Started
Core concepts
iLert domains, ips, emails & phone numbers
FAQ
On-call management & Escalations
Escalation policies
On-call schedules
Incident comms
Getting started
Services
Incidents
Status pages
User Administration
User roles and permissions
Team-based organisation
Single sign on
🔐
Two-factor authentication / MFA
Call Routing
Getting started with call routing
Routing calls based on support hours
Voicemail only mode
Managing call routing alerts
Adding webhooks and outbound chat messages
Uploading custom audio responses
Uptime & Heartbeat Monitors
Uptime Monitoring
Heartbeat Monitoring
REST API
iLert REST API
API Version History
Rate Limiting
Client Libraries
Terraform
API Samples
🔥
Developing iLert Apps
🪝
Application Hooks
Integrations
Amazon CloudWatch Integration
Amazon EventBridge Integration
Amazon SNS Integration
Azure Alerts Integration
API Fortress Integration
AppDynamics Integration
AppSignal Integration
AWS Budget Integration
AWS GuardDuty Integration
AWS Lambda Integration
AWS Personal Health Dashboard Integration
Autotask Integration
Auvik Integration
Azure Function Integration
Checkmk Integration
Cisco Webex
Cloudflare Integration
Connectwise Manage Integration
Cortex XSOAR (formerly Demisto) Integration
CrowdStrike Integration
Datadog Integration
Discord Integration
DingTalk Integration
Dynatrace Integration
Email Integration
Email Outbound Integration
FreshService Integration
GitHub Integration
GitLab Integration
Google Cloud Function Integration
Google Cloud Monitoring (formerly Stackdriver) Integration
Grafana Integration
HashiCorp Consul
Humio Integration
IBM Cloud Functions Integration
Icinga Integration
Instana Integration
IXON Cloud Integration
Jira Integration
JumpCloud Integration
Kapacitor Integration
Kentix AlarmManager
Kubernetes Integration
Lightstep Integration
Mattermost Integration
Microsoft Teams Integration
MongoDB Atlas Integration
MXToolBox Integration
N-central Integration
Nagios Integration
New Relic Integration
Oh Dear Integration
PandoraFMS Integration
Pingdom Integration
Prometheus Integration
PRTG Network Monitor Integration
Push Notifications
Raygun Integration
Salesforce Integration
Samsara Integration
Search Guard Integration
Sematext Integration
Sensu Integration
Sentry Integration
Server Density
ServiceNow Integration
SignalFx Integration
Single Sign-On Setup
Slack Integration
SMS Integration
SolarWinds Integration
Splunk Integration
StatusCake Integration
StatusHub Integration
StatusPage Integration
Sumologic Integration
Sysdig Integration
TOPdesk Integration
Terraform Cloud / Terraform Enterprise
UptimeRobot Integration
Webhook Integration
Hyperping Integration
Prisma Cloud Integration
X-Pack Alerting (Elasticsearch Watcher) Integration
Zabbix Integration
Zammad Integration
Zapier Integration
Zendesk Integration
Zoom Integration
Contact us
iLert Release Notes
Android Push Notification Configuration
Powered By GitBook
PRTG Network Monitor Integration
Create alerts in iLert from PRTG notifications.
With PRTG integration, you can easily integrate PRTG with iLert and extend your existing PRTG monitoring with SMS, push and voice notifications as well as on-call schedules from iLert.

In iLert: Create PRTG alert source

  1. 1.
    Go to Alert sources and click on Add a new alert source
  2. 2.
    Enter a name for your alert source (e.g. "PRTG") and select your desired escalation policy.
  3. 3.
    In the Integration Type field, select PRTG Network Monitor and click on Save
  1. 1.
    On the next page, PRTG URL and PRTG Postdata fields will be displayed. You will need those two fields in the PRTG setup.

In PRTG: Create new notification

  1. 1.
    Got to notification settings
  1. 1.
    Add a new notification
  2. 2.
    As notification method select Execute HTTP ACTION
  3. 3.
    Copy the URL and Postdata fields from the iLert alert source. The API key is included in Postdata.
  1. 1.
    Click on Save
  2. 2.
    Next, we will use the newly created iLert notification method in PRTG. To do this, switch to the root group in the device overview and select the "Notifications" tab.
  1. 1.
    Create the following status triggers. Note: We recommend the option "repeat this every 5 minutes" in case your internet connection goes down.

FAQ

Will alerts in iLert be resolved automatically?
Yes, as soon as the condition of a sensor in PRTG is OK again, the associated alert is resolved in iLert.
What if an alert is acknowledged in PRTG, is the associated alert also acknowledged in iLert?
No, in PRTG it is unfortunately not possible to send notifications for acknowledgements.
What if my internet connection is interrupted? Are the events generated in PRTG lost?
No, events will not be lost if you enable the "repeat every x minutes" option in PRTG (see above). In addition, we recommend that you monitor your Internet connection with an external monitoring service (e.g. using iLert's uptime monitoring or heartbeat monitoring). You can send these alerts to iLert.
Can I link PRTG to multiple alert sources in iLert?
Yes, create multiple iLert notifications in PRTG. You can then associate them with objects in the PRTG object hierarchy.
The integration does not work. How do I find the issue?
If you can not find the error, please contact our support at [email protected].
Integrations - Previous
Prometheus Integration
Next - Integrations
Push Notifications
Last modified 10mo ago
Copy link
Edit on GitHub
Outline
In iLert: Create PRTG alert source
In PRTG: Create new notification
FAQ