Client: FabriSense · Telecom & Manufacturing · German smart-factory IoT provider (180 staff)

Reducing False Downtime Alerts for Smart Factories

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

TechSupport Team supported the Kafka and TimescaleDB alert pipeline on FabriSense’s factory monitoring platform. Over five months, client Datadog records show false downtime alerts falling from 240 to 77 per week. Notification time fell from nine minutes to 90 seconds.

Client and engagement facts

Client
FabriSense
Industry
Telecom & Manufacturing
Business context
German smart-factory IoT provider (180 staff)
Delivery model
IoT support
Application
Smart-factory IoT with downtime alerting
Supplied geography
German
Company size in source
180 staff

Application stack and tools

Application stack

  • Python
  • Kafka
  • TimescaleDB
  • Kubernetes
  • Azure IoT

Tools used

  • Datadog
  • PagerDuty
  • Grafana

Why Support Was Needed

Shared thresholds across device types and Kafka consumer lag triggered false downtime alerts that interrupted production. The engineers tuned thresholds by device model and addressed lag in the pipeline.

Technical Work

  • Added sensor threshold checks per device model.
  • Fixed the Kafka consumer lag causing 40% of false alerts.
  • Built per-device alert calibration.

Representative Incident

A plant network outage generated a cluster of false alerts in month three. TechSupport Team recorded the impact in the alert register. The client retained responsibility for plant networking.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSource and scope
False alerts240/wk77/wk/wk5 monthsClient Datadog; Scope: The five-month false-alert comparison excludes one plant network outage.
Notify time9 min90 sBaseline: min; Result: s5 monthsClient PagerDuty
Dashboard uptime99.1%99.9%%5 monthsClient Grafana

Evidence and Limitations

The five-month false-alert comparison excludes one plant network outage. Notification time and dashboard uptime use PagerDuty and Grafana.

Plant and Platform Ownership

FabriSense managed on-site networks. TechSupport Team handled alert calibration and the data pipeline.

Scope a Similar Engagement

Share which devices generate false alerts and where plant networking hands off to the application team. Request a support plan or explore application 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.