Central log management
Find the message behind the incident
Search application and system logs in one workspace. Filter messages, follow incoming entries and investigate problems alongside your monitoring.
Free to use · view quotasSource: Example API
Severity: warning and error · Last 15 minutes
Request took longer than expected
Upstream connection failed
Credential: [REDACTED]
Alert: at least five matching messages in five minutes
What you can monitor
From a message to a useful answer
Keep sources separate, narrow down a problem and reuse the searches that help your team. Connecting a source never enables collection on its own.
Connect the sources you choose
Search, compare and follow live
Turn matching logs into alerts
Understand your data
Choose what you send and how long it stays
Sources retain logs for seven days by default; choose one to 30 days. Shortening requires confirmation. Masking applies before storage, but review your data: sensitive values may remain. Logs use a separate daily quota.
Source: Example API
Severity: warning and error · Last 15 minutes
Request took longer than expected
Upstream connection failed
Credential: [REDACTED]
Alert: at least five matching messages in five minutes
Your first steps
Your first steps
Connect your source in three steps.
- 01
Create a source
Open Logs in your workspace, select an integration and create a dedicated source key. Keep this key private.
- 02
Review and enable collection
Configure the sender, approve local access if needed and check masking. Enable the source and send a first message.
- 03
Save a useful search
Find your first indexed message, save the filters and explicitly enable any alert rule you need. Indexing delays remain visible.
Good to know
Frequently asked questions
Answers and setup guides.
How much log data can I send?
Do logs need a monitor?
Your next step
Start with one source
Connect a source you control, verify its first message and build a focused search. The integration guide includes working examples.