Skip to main content

Logs View

Search and explore structured log entries collected from your Meteor application.

Overview​

The Logs view is a centralized log viewer accessible from the sidebar navigation. It displays structured log entries captured by the SkySignal agent, with filtering by level, source, time range, and free-text search. Logs are loaded in pages of 50 entries at a time with a "Load More" button for pagination.

Viewing Logs​

Navigate to Logs in the sidebar. If you have multiple sites, select the target site from the dropdown in the page header. The default site is your most recently created one.

Logs are displayed in a vertical list with each entry showing:

  • Timestamp - Full date/time with millisecond precision (hidden on small screens, visible on expand)
  • Level - Color-coded chip (DEBUG, INFO, WARN, ERROR, FATAL)
  • Source - Where the log originated (hidden on small screens)
  • Message - The log message text, truncated to one line

Click any log entry to expand it and see the full details.

Level Summary Bar​

At the top of the log list, a row of clickable level chips shows the count of entries for each level in the current time range:

  • DEBUG - Gray
  • INFO - Blue
  • WARN - Amber
  • ERROR - Red
  • FATAL - Dark red

Click a level chip to filter the list to only that level. Click it again (or click "Clear") to remove the filter.

Filtering​

The filter bar provides several ways to narrow down logs:

FilterDescription
SearchFree-text search across log messages. Debounced at 300ms so results update as you type.
LevelMulti-select dropdown to filter by one or more log levels (debug, info, warn, error, fatal).
Time RangeLast 1 Hour, Last 6 Hours, Last 24 Hours (default), or Last 7 Days.
SourceFilter by log source (e.g. console, meteor-log, api, or a custom source name).
MethodFilter by Meteor method name to see logs generated during a specific method execution.

Click "Clear" to reset all filters back to defaults.

Log Entry Details​

Expand a log entry by clicking on it. The expanded view shows:

Trace Correlation​

Logs captured during Meteor Method execution are automatically linked to the method trace:

  • Method Name - The Meteor method that was executing when the log was emitted
  • Trace ID - Clickable link that navigates to the trace detail view, so you can see the full method execution context alongside the log
  • Error ID - If the log is associated with an error, a clickable link to the error detail view

Additional Fields​

  • Host - Which server instance produced the log (useful for multi-server deployments)
  • Source - The logging source (e.g. console, meteor-log, api)

Metadata​

If the log entry includes attached metadata (arbitrary JSON), it renders in a dark-themed code block with syntax highlighting. This is where you will find any structured data your application attached to the log call, such as user IDs, request parameters, or diagnostic context.

Configuration​

Log collection is configured in the SkySignal agent settings. The agent captures output from console.log, console.warn, console.error, and any logs emitted through Meteor's logging utilities.

For details on configuring which logs are captured, log level thresholds, and custom log sources, see the Agent Log Configuration guide.

Tips​

Finding Logs for a Specific Method​

Use the Method filter field to enter a method name (e.g. users.updateProfile). This shows only log entries emitted during executions of that method, which is useful for debugging method-specific issues without wading through unrelated output.

Correlating Logs with Errors​

When investigating an error:

  1. Go to the Errors View and find the error
  2. Note the method name and approximate timestamp
  3. Come back to Logs, set the time range, and filter by that method name
  4. Expand log entries around the error timestamp to see what led up to the failure

When a log entry has a Trace ID, clicking it takes you to the full trace waterfall for that method execution. This gives you the complete picture: the log message in context with the method's database queries, external calls, and timing breakdown.

Next Steps​