Source Name #

For example, YourApp would be good for all logs from your app. YourApp.bots would be a good place to keep all bot logs. Route logs with LQL rules using rules.

Update name

Alert Frequency #

How often do you want to receive alerts?

Update alert frequency

Email Alerts #

Send emails when this source gets new events. Add email addresses below. Sometimes sources can get a lot of events quickly. At most you will get one email per minute.

Comma separated list of emails please.

Send email alerts to the account owner (default@logflare.app)

Select some team members to alert
Reset email preferences to clear this list.

Update email preferences

Reset

SMS Alerts #

Get text message alerts when a source gets new events. Sometimes sources can get a lot of events quickly. At most you will get one text message per minute.

Send SMS alerts to the account owner (add a phone number)

Select some team members to alert (team members without phone numbers are not listed) Reset SMS preferences to clear this list.

Update SMS preferences

Reset

Slack Alerts #

Get Logflare notifications in your Slack channels! Separate from signing in with Slack. You can send alerts to any Slack channel from any Logflare source.

Schema Change Alerts #

We automatically update your source schema based on the incoming metadata payload. Get an email when the source schema is updated.

Send schema change alerts to the account owner (default@logflare.app)

Select some team members to alert
Reset preferences to clear this list.

Update schema change notifications

Reset

Webhook Alerts #

We recommend setting up RequestBin to see what our payloads look like. Once a webhook url is saved here you can send a test request to it.

Payloads are automagically compatible with Discord webhook urls!

This endpoint should accept POST requests with a JSON body.

Update webhook preferences

Custom Event Message #

Comma separated list of metadata keys to customize the log event message. Use message to target the default log event message. Use JSONpath queries to target more complex nested data structures. The root ($.) is implied here.

Key values will be concatenated with a pipe ( | ).

Update keys

Public Access #

Public paths let you share your logs with other people without having to give them a login. Generate a public token and this source will be accessible by anyone with this url. Regenerate a public path if needed.

Generate path

Schema Lock #

Lock this source schema to keep it from updating automatically. Any new fields encountered during ingest will be ignored.

Lock schema

Schema Validation #

Disable schema validation on ingest. Use this for high volume sources. Typically schema validation should be disabled for sources seeing >1,000 log events per second.

Disable schema validation

Drop Log Events #

Use an LQL statement to drop log events on ingest.

Currently in beta.

Update LQL

Backend TTL #

Set how long to keep data in your backend.

Days to keep data.

Update backend settings

Suggested Search Keys #

Set suggested search keys for this source, to encourage usage of certain filtering keys when performing searches across large sources. If a declared key is missing, users will be prompted to include the key when a search is made.

Comma-separated. For example: status,metadata.level

Save

Multi Backends #

Toggle v2 pipeline for this source

Save