Products Solutions Templates Pricing Resources

Operational dashboards: real-time monitoring for daily operations

Home / Everything About / Everything About Analytics / Operational dashboards: real-time monitoring for daily operations

You run an e-commerce site. Someone is checking out right now. Checkout is broken. Customer gets error. Customer leaves. You just lost sale.

Without operational dashboard, you would not find error until tomorrow when you review daily report.

With operational dashboard, operations team spots error within seconds. Fixes it immediately. Customer retries. Sale goes through.

Cost of slow detection: hundreds of dollars per hour per error.

Operational dashboards catch problems in real-time, not hours or days later.

The job of operational dashboards

Operational dashboards monitor system health and active operations.

Is website up. Are checkout flows working. Are payment processors responding. Is email sending. Are API calls succeeding.

Operational dashboard is not about revenue or business metrics. It is about system health.

Real-time data requirement

Operational dashboard must update in real-time or near-real-time (within one minute).

Delayed data is useless. If dashboard updates every hour, you miss outages that happen between updates.

Real-time requirement means: operational dashboard is expensive to build and maintain. Use only for critical systems.

What to monitor on operational dashboard

System uptime

Is website responding. Green if up, red if down.

Response time

How fast is website. Green if under two seconds, yellow if two to five seconds, red if over five seconds.

Error rate

What percentage of requests are returning errors. Green if under 0.1%, yellow if 0.1% to 0.5%, red if over 0.5%.

Active transactions

How many transactions happening right now. For reference. Not inherently good or bad.

Conversion funnel in progress

How many visitors are in each step of checkout right now. Drop-off at any step triggers investigation.

API performance

Response times for external integrations. Payment processor, email service, shipping API.

Database performance

Query response times, connection pool health.

Real example: e-commerce operational dashboard

Top section (system health)

Website status: UP (green). Response time: 1.2 seconds (green). Error rate: 0.08% (green). Active users: 423. Transactions in progress: 17.

Middle section (checkout funnel)

Cart view: 127 users. Checkout start: 89 users (70% conversion from cart). Shipping info: 72 users (81% conversion). Payment info: 68 users (94% conversion). Order confirmation: 64 users (94% conversion). Drop-off at shipping info: 17 users (wait, this is higher than normal, investigate).

Bottom section (integrations)

Payment processor: responding in 800ms (green). Email service: 99.8% delivery (green). Shipping calculator: responding in 1200ms (yellow, slightly slow).

Immediate action

Drop-off at shipping info is higher than normal. Investigate whether shipping calculator slowness is causing abandonment.

Alerting system

Operational dashboard should trigger alerts when metrics go red.

Alert to operations team immediately. Not email that might be missed. SMS or Slack or pager that interrupts.

Thresholds should be strict. Do not want false alarms. But better to have one false alarm and catch one real problem than miss problems.

Example thresholds: website down for 30 seconds = alert. Error rate above 1% for 5 minutes = alert. Response time above 5 seconds for 10 minutes = alert. Payment processor not responding = alert immediately.

The on-call rotation

For systems critical enough to need operational dashboard, you need on-call rotation.

Someone is responsible for monitoring 24/7. If alert fires at 3am, on-call person wakes up and fixes problem.

On-call is expensive. But cost of downtime is more expensive.

Only put critical systems on operational dashboard with on-call.

What NOT to monitor

Do not monitor business metrics on operational dashboard. Revenue, conversions, traffic trends are business dashboards, not operational dashboards.

Mixing business and operational confuses purpose. Operational is about system health. Business is about business health.

Separate dashboards for separate purposes.

Dashboard versus alerts

Operational dashboard lets you monitor proactively. Check dashboard before issue becomes critical.

Alerts let you respond reactively. Issue happens, alert fires, you fix it.

Both needed. Dashboard for proactive monitoring. Alerts for reactive response when dashboard is not being watched.

Incident response playbooks

When alert fires, what happens next. Operational team should have playbook for each alert type.

Website down alert: restart web server. If still down, failover to backup. If still down, escalate to senior engineer. Payment processor down alert: switch to backup processor. Notify customers of possible delay. Monitor until main processor recovers. Database slow alert: check connection pool. If full, increase. Check query log. Kill slow queries. Monitor.

Playbooks prevent panic. Clear steps prevent mistakes.