Transactions and services
Web and mobile applications are built upon services that process requests like web requests, web service calls, and messaging. Such "server-side services" can take the form of web services, web containers, database requests, custom services, and more. Services may in turn call other services.
Processes are essentially containers that host services. When you look at processes, you're seeing topology information. Whereas services give you code-level insight. For example, you might have a Tomcat process that hosts a web application in the form of a server-side service. While processes are host-centric, associated with a single machine in your environment, services are request-centric and therefore typically span across multiple machines in a data center.
Basic concepts
Analysis
- Service analysis types
- Service analysis timings
- Response time distribution and outlier analysis
- Service response time hotspots
- Service flow
- Service flow filtering
- Filter monitoring data via request attributes
- Service backtrace
- PurePath visualization
- PurePath capture errors
- Context-specific drill down
- Analyze individual service instances
- Memory profiling
Configuration
- Service monitoring settings
- Customize service naming
- Set up request naming using request attributes
- Configure service error detection
- Capture request attributes based on web request data
- Capture request attributes based on method arguments
- Define custom services
- Define queue messaging consuming custom services
- Custom API definitions