Logs

The Logs page — Log Explorer — brings the logs from all of your resources into one place, where you can search, filter, and watch them stream live. Find it under Observability in the sidebar.

Overview

  • One place for every resource's logs — no need to open each instance separately.
  • Automatically collected — structured logs from the services you run on DanubeData are gathered for you. There is nothing to install or configure.
  • Search and filter across any of your instances by keyword, regular-expression pattern, or level.
  • Live tail — watch logs stream in as they happen, with automatic reconnect if your connection drops.
  • Volume chart — see log and error volume over time, then drag to zoom into any window and jump straight to the matching lines.
  • Retention — the searchable runtime archive covers 10 days.

Supported resources

Log Explorer covers the logs from:

  • Databases — MySQL, PostgreSQL, MariaDB
  • Cache — Redis, Valkey, Dragonfly
  • Queues — RabbitMQ
  • Managed Apps
  • Serverless Containers (Rapids)

VPS instances are not included here — their logs live inside the guest operating system, which you reach directly over SSH or the browser VNC console.

  • Resources — pick one or more of your instances, or view everything at once.
  • Time range — 15 minutes, 1 hour, 6 hours, 24 hours, 3 days, 7 days, or 10 days (default: the last 1 hour).
  • Keyword search — type any text to show only the lines that contain it.
  • Regex pattern — match with a regular expression when a plain keyword isn't specific enough.
  • Level — show everything, or narrow to just error-level entries (errors, panics, and fatals).

The volume chart

Above the log stream, a chart shows how many log lines — and how many error lines — each selected resource is producing over your chosen window. Drag across the chart to zoom into a narrower slice of time; the stream below updates to the matching lines, which makes it easy to zero in on a spike.

Live tail

Select a single resource and turn on Live tail to watch its logs arrive in real time. If your connection drops, it reconnects on its own. (Live tail follows one resource at a time; when you have several selected at once, the view refreshes on an interval instead.)

Jumping in from an instance

Every supported instance's own page has a View logs link that opens Log Explorer already filtered to that resource — handy when you're looking at one service and want its logs without setting up a filter first.

Rapids build and run output

Build output and the captured output from Scheduled Runs/one-off Runs are separate from the runtime archive. Their stored text expires ten days after completion. Expired output is no longer returned by the console or API; hourly cleanup removes it from the application database. The run/build history metadata remains available, including status and diagnostic error summaries. Active build and run output is not removed by this cleanup.

This retention is platform-controlled. It does not provide a customer setting for shorter or longer retention, and it is not a deletion guarantee for infrastructure backups or node-local logs. Contact support if your processing documentation needs an end-to-end retention commitment.

Sensitive information

The platform collects the output your services produce. It does not automatically remove patient information or secrets printed by your application, build scripts, jobs or database diagnostics. Review logging at each source, including query parameters and exception messages, before stating that your logs contain no sensitive data. Masked environment-variable fields in the console are not log redaction.