Service
A service in the supply chain represents one or several application components that perform a defined, measurable function as part of an internal or user-initiated request. Its performance is key to understanding application performance, but only indirectly impacts user experience. You can measure performance as experienced internal to the business application in the context of services.
This topic discusses Services discovered through APM targets and user-defined application maps. For details about Services discovered through container platform targets, see this topic.
Synopsis

Synopsis | |
---|---|
Provides: | Response time and transactions to Business Transactions and Business Applications |
Consumes from: | Application Components, Database Servers, and the underlying nodes |
Discovery: | Turbonomic discovers the following:
Note:
If you do not have an APM target, you can create your own Services using the Application Maps feature. For details, see Application Map. |
Monitored resources
Turbonomic monitors the following resources:
-
Response time
Response time is the elapsed time between a request and the response to that request. Response time is typically measured in seconds (s) or milliseconds (ms).
-
Transaction
Transaction is a value that represents the per-second utilization of the transactions that are allocated to a given entity.
The Response Time and Transaction charts for a Service show average and peak/low values over time. You can gauge performance against the given SLOs. By default, Turbonomic estimates SLOs based on monitored values. You can set your own SLO values in policies.
Actions
None
Turbonomic does not recommend actions for services discovered through APM targets, but it does recommend actions for the underlying Application Components and nodes. The Pending Actions chart for services list these actions, thus providing visibility into the risks that have a direct impact on their performance.