# Continuous Monitoring for Shipment Tracking

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

- Publisher: TechSupport Team
- Canonical page: https://techsupport-team.com/case-studies/shipment-tracking-24-7-technical-monitoring/
- Updated: 2026-11-16

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

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

Related services: [24/7 technical support](https://techsupport-team.com/services/24-7-technical-support/)

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

Table: Reported results and their measurement scope

| Metric | Baseline | Result | Units | Measurement window | Sample / population | Source and scope |
| --- | --- | --- | --- | --- | --- | --- |
| Event uptime | 99.83% | 99.97% | % | 6 months | Event uptime; separate from event-delivery delay. | Client Datadog; Scope: One carrier outage was excluded from the uptime comparison. |
| Alert lag | 25 min | 3 min | min | 6 months |  | Client PagerDuty |
| Auto-resolved tickets | 0% | 46% | % | 6 months |  | Client 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](https://techsupport-team.com/contact/) or explore [24/7 technical support](https://techsupport-team.com/services/24-7-technical-support/).

## Related pages

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

## Contact

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