An integration is a service you already have, connected once on the team and available to every project it owns. Find them under your team's settings; adding, changing or removing one takes the Admin role or above.
What can be connected
| For | Services | What it does |
|---|---|---|
| Somewhere to send logs | Datadog, New Relic, Logz.io, Axiom, Grafana Loki, Splunk, an OpenTelemetry endpoint, or a plain syslog host and port for anything not on that list | Logs are shipped from the machine, alongside the copy the platform keeps. See Logs. |
| Storage you control | S3-compatible object storage, SFTP, or an rclone remote | Your backups are copied there. One S3-compatible connection can also be where logs are archived. SFTP and rclone take backups only. |
| Somewhere the platform can tell you something | Slack, Telegram, Discord, PagerDuty, or a webhook for anything else | The channels Notifications uses. |
Email needs no integration: choose it as a channel when setting up a notification.
Log forwarding and backups to your own storage are not offered on the entry line of machines; a larger machine adds both.
Credentials
A key you paste is stored encrypted and never shown again. To replace one, enter the new value.
Changing where a key is sent asks for the key again: the endpoint of a log service, or a webhook's URL or header name. A stored key is only ever sent to the address it was entered for.
A log service's endpoint, and a syslog host, is an address on the public
internet: the machines your sites run on send to it, and an address on a
machine or a private network is refused when you save it. An OpenTelemetry
endpoint's header is a plain header name, such as Authorization or
dd-api-key.
Credentials never travel in a task: a machine is handed what it needs when it asks, over its own authenticated channel.
Removing one
An integration in use cannot be removed. The console lists what is using it: the projects that ship logs there, the backup destinations that write there and the notifications that post there. Point those somewhere else first.
Nothing already written is deleted: a backup already copied to your bucket stays there.
Next
- Logs — what is shipped, and what the platform keeps regardless
- Backups — pointing a copy at storage you control
- Notifications — the channels these feed
Thank you. Good to know it helped.
Thanks — tell us what was missing. Open a ticket from Support in the console, and we answer on the ticket. Open the console