Logs Are Talking.
You're Not Listening.
Developers ignore 99% of their logs. LogTrunk makes them useful.
> _
10,000 lines per minute.
Your console can't keep up.
That error you need?
It scrolled past 47 seconds ago.
Clear the console.
Lose the context.
Start over.
What if logs worked for you?
Every source. One place.
TCP, UDP, HTTP, or file tailing. Configure multiple sources per tab and see all your logs in a unified view.
TCP
Port:
HTTP
Port:
FILE
Parsed Fields
level 4 2
info 1234
error 56
warn 89
debug 2341
status 3
200 890
404 23
500 12
service 3
api 500
worker 300
scheduler 100
Find anything. Instantly.
Filter by any parsed field. Include or exclude values with a click. Combine with regex queries for precision.
Pin it. Mark it. Keep it.
Pin important logs to preserve them. Add markers to separate debugging sessions. Never lose context again.
Deploy v2.1.0 started 14:32:10.000
latency: 45ms
pool: 3/10
Parser Pipeline
- 1 Envelopestops
- 2 JSONstops
- 3 Grokstops
%{TIMESTAMP_ISO8601:ts} %{LOGLEVEL:level} %{GREEDYDATA:msg}
Raw Input
{"log":"2024-01-15T10:32:08Z INFO Starting...","stream":"stdout"}Parsed Fields
timestamp: 10:32:08Zlevel: INFOmessage: Starting...stream: stdout
Any format. Auto-detected.
JSON, Grok patterns, Logfmt, or regex. Chain parsers in a pipeline. Let AI suggest the right pattern.
Debug with AI.
Connect via MCP protocol. Let AI query, analyze, and mark your logs. Turn debugging into a conversation.
get_logs query_logs add_marker get_markers Connected LogTrunk MCP v0.1.0
Example Prompts
"Why is the API returning 500 errors?" Analyzing error patterns and stack traces...
"Show me all requests from user_id=42" Filtering logs by field value...
"Add a marker for when I started debugging" Creating visual checkpoint...
Appearance
Light Theme
Dark Theme
Make it yours.
Light, dark, or system. Choose from built-in themes or create your own with custom CSS.
Stop scrolling.
Start debugging.
Start Free Trial Free trial available. Upgrade anytime for advanced features.