Time Series Metrics

Raw run logs are essential, but dashboards need shape and direction: are things getting better, worse, or flat?

That's exactly what getDomainMonitorSeries provides: chart-ready aggregates by hour or day.

Why teams need series data

With series points, you can visualize:

  • healthy-rate changes over time
  • average health score movement
  • status distribution by time bucket

Domain monitor trend charts in MailSlurp showing health score and status distribution

This helps both technical and non-technical stakeholders understand risk quickly.

Endpoint

GET /domain-monitor/monitors/{monitorId}/series

Query parameters

  • since
  • before
  • bucket (HOUR or DAY)

cURL example

curl -sS "https://api.mailslurp.com/domain-monitor/monitors/$MONITOR_ID/series?bucket=DAY" \
  -H "x-api-key: $API_KEY"

What a good response looks like

Series responses are most useful when each bucket point contains just enough to drive charts:

  • total runs
  • count of healthy vs failing runs
  • average score (or median) for the bucket

That lets you build trend charts without re-aggregating hundreds of runs in the browser or in a client service.

How to pick the right bucket size

Bucket size is a tradeoff between noise and visibility:

  • HOUR: best when you're debugging "something changed overnight" or you're running checks frequently.
  • DAY: best for weekly reporting and broader posture reviews.

If you're unsure, start with DAY and only drop to HOUR during investigations.

Good chart patterns

  1. Line chart: average health score.
  2. Line chart: healthy rate.
  3. Stacked bars: run count by status.

If your team wants monitoring that drives decisions, not just alerts, trend visualization is mandatory. This endpoint gives you the right data shape for that.