Run-time Monitoring States for IntegrationServer-instanceName
In response to the sagcc get monitoring runtimestate and sagcc get monitoring state commands, IntegrationServer-instanceName run-time component provides information about the following key performance indicators (KPIs):
KPI | Description |
Running Services | Use this KPI to monitor the number of services that Integration Server is running concurrently so that you can take corrective actions if the number approaches a critical value. The number of running services includes services that were triggered, scheduled, or directly invoked. The KPI uses the following marginal, critical, and maximum values: ![*](chapterTOC_bullet.png) Marginal is 80% of the high water mark of concurrently running services. ![*](chapterTOC_bullet.png) Critical is 95% of the high water mark of concurrently running services. ![*](chapterTOC_bullet.png) Maximum is 100% of the high water mark of concurrently running services. This is shown in the Threads area of Integration Server. |
Response Time | Use this KPI to monitor service response time so that you can take corrective actions if the response time approaches a critical value. The KPI uses the following marginal, critical, and maximum values: ![*](chapterTOC_bullet.png) Marginal is 80% of the high water mark of service response time. ![*](chapterTOC_bullet.png) Critical is 95% of the high water mark of service response time. ![*](chapterTOC_bullet.png) Maximum is 100% of the high water mark of service response time. |
Service Errors | Use this KPI to monitor how many service exceptions have occurred in the last minute so that you can take corrective actions if the current number of exceptions is approaching a critical value. The KPI uses the following marginal, critical, and maximum values: ![*](chapterTOC_bullet.png) Marginal is 5 exceptions in the last minute. ![*](chapterTOC_bullet.png) Critical is 20 exceptions in the last minute. ![*](chapterTOC_bullet.png) Maximum is more than 20 exceptions in the last minute. |