Connection Guide 3 min read

Connect Your First Server

Add your first server and confirm the current browsing and triage workflow works in the TriggerDeck iPhone app for Zabbix.

Add a server connection

TriggerDeck is designed as a direct iPhone client for Zabbix environments. Start by adding a server connection that the mobile client can reach over HTTPS. Supported Zabbix API versions in the app are 6.0 LTS, 7.0 LTS, and 7.4. Additional compatible versions are 6.2, 6.4, and 7.2; support for these versions is restricted and untested. Patch versions follow the status of their minor line.

  1. Open TriggerDeck on your iPhone.
  2. On a fresh install, the add-server flow opens automatically. If you already dismissed it, open More and tap Add Server.
  3. Enter:
    • Display name
    • Zabbix URL
    • API token
  4. Tap Test Server to verify the connection. A result row will appear confirming the detected Zabbix version (green), a compatible or unsupported version (orange), or a connection failure (red).
  5. Tap Save Server once the test succeeds.

Verify direct data reads

After the connection succeeds, open the main monitoring flows and verify that live data is loading for the selected server.

Use this quick validation path:

  1. Open Problems and switch between Active, Recent, and History.
  2. Confirm the list refreshes and that the selected server shows the expected problem set.
  3. Swipe a problem row or open the actions flow and verify that in-list problem actions are available.
  4. Open any problem and confirm Problem Details shows the refreshed summary, latest data section, and chart actions for numeric rows.
  5. Open Hosts and confirm host browsing works for the same server context.
  6. Open Items and confirm host-scoped latest values, filters, and search work for the same server.
  7. Open Dashboards and confirm the server exposes the expected dashboard list. Rotate to landscape if the reader prompts for it.
  8. Adjust sorting, grouping, filters, or selected dashboard, leave the screen, and verify the chosen organisation is remembered for that server.

TriggerDeck reads data directly from your Zabbix API. The alert-gateway is not required for browsing problems, hosts, items, dashboards, latest values, or charts.

Confirm the server context

If you connect more than one server:

  • make sure each server entry has a clear display name
  • switch between servers before checking live data
  • confirm that the counts and details you see match the selected server

TriggerDeck keeps each configured server separate so you always know which environment you are viewing.

Remember that filters, sorting, grouping, and dashboard selection are part of the per-server working state. If something looks unexpected, confirm you are checking the right server before treating it as a data issue.

Security model notes

  • API tokens are stored in iOS Keychain.
  • TriggerDeck does not send Zabbix tokens to the optional push service.
  • Use TLS/HTTPS endpoints.
  • Prefer API tokens scoped for the exact monitoring data the operator needs to read.