# Reducing Kafka Ingestion Lag for Energy Monitoring

> 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%.

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/energy-monitoring-kafka-ingestion-support/
- Updated: 2026-11-16

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

## 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

Related services: [DevOps support](https://techsupport-team.com/services/devops-support/)

## 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

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Source and scope |
| --- | --- | --- | --- | --- | --- |
| Availability | 99.78% | 99.95% | % | 6 months | Client Datadog; Scope: The six-month comparison excludes one Azure regional outage. |
| Ingestion lag | 90 s | 6 s | s | 6 months | Client Grafana |
| Sev-2 incidents | 17/mo | 3/mo | /mo | 6 months | Client 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](https://techsupport-team.com/contact/) or explore [DevOps support](https://techsupport-team.com/services/devops-support/).

## Related pages

- [DevOps support](https://techsupport-team.com/services/devops-support/): The related service for this engagement.

## Contact

Request engineers from TechSupport Team or ask a question: https://techsupport-team.com/contact/
