Swavan Studio / Documentation

From sources to dashboards.

Collect logs and metrics, find the records you need, and turn useful views into a dashboard.

GUIDE / HEALTHSources → Query → Dashboard

Before you start

Select your Studio profile and save the connections you want to monitor. Health data sources are selected from those connections; the source picker supports SSH, Docker, Kubernetes, databases, VNC, and RDP. The records available depend on the source and its activity.

1. Add logs and metrics sources

  1. Open Health and choose Data sources from the toolbar or overflow menu.
  2. Turn on Telemetry collection. When it is off, saved sources remain configured but new logs and metrics are not gathered.
  3. Under Connections, select each connection you want to collect from.
  4. Choose Logs, Metrics, or both for each selected connection.
  5. For Docker and Kubernetes sources, choose the relevant scopes: containers, pods, events, and others.
  6. Click Save data sources. In Saved data sources, check that the source is enabled.

Use the saved source’s edit control to change its collection choices. Its enable switch lets you pause that source without removing its configuration.

Control retention

In the same dialog, set Max database size (MB) and Max record age (hours), then choose Save retention. Retention has a separate save button from the source configuration.

2. Query logs or metrics

  1. Open Logs or Metrics from Health.
  2. Choose a time range: Last 15 minutes, Last hour, Last 24 hours, Last 7 days, or All time.
  3. Enter text in Search logs or Search metrics. Leave it empty to see all records within that range.
  4. Press Enter or click Run query.
  5. Open View options to choose Table view or Time series view. Use Group by Data Source to separate sources in the table view.
ViewSearch matchesExample
LogsMessage text or connection ID, without case sensitivitySearch timeout over the last hour to find matching log messages.
MetricsMetric name, without case sensitivitySearch cpu over the last 24 hours to find metric names containing CPU.

The search is a literal text match, so typing SQL into the search field does not execute SQL. Each query returns up to 500 recent records for the active profile.

Keep a view live

In View options, choose Start live tail to keep updating the results, or Pause live tail to stop those updates while inspecting a result.

3. Create a dashboard from a query

  1. Run a logs or metrics query and choose its table or time series view.
  2. Open View options → Add to dashboard.
  3. Enter a Panel name, such as CPU history or Recent timeouts.
  4. Select New dashboard and enter a Dashboard name, or select an existing dashboard.
  5. Choose Save panel.
  6. Open the dashboard’s tab in Health. Repeat the workflow to add more logs or metrics panels to the same dashboard.

A saved telemetry panel keeps the search text, relative time range, view type, and grouping choice. Its data is queried again when the panel loads, so it is a reusable view rather than a frozen copy of the result.

Example: a service dashboard

Enable logs and metrics for the connections you need. In Metrics, search cpu, choose Last 24 hours and Time series view, then save a panel named CPU history to a new dashboard named Service health. In Logs, search timeout, choose Last hour and Table view, then save Recent timeouts to the same dashboard. The results include any enabled sources with matching records; use source grouping to distinguish them.

If data is missing

  • Check the active profile, the global Telemetry collection switch, and the source’s enable switch.
  • Confirm that the source has Logs or Metrics selected for the view you are querying, then save changes.
  • Clear the search text, widen the time range, and run the query again.
  • Check source connectivity and allow time for new activity to produce records. Retention may have removed older records.
  • If the source picker is empty, save a connection in Studio first.
Continue exploringExplore the s2s CLI
On this page