InfraWatchdogradar
Service map

Group your noise into the services your team actually thinks in.

CloudWatch shows you 4,000 log groups. Your team thinks in 12 services. The service map closes that gap once — and every other feature (trace, alerts, reviews, investigations) gets smarter for it.

What you'll actually see
services · acme robotics · 3 mapped
acme-apiproductiontier-1
3 ECS · 1 RDS · 2 EC2
team · Payments
/ecs/acme-api/web/ecs/acme-api/payments/ecs/acme-api/fraud/aws/rds/acme-api-pg/postgresql
acme-apiproductiontier-1
3 ECS · 1 RDS · 1 Atlas
team · Platform
/ecs/acme-api/web/ecs/acme-api/auth/ecs/acme-api/billing/aws/rds/acme-api-pg/postgresql
acme-workerproductiontier-2
3 ECS · 1 RDS · 1 Atlas
team · Data
/ecs/acme-worker/email/ecs/acme-worker/exports/ecs/acme-worker/scheduler/aws/rds/acme-analytics-pg/postgresql

What changes for the on-call engineer

Set it once

Map a service to its log groups. Trace, alerts, reviews, and investigations all use the same definition.

Auto-discover

We crawl your AWS account read-only and suggest the obvious mappings on day one.

Owner + tier

Tag each service with its owning team and tier. Routing, escalation, and reviews all key off this.

How it works

step · 01

Connect AWS

Read-only IAM role. We never get write access — never can.

step · 02

Auto-suggest

We crawl ECS, RDS, EC2, and CloudWatch log groups and propose service groupings.

step · 03

Confirm + tag

Approve, edit, and add team + tier tags. The rest of the product configures itself.

Pairs well with

Trace journey

Where the service map decides which log groups to fan across.

Cluster reviews

Reviews run per service — the map defines the unit.

Resolve incidents in 30 seconds, not 30 minutes.

Connect your AWS account in read-only mode and let Radar take the next page.