Log Destinations
Log Destinations streams your account's logs to your own logging provider.
Log Destinations are available on the Teams and Business plans. Owners and Admins can add and change destinations; Auditors can view them.
Where to find it
Open Manage Account > Log Destinations.
What you see
The destinations list
Each destination shows its Name, Provider, Streams, Status and Last delivery. Last delivery shows the time of the last successful delivery, or the last error.
| Status | Meaning |
|---|---|
| active | Delivering. |
| failing | The last delivery failed. Last delivery shows the provider's error. |
| disabled | Turned off. Nothing is sent. |
Each row has Send test event, Enable or Disable, and a delete button. Other roles see the list without these controls. Refresh reloads the list.
Send test event sends one event to the provider. When the provider accepts it, a failing destination returns to active. When it refuses it, the row shows the provider's answer and an active destination reads failing.
Providers
| Provider | What you enter |
|---|---|
| Datadog | Datadog site (the site your Datadog account uses, such as us1 or eu1) and an API key. Find the key in Datadog under Organization Settings > API Keys. |
| Grafana Loki | Loki URL, User ID and an Access policy token. Find them in Grafana Cloud under Loki > Details. |
| Elasticsearch | Elasticsearch URL (an https address), Data stream (lower case, no spaces) and an API key (the encoded value Elastic shows when you create the key). |
| Splunk | Splunk URL, an HEC token, and optionally an Index and a Sourcetype. Wait for indexer acknowledgement confirms that events reached an index, with about a minute of delay. |
Grafana Loki, Elasticsearch and Splunk also take an optional Certificate authority: paste the PEM certificate when your endpoint uses a private certificate authority, and leave it blank for a public one.
Streams
Choose which logs a destination receives:
| Stream | What it carries |
|---|---|
| Data pipeline runs | One record per run, with its status and timings. |
| Node execution | One record per node in each run. |
| Connector errors | Errors returned by connected systems. |
| Platform errors | Errors raised by DataLug while running your work. |
| Audit trail | The account's audit log entries. |
| Milo usage | Milo requests and their AI usage. |
Minimum severity filters out records below a level: debug, info, warn, error or fatal.
Common tasks
Add a destination
- Select New destination.
- Enter a Name and choose the Provider.
- Fill in the provider's fields.
- Tick the streams to send and set the Minimum severity.
- Select Test and save. DataLug sends a test event with the credential and saves the destination only when the provider accepts it.
Changing the provider clears the credential you entered. Stored secrets are never sent back to the browser.
Pause a destination
Select Disable on its row. Nothing is sent until you select Enable.
Troubleshooting
- The test event fails. Check the URL and the credential against the provider. The message in the form is the provider's answer, and nothing is saved.
- A destination reads failing. Open the provider and check that the credential is still valid. Send a test event to confirm the fix.
- Nothing arrives for a stream. Check that the stream is ticked and that the Minimum severity is not above the level of the records you expect.