Client: GridWatch · Regulated Verticals · EU energy monitoring SaaS (145 staff)

Reducing Kafka Ingestion Lag for Energy Monitoring

By TechSupport Team. Published November 16, 2026. Updated .

TechSupport Team provided around-the-clock reliability engineering for GridWatch’s energy monitoring platform. Over six months, the client’s Grafana records show ingestion lag falling from 90 to 6 seconds. Datadog recorded availability rising from 99.78% to 99.95%.

Client and engagement facts

Client
GridWatch
Industry
Regulated Verticals
Business context
EU energy monitoring SaaS (145 staff)
Delivery model
Managed reliability engineering
Application
Energy monitoring platform
Supplied geography
EU
Company size in source
145 staff

Application stack and tools

Application stack

  • Go
  • Kafka
  • InfluxDB
  • Kubernetes
  • Azure

Tools used

  • Datadog
  • Grafana
  • PagerDuty

Why Support Was Needed

A Kafka partition imbalance created lag during peak hours across a platform monitoring 9,000 sites. Engineers made ingestion health visible and adjusted partition and consumer-group settings.

Technical Work

  • Built SLO dashboards for ingestion and availability.
  • Rebalanced Kafka partitions.
  • Tuned consumer groups for peak-hour patterns.

Representative Incident

An Azure regional outage in month five affected 3% of sites for 20 minutes. The team documented the outage and its effect in the incident register.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
Availability99.78%99.95%%6 monthsClient Datadog; Scope: The six-month comparison excludes one Azure regional outage.
Ingestion lag90 s6 ss6 monthsClient Grafana
Sev-2 incidents17/mo3/mo/mo6 monthsClient PagerDuty

Evidence and Limitations

The six-month comparison excludes one Azure regional outage. The reported availability was 99.95%. The stated availability objective was above 99.95%. The reported 99.95% result does not meet the strict objective of availability above 99.95%.

Service Objectives and Review

The team reviewed p95 ingestion lag and availability weekly. The targets were under 10 seconds and above 99.95%, respectively.

Scope a Similar Engagement

Share the number of sites, the ingestion rate and the service objectives your on-call team tracks. Request a support plan or explore DevOps support.

Get a technical support plan

Tell us which application needs support, what is reaching your engineers and when you need coverage. TechSupport Team will review the fit and explain the next scoping step.

  • We reply by email.
  • We agree a call about the roles, your stack and the hours.
  • If there is a fit, we propose engineers after an assessment.

A short outline is enough. Add your stack and coverage hours if you know them. Do not include credentials or customer data.

Add coverage and team details

We use these details only to reply to you. Describe the application, stack and hours you need covered. Keep credentials and sensitive technical data out of this form. We save the brief for delivery and use Telegram to notify our team.