Configure Notifications
Check push status, copy the server's identifier, and finish notification routing in Zabbix.
Start inside the app
Check push readiness in two places:
- Settings, where you can check iOS authorization and alert-gateway status
- the server edit flow, where the app shows the per-server registration state and exposes the
UNIQUE_UID
Push notifications are optional. Monitoring data still comes directly from the Zabbix server. Check the app’s authorization and registration status before configuring delivery in Zabbix.
In the app
Settings push status
In Settings, Push Notifications shows iOS authorization and Alert Gateway status. Check both before setting up Zabbix delivery.
Use the server-specific UNIQUE_UID
Each configured server has its own UNIQUE_UID. Open the edit screen for the server whose alerts you want, then copy its identifier for the Zabbix setup.
In the app
Server-specific push identity
Edit Current Server shows push status and the UNIQUE_UID for that server. Copy this identifier for the matching Zabbix user media entry.
Finish the routing in Zabbix
In Zabbix, an administrator completes delivery routing:
- import the shared TriggerDeck media type
- create a user media entry with the copied
UNIQUE_UID - attach that media type to the relevant action path
In the app
Zabbix media type import
Import the TriggerDeck YAML media type in Zabbix. This creates the media type used for notification routing.
In the app
Zabbix user media entry with UNIQUE_UID
Select the TriggerDeck media type in Zabbix user media and put the matching UNIQUE_UID in Send to. Attach the media type to the relevant action path to route alerts.
What push can access
- Browsing data still comes directly from the iPhone to Zabbix.
- The alert-gateway is only for push routing.
- Reinstalling the app or changing registrations can require updating the
UNIQUE_UIDin Zabbix.