CloudLine
Configuration

Custom Date Ranges

Pick any window you want — last month, May 15 to May 19, this quarter — for the uptime and metrics views. Pro+ feature.

By default, every bot's Monitor view shows one of five fixed ranges: 1 hour, 24 hours, 7 days, 30 days, 90 days. The custom-range picker lets Pro and Business users select an arbitrary start and end date.

Plan availability

PlanWhat's available
StarterFive fixed presets only (1h / 24h / 7d / 30d / 90d).
ProSame five presets + custom range up to 365 days.
BusinessSame as Pro. Plus CSV export of any range.

The Starter plan sees a lock icon on the custom-range picker; clicking it shows a "Pro+ feature" tooltip without opening the calendar.

Using the picker

  1. On a bot's detail page, click the date range button in the top-right corner of the Monitor view.
  2. On the left, pick a preset (one-click) or select a start date on the calendar.
  3. Select an end date. The popover shows a hover preview between the two as you move your cursor.
  4. Click Apply.

The bot detail view re-fetches uptime, metrics, and incidents for the new window.

Built-in presets in the popover

The picker includes seven one-click shortcuts beyond the five fixed-range buttons:

  • Yesterday
  • Last 3 days
  • Last 7 days
  • Last 30 days
  • Last 90 days
  • This month (1st of current month → now)
  • Last month (full previous calendar month)

These match what most users want without typing a date.

Limits

  • Maximum span: 365 days. The picker rejects anything wider.
  • Older than your plan's retention: the window is accepted, but the older slice is filled from the 5-minute aggregate table (uptime_buckets) instead of raw events. You still get the chart and uptime %, but per-second resolution drops off after the retention window. See Retention policy.
  • Future dates: the picker doesn't stop you from picking them, but the data view will simply show "—" past the current moment.

Timezone

The calendar grid and presets compute in your browser's local timezone. The values sent to the server are UTC millisecond timestamps, so the window you picked at 14:00 in Berlin matches the same wall-clock minute in CloudLine's backend.

If you switch timezones between picks (e.g. you're traveling), reopen the picker — it re-anchors on the new local time.

What changes with the range

Every chart and metric on the bot detail page recomputes for the selected window:

  • Uptime %, MTTR, MTBF, SLA budget — all computed over the new range
  • Incident list — only incidents whose start is inside the window
  • Telemetry charts — sparkline span matches the window
  • Reliability tier badge — recomputed from the new range's uptime

CSV export (Business)

Business users get an Export CSV action that downloads the raw events for the currently selected range. The export endpoint is rate-limited; one large export per few minutes.

CSV columns:

  • t — event timestamp (ms epoch, UTC)
  • status — bot status at that tick
  • latency_ms, memory_mb, cpu_pct, event_loop_lag_ms — telemetry fields
  • guilds, gateway_ok, gateway_stale_sec — connection state
  • All other telemetry fields the bot reported

If a field is missing (the bot didn't report it that tick), the cell is empty.