Dashboard settings

All settings are per-project and accessible from the sidebar under Settings.

Projects

Manage your projects and their API keys.

Project settings

• Name: display name shown in the sidebar and alerts

API keys

Each project can have multiple API keys. There are two types:

• Public keys (vpk_ prefix): used by the tracker in browser-side code. Safe to expose publicly because a public key can only send logs (cannot read, modify, or delete data). The worst-case misuse is someone spamming ingestor with bogus logs, but rate limits and circuit breakers prevent abuse.
• Secret keys (vsk_ prefix): used by the CLI and server-side integrations. Never expose these in client-side code.

For each key you can configure:

• Allowed origins: a list of domains that can send events with this key (e.g., https://example.com). Set to * to allow all origins.
• Revocation: revoke a key to immediately block all traffic using it. This cannot be undone.

When you create a new public key, the dashboard shows a ready-to-paste integration snippet with the CDN URL and ingestor endpoint.

Monitoring

Configure uptime monitoring and alert notifications for the selected project.

Uptime monitoring

• Enable/disable toggle: turn health checks on or off
• Monitor URL: the HTTP or HTTPS endpoint to check (e.g., https://example.com/health)

The default check interval is 5 minutes. A custom interval can be configured per project in the database.

Error spike detection

Vantmetry continuously monitors the error rate from your application. If errors suddenly spike above normal levels, you get alerted immediately.

How it works from your perspective:

• A spike is triggered when error volume exceeds 50 errors per minute
• You receive an alert via your configured webhook (Discord, Slack, or ntfy) the moment a spike is detected
• The spike is marked as "Resolved" automatically after 2 minutes without new errors
• You get another alert when the spike resolves, so you know the situation is back to normal

Example scenario:

Your app is running smoothly with ~5 errors/minute. A bug is deployed and suddenly you get 100 errors/minute. Within seconds, you receive a spike alert. You investigate, revert the deployment, and errors drop back to normal. 2 minutes later, you get a "resolved" notification.

Note: To avoid alert fatigue, if the same spike pattern repeats within 10 minutes, you won't get duplicate alerts. The system assumes you're already aware and working on it.

Notifications

Choose where to send alerts when the monitor status changes or an error spike is detected:

Provider	Webhook URL format
Discord	https://discord.com/api/webhooks/...
Slack	https://hooks.slack.com/services/...
ntfy	https://ntfy.sh/your-topic
None	Monitoring runs but no notifications are sent

Webhook URLs are validated for HTTPS and checked against private IP ranges (SSRF protection) before any request is made.

Usage

View storage consumption for the selected project.