Response time chart
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).
Turbonomic collects response time data from entities discovered by Applications, Databases, and APM targets. Entities include Business Applications, Business Transactions, Services, Application Components, and self-hosted Database Servers. When you set the scope to any of these entities, the data that Turbonomic collected displays in the Response Time chart.
The chart shows average and peak/low values over time. Use the selector on the chart to change the time frame.
An empty chart could be the result of delayed discovery, target validation failure, unavailable data for the given time frame, or an unsupported entity (see the next section for a list of supported entities).
Supported entities
Data is available in the Response Time chart for the following entities:
| Target | Supported entities |
|---|---|
| AppDynamics | Business Application, Business Transaction, Service, Application Component |
| Datadog | Business Application, Business Transaction, Service, Application Component |
| Dynatrace | Business Application, Service, Application Component |
| Instana |
Business Application, Business Transaction, Service, Application Component, Database Server |
| JBoss | Application Component |
| JVM | Application Component |
| MySQL | Database Server |
| New Relic | Business Transaction, Service, Application Component, Database Server |
| Oracle | Database Server |
| SQL | Database Server |
| Tomcat | Application Component |
| WebLogic | Application Component |
| WebSphere | Application Component |
Response time SLOs
To evaluate the performance of your applications and Database Servers, set Response Time SLOs (Service Level Objectives) as an operational constraint in policies. For applications, you can set the SLO at the Business Application, Business Transaction, Service, or Application Component level.
After you create a policy, the SLO value appears as a solid straight line in the Response Time chart. You can then gauge performance against the given SLO.
If you do not set an SLO, Turbonomic estimates SLO based on historical Response Time data collected from the target, and then displays the estimated value in the Capacity and Usage chart, as Response Time capacity. This estimated value is not reflected in the Response Time chart.
When you set an SLO value, Response Time capacity in the Capacity and Usage chart shows as N/A.
Response time SLOs for container platform services
When you add a container platform target, Turbonomic discovers services monitored by AppDynamics, Instana, Dynatrace, and New Relic.
To generate actions that adjust pod replicas, services must be discovered by the Kubeturbo agent that you deployed to your environment, as well as collect performance metrics through Instana or DIF (Data Ingestion Framework). In addition, Turbonomic requires that you turn on horizontal scaling and specify Response Time SLOs in policies for the affected services.
Response time SLO is the desired weighted average response time (in milliseconds) of all Application Component replicas associated with a Service.
If you specified SLOs but turned off horizontal scaling in policies, no actions generate but SLO values will continue to display in the Response Time chart for Services, for your reference. This allows you to gauge performance against those SLOs.