// DOCUMENT_ROOT / GETTING_STARTED

Getting Started with GRZU

This manual provides a quick-start roadmap to deploying active, real-time uptime checks across global cloud nodes. Hook up latency diagnostics and output instant fail details to your developer slack tunnels.

Install the Daemon CLI

GRZU includes a lightweight, ultra-fast worker monitoring daemon CLI used to create, compile, and configure test definitions locally or trigger them on our remote network nodes. Run our standard installer shell script:

TERMINAL SH_INIT

$ curl -s https://get.grzu.dev | sh

Export Your Authentication Secrets

To authenticate with the tracking engine, set your project secret token as an environment variable in your terminal instance or local production environment files:

EXPORTS .ENV

export GRZU_PROJECT_ID="proj_acme_832"

export GRZU_API_KEY="key_live_7231aa492b"

Deploy Your First API Active Monitor

Execute a ping monitor definition creation. Set headers, target domains, check intervals, and declare custom status verification thresholds:

GRZU MONITORS ENGINE

grzu monitors:create \

--name "Users API check" \

--url "https://api.acme.com/v1/users" \

--assert-status 200 \

--interval "10s"

Inspect Telemetry Logs and Active Statuses

Verify client telemetry flows. Our workers deploy your check across chosen region worker environments instantly, reporting status variables and ping latency outputs:

TERMINAL PEER_LOGS

[18:31:00] DEPLOYED "Users API check" across 3 global regions.

[18:31:10] US_EAST_1 >> HTTP 200 OK (latency: 14ms)

[18:31:10] EU_WEST_1 >> HTTP 200 OK (latency: 22ms)

[18:31:10] AP_NORTHEAST_1 >> HTTP 200 OK (latency: 38ms)

Need custom assertion examples?

Dive into our custom headers parameters and assertions templates to handle complex authentication cookies or nested body value schema pings.

Configure JSON Assertions