Understanding how your services interact shouldn’t require digging through individual traces or relying on outdated architecture diagrams. Service Map gives you a real-time, visual representation of your service architecture — built automatically from your OpenTelemetry trace data.

What You Can Do Now

See your entire service architecture at a glance – Service Map automatically discovers services and their dependencies from your trace data. Each service node shows request rate, P95/P99 latency, and error rate, while color-coded health indicators let you instantly spot healthy, degraded, and critical services.

Investigate incidents faster – When a service starts failing, open Service Map to immediately see its upstream callers and downstream dependencies. Spot cascading failures across your architecture, identify the root cause service, and jump straight into filtered traces with one click — View All Traces, View Slow Traces, or View Error Traces.

Understand every connection between services – Click on any edge to see detailed metrics for that dependency: total requests, success/error breakdown, Avg/P50/P95/P99 latency, the communication protocol, and the HTTP methods being used. No more guessing about how services communicate.

Discover which endpoints are actually being used – The Top Endpoints view shows the most frequently called endpoints for each service with their request counts. Identify unused endpoints, discover undocumented APIs, and verify that traffic is flowing where you expect it — replacing outdated tribal knowledge with real-time data.

Filter and focus on what matters – Use filters to narrow the map by health status, service role (Server/Client), error rate ranges, or latency ranges. During incidents, quickly isolate all critical services to focus your investigation. Customize thresholds to match your environment — changes apply immediately.

Access from anywhere in your workflow – Service Map is available as a top-level item in the left navigation, from within any Tracing App, and from your Logs, Synthetics, Monitoring, or Infra Apps, as well as from Alerts. Jump to Service Map during any troubleshooting workflow without losing context.

How It Works

Service Map is built from your existing OpenTelemetry trace data — no additional instrumentation or configuration required. If you’re already sending traces to Sematext, Service Map is ready to use:

1. Open Service Map from the left navigation under Insights and Analysis
2. Select the Tracing App you want to visualize
3. Click Go to Service Map to see your service topology

The map reflects actual service communication patterns based on real traffic, updating in real time as new trace data arrives.

Service Map vs. Network Map

Service Map joins Network Map as a complementary topology visualization. While Network Map shows infrastructure-level connectivity using eBPF (traffic bytes, CPU, memory, I/O), Service Map shows application-level service dependencies from OpenTelemetry traces (request rate, latency, error rate). Use both together for full-stack visibility — from infrastructure to application.

Getting Started

Service Map works with your existing Sematext Tracing setup. If you’re already sending OpenTelemetry traces, simply open Service Map from the left navigation — your service topology is waiting for you.

New to Sematext Tracing? Get started in minutes:

1. Create a Tracing App in Sematext Cloud
2. Add the OpenTelemetry SDK to your application
3. Configure Sematext Agent with OTLP receiver enabled
4. Open Service Map and see your service dependencies

Ready to visualize your service architecture? Check out the documentation to learn more.

Start Free Trial

---