Skip to Content
Logvera
API Keys and CLI

Analyse Logs on a Schedule

Send a log every night from any server or pipeline and get the summary in Slack, a webhook or your inbox.

1. Create a Key

Add where summaries should go: Slack, a webhook or email.

2. Run the CLI

One Python file with no dependencies uploads any log.

3. Get the Summary

Health, incidents and a private report link, every night.

Create an API Key

Keys last 90 days and allow 50 uploads a day. Destinations are optional and stored encrypted.

Shown in notifications, e.g. “Production API Nightly”.

Create an incoming webhook in Slack and paste its URL.

We POST a JSON summary. Must be a public https:// address.

When to Send a Message
Alert Rules
Health falls belowout of 100
Health drops bypoints or more since the previous run
Error rate rises by% or more since the previous run
or more unusual periods are found
New security findings appear since the previous run

Runs are compared with the previous run of the same log. Dates and numbers in file names are ignored, so app-2026-09-25.log and app-2026-09-26.log count as the same log.

Your Keys

Saved in this browser so you can manage them. Anyone with a key can upload logs under its daily limit.

No Keys Yet

Create a key above to start sending logs from servers, cron jobs or CI pipelines.

Schedule It

Download the command-line tool, then run it from cron, CI or any script.

Download CLI
Terminal
curl -fsSL https://api-logvera.taaranjain.com/api/v1/cli -o logvera.py
export LOGVERA_API_KEY=lv_your_key_here

python3 logvera.py analyze /var/log/nginx/access.log --wait
python3 logvera.py analyze /var/log/nginx/access.log.*.gz --wait
python3 logvera.py analyze logs-bundle.tar.gz --wait --fail-on-alert
python3 logvera.py analyze app.log --tail 200000 --wait --fail-under 70
python3 logvera.py whoami

Needs Python 3.8 or newer and nothing else. Logs are gzipped before upload. Exit code 3 means health fell below --fail-under; 4 means an alert rule was triggered.