Send logs
Choose how your application sends logs to dlogify.
Pick the method that fits your stack. They all end up in the same place, and you can mix them in one project.
| Method | Use it when | Guide |
|---|---|---|
| Node.js SDK | Your service runs on Node.js 20.19 or later. Works without code changes. | Node.js |
| Python SDK | Your service runs on Python 3.10 or later. Two lines of code. | Python |
logify run | Any process in any language: wrap the start command and its output is sent. Ships with the Node.js and Python packages. | logify run |
| OpenTelemetry (OTLP) | You already use OpenTelemetry, or a language without a dlogify SDK. | OpenTelemetry |
| REST | Scripts, cron jobs and simple integrations at moderate volume. | REST |
| OpenTelemetry Collector presets | Docker or Kubernetes: collect the logs of labelled containers without changing images or code. | Collector |
Authentication
Every method authenticates with a project API key, sent as a bearer token:
Authorization: Bearer lgf_live_<key_id>_<secret>Create one under API keys in your project (see Projects and API keys). The key decides which project the logs belong to.
What happens next
dlogify redacts personal data, groups ERROR and WARN events into error groups, and counts INFO events into summaries. See What is sent and Limits.