Logs

Overview

The Logs page aggregates output from all running containers into a single, searchable log viewer. Instead of connecting to each container individually, you can view, filter, and search logs from every service in one place.

Container Logs

Navigate to Logs by clicking Logs in the sidebar.

Log Viewer

The log viewer displays entries in reverse chronological order (newest first). Each log entry shows:

Logs are colour-coded by level for quick visual scanning.

Log Levels

Organism recognises standard log levels, each with a distinct colour:

Interpreting Log Levels

• INFO is the most common level — it shows healthy application activity like HTTP requests, database queries, and background tasks
• WARN entries are worth monitoring but usually don't require immediate action
• ERROR entries indicate something went wrong — check these when an application is misbehaving
• DEBUG entries are typically only useful when actively troubleshooting a specific issue

Filtering

By Container

Use the container dropdown to view logs from a specific container only. This is useful when troubleshooting a single service within a multi-container application.

By Log Level

Filter by severity to focus on what matters:

• Show errors only when investigating a failure
• Show warnings and above for a health overview
• Show all levels when debugging a specific issue

By Time Range

Narrow the log view to a specific time period:

• Last 15 minutes — recent activity
• Last hour — short-term troubleshooting
• Last 6 hours — medium-term analysis
• Last 24 hours — daily overview
• Custom range — specify exact start and end times

Real-Time Streaming

When viewing the most recent logs, the viewer automatically streams new entries as they arrive. New log lines appear at the top of the list with a subtle highlight animation.

The stream pauses automatically when you scroll up to read older entries, so new logs don't push the content you're reading out of view. Scroll back to the top to resume streaming.

Search

The search bar lets you find specific text across all log entries:

• Type a search term and press Enter to filter
• Matching entries are highlighted
• Search works across container names, log messages, and timestamps
• Clear the search to return to the full log view

Common Search Patterns

Troubleshooting with Logs

Application Won't Start

1. Filter logs to the application's containers
2. Set level to ERROR
3. Look for startup failures — common causes:
   • Port already in use
   • Database connection refused
   • Missing environment variable

Slow Performance

1. Filter to the relevant time period
2. Look for WARN entries about timeouts or slow queries
3. Check Monitoring for resource constraints

Health Check Failures

1. Search for health or unhealthy
2. Check if the application is actually responding on its configured port
3. Look for errors in the application container's logs around the time of the health check failure

Related Documentation

• Monitoring — System resource metrics
• Installed Apps — Restart or stop problem containers
• Settings — Configure health check intervals
• Dashboard — System overview