Client: RouteWise · Logistics, Travel & Marketplaces · US transportation management software provider (190 staff)

Continuous Monitoring for Shipment Tracking

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

TechSupport Team staffed technical monitoring and response for RouteWise’s Kafka shipment-tracking platform. In a six-month comparison, client Datadog records show event-platform uptime rising from 99.83% to 99.97%. PagerDuty alert lag fell from 25 to 3 minutes.

Client and engagement facts

Client
RouteWise
Industry
Logistics, Travel & Marketplaces
Business context
US transportation management software provider (190 staff)
Delivery model
24/7 technical monitoring and response
Application
Transportation management with shipment tracking
Supplied geography
US
Company size in source
190 staff
Coverage
24/7, three shifts

Application stack and tools

Application stack

  • Java
  • Kafka
  • PostgreSQL
  • AWS

Tools used

  • Datadog
  • PagerDuty
  • Jira Service Management

Why Support Was Needed

The monitoring loop was slow to spot issues in a system processing 1.2 million events per day. The engineers shortened the polling interval and automated responses to routine cases.

Technical Work

  • Shortened the alert polling interval from 25 minutes to 3 minutes.
  • Automated responses to routine monitoring tickets.
  • Added a Kafka consumer-group restart detector.

Representative Incident

A carrier outage delayed 200,000 events in month four. The engineers detected the issue and recorded its impact and internal escalation. The client retained carrier communications.

Results and how they were measured

Reported results and their measurement scope
MetricBaselineResultUnitsMeasurement windowSample / populationSource and scope
Event uptime99.83%99.97%%6 monthsEvent uptime; separate from event-delivery delay.Client Datadog; Scope: One carrier outage was excluded from the uptime comparison.
Alert lag25 min3 minmin6 monthsClient PagerDuty
Auto-resolved tickets0%46%%6 monthsClient JSM

Evidence and Limitations

One carrier outage was excluded from the uptime comparison. Uptime and event delivery are separate measurements. Jira Service Management tracked automated ticket resolution.

Carrier Communication During Outages

RouteWise owned carrier communication. TechSupport Team detected incidents and handled internal escalation.

Scope a Similar Engagement

Describe your event volume, monitoring coverage and how your team escalates failures to carrier systems. Request a support plan or explore 24/7 technical 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.