Getting Started
Service Monitoring uses an Infra App and Sematext Agent on the hosts you want to observe. For Kubernetes, deploy the agent on the worker nodes whose workloads you want to monitor.
Requirements¶
| Feature | Minimum Sematext Agent version |
|---|---|
| Network Map | 4.4.0 |
| API Radar | 4.6.0 |
See the Network Map setup guide for network collection requirements and enabling topology collection. API Radar shows an outdated-agent banner when monitored hosts need an agent update. Use Go to Fleet to identify those hosts.
Verify network data¶
Open Service Monitoring → Network → Map. Check that services and their connections appear. Switch to Services, Kubernetes, Hosts, or Connections to inspect the same topology in tables.
If data is missing, see Network Map Troubleshooting.
Verify API data¶
- Open Service Monitoring → API Radar → Services Overview.
- Select a time range containing traffic to the service you want to inspect.
- Open Endpoints and find a method and path for that service.
- Select the endpoint and inspect its request volume, observation status, and available metrics.
Next steps¶
- Explore the Network Map to understand service dependencies and infrastructure connections.
- Use Network tables to inspect services, Kubernetes workloads, hosts, and connections.
- Review API Radar Services Overview to find services and endpoints requiring attention.
- Investigate request volume, latency, and errors in Endpoints.
- Manage Ignored Endpoints and review SSL Certificates.