What you'll need
- SigNoz Cloud or a self-hosted SigNoz instance reachable from the Parumox connector service
- An admin user (only Admins can create API keys; regular members must ask one)
- The base URL of your instance, no trailing slash
Set it up
Sign in as an admin
API key creation requires the Admin role. If you don't have it, ask your org admin to follow these steps and share the resulting key with you securely.
Create the API key
SigNoz UI → Settings → API Keys → New API Key. Name it parumox-connector. Pick a role with read access to logs and metrics. Copy the generated key — SigNoz only shows it once.
Identify your base URL
For SigNoz Cloud this looks like https://your-org.signoz.cloud. For self-hosted, it's the root URL of your query-service (e.g. https://signoz.example.com). The connector strips a trailing /api if you accidentally include one — but no other trailing path.
Permissions required
The key needs read access to the log streams and metric series you want investigated. Health check hits GET /api/v1/version. Log search hits POST /api/v4/query_range with ClickHouse SQL against signoz_logs.distributed_logs_v2. PromQL metric queries use the same key.
Paste into Parumox
Portal → Connectors → Add Connector → choose SigNoz and fill in:
- Base URL — e.g.
https://your-org.signoz.cloud(no trailing slash) - API Key — from step 2
Save. The connector authenticates with the SIGNOZ-API-KEY request header on every call.