Overview
Faddom can receive events from external monitoring tools via an inbound REST API integration. This allows you to push alerts from systems like Zabbix, Nagios, PRTG, and SolarWinds directly into Faddom, correlating them with your network topology and application maps.
Prerequisites
Firewall open from the source system to Faddom on the port used for the UI (typically 443 or 9443)
An API token from Faddom. Please take a look at our guide on Creating the API Token for API Access if you do not already have one.
How It Works
External monitoring tools send event notifications to Faddom's webhook endpoint. Faddom automatically:
Matches events to servers in your inventory
Creates or closes Operational Events
Associates events with relevant application maps
Provides unified visibility across monitoring platforms
API Endpoint
Endpoint: PUT /v1/event
Base URL: https://<FaddomServerIpAddress>/WebServices/api
Authentication: Bearer token (API access token required)
For specific instructions, you can see our guide on How to Use The Faddom API
Server Matching
Faddom matches incoming events to servers using IP address or hostname. If the server is not found in Faddom's inventory, the server will be created, so you will still be able to see the event.
Setting Up Webhook Integration
Any monitoring tool that can make authenticated REST API calls can push events into Faddom today using the endpoint above. This works for Zabbix, Nagios, PRTG, SolarWinds, or any other system, no prebuilt connector required.
Zabbix also has a prebuilt, guided integration (a native Media Type/Webhook template you import directly into Zabbix), so no custom scripting is needed. Prebuilt integrations for other platforms are in planning; until then, use the generic API above.
For complete API specifications and testing, see the Interactive API Documentation using
<FaddomServerIpAddress>/WebServices/api/swagger-ui/index.html#/
Note: The Swagger UI is hosted on your own Faddom server, so the URL will be specific to your environment. Replace <FaddomServerIpAddress> with your Faddom server's IP address or hostname.
Event Lifecycle
Opening Events: When your monitoring tool detects an issue, it sends an event with status "OPEN". Faddom creates an Operational Event for the affected server.
Closing Events: When the issue is resolved, send an event with status "CLOSE" using the same External Event ID. Faddom marks the event as resolved.
Viewing the Events in Faddom
There are two places you can see the events pushed to Faddom. You can view them in our Notifications and Operational Events screen or in the Events section of the Server Properties.
When looking at the Operational Events & Notifications screen, it will show the source, eg, Zabbix
From the server properties, you will see it in the pattern defined in your webhook
If you are looking at an Application Map, operational events including external events will appear as red indicators on the affected servers.
If you have any questions or need help, please contact support@faddom.com.