boltZharp Docs
terminalLogs

Log Streaming Setup

Before you can attach monitors to your logs, you need to begin streaming data to the Zharp Technical Ingestion Layer.

Zharp provides two primary ways to ingest logs: a highly-optimized REST API for serverless and application-level streaming, and a lightweight local agent for infrastructure-wide log tailing.

send

Option 1: Direct Stream

Best for webhooks, serverless functions, or application-level loggers. We support REST API ingestion via the X-API-KEY header.

https://api.zharp.io/api/v1/logs/ingest

Ensure you include the X-API-KEY header with a valid workspace token. You can manage these in Settings > Developer > API Keys.

terminal

Option 2: Zharp Agent

Recommended for Linux and Windows servers where you need to tail multiple local log files efficiently.

1

Download & Install

Get the binary from our Releases page and install it on your host.

2

Configure zharp.yaml

Define your services and log paths. Replace YOUR_API_TOKEN with a token from your dashboard.

# Zharp Agent Configuration
# https://docs.zharp.io/agent

api_key: "YOUR_API_TOKEN" # Manage tokens in Developer Settings

logs:
  - service: "my-service"
    path: "/var/log/*.log"
    interval: 10s
3

Activate

Restart the agent to begin streaming logs.

sudo systemctl restart zharp-agent

Attaching Monitors

Once your logs are streaming, you can go to the Monitors page and create a Log Monitor. By selecting the corresponding service names (e.g., my-service), Zharp will begin scanning your incoming streams for the patterns you specify.

Start Monitoring Logs

Once your data is flowing, set up your first log alert monitor to stay informed.

Create Log Monitorarrow_forward
Previous
System Architecture
Next
Quick Start Guide