SafeCall Docs

Appearance

Quickstart ​

This quickstart assumes:

  • machine A runs the main SafeCall server (serves /lld/*)
  • machine B runs SafeCall bridge mode
  • machine C runs Zabbix

1) Validate Main Server LLD Endpoints (machine A) ​

bash
curl -fsS "http://<main-server>:8088/lld/gateways" | jq .
curl -fsS "http://<main-server>:8088/lld/beacons" | jq .

Both endpoints must return JSON arrays with LLD macros ({#MAC}, {#NAME}, etc.).

2) Configure Bridge Runtime (machine B) ​

Set bridge configuration in config/main.config.json (legacy fallback: main.config.json):

  • server_features includes bridge
  • server_bridge_server_url points to machine A
  • server_bridge_endpoint_gateway and server_bridge_endpoint_beacon point to lld/gateways and lld/beacons
  • server_bridge_zabbix_host and server_bridge_zabbix_port point to machine C trapper (10051)

3) Run SafeCall-Side Diagnostics (machine B) ​

bash
./util.sh integrations zabbix doctor

This command verifies:

  • bridge feature/config presence
  • LLD endpoint reachability and payload format
  • TCP reachability to Zabbix trapper

4) Provision Zabbix Objects (machine C or API-access host) ​

bash
./util.sh integrations zabbix setup --url "http://<zabbix>/api_jsonrpc.php" --user Admin

Use --dry-run first if desired.

If your Zabbix server host name is not the default (Zabbix server), pass:

bash
./util.sh integrations zabbix setup --url "http://<zabbix>/api_jsonrpc.php" --user Admin --zabbix-host "<exact host name>"

5) Verify Zabbix Read-Only State ​

bash
./util.sh integrations zabbix verify --url "http://<zabbix>/api_jsonrpc.php" --user Admin

This performs API-only checks and does not modify Zabbix. If host matching fails, the command prints host candidates to help you choose --zabbix-host.

6) Incident Debug Mode ​

When debugging production issues, enable:

  • server_bridge_debug_enabled: true
  • optional sampling/interval knobs:
    • server_bridge_debug_sample_rate
    • server_bridge_debug_snapshot_interval

Then restart SafeCall and inspect bridge logs for stage counters and send failures.