Documentation

From first signal to operational intelligence.

Implementation guidance for configuring, integrating and operating Pulszo.

Platform overview

Pulszo is a network operations intelligence platform for collecting service telemetry, calculating SLA performance, correlating incidents and analyzing provider risk.

You need an active workspace and an API key with collector permissions to complete this guide.

Quickstart

Connect a collector, register your first target and confirm that telemetry is flowing into the workspace.

1. Install a collector

curl -fsSL https://install.pulszo.com/collector | sh
pulszo-collector configure --workspace YOUR_WORKSPACE_ID

2. Register a target

curl -X POST https://api.pulszo.com/v1/targets \
-H "Authorization: Bearer $PULSZO_API_KEY" \
-d '{"host":"10.20.0.1","protocol":"snmp"}'

Collectors

Collectors run close to the monitored environment and securely forward normalized telemetry. Deploy at least two collectors per critical region for collection resilience.

Monitoring

Pulszo continuously tracks availability, latency, packet loss and interface health across links, devices and services. Configure polling intervals, thresholds and alerting policies per target or group.

SLA policies

SLA policies combine service targets, measurement windows, exclusions and escalation thresholds. Attach a policy to a service or group to begin automated compliance calculations.

AI Network Analyst

The analyst can query your permitted operational context. Every response includes evidence references and a confidence indicator so operators can validate recommendations.

Multi-tenancy

Multi-tenant workspaces isolate data, access and branding per customer or business unit. Delegate scoped roles so each team sees only what it is permitted to.

REST API

The REST API exposes targets, metrics, SLA policies and incidents for automation and integration. Authenticate with scoped API keys; every endpoint is rate-limited.

Webhooks

Subscribe to incident, SLA and threshold events to push real-time updates into ticketing, chat or custom workflows. Webhook payloads are signed so receivers can verify authenticity.

Security model

Use scoped API keys, role-based access, SSO and audit events to enforce least privilege. Never embed collector credentials in scripts or source control.

Request demo