Monitor environments monitoring-environments
Learn how to monitor your environments in Cloud Manager.
Metric thresholds thresholds
System Monitoring in Cloud Manager is done by observing the individual instances within an environment and tracking a variety of metrics for each instance. Each metric has two defined thresholds: a warning threshold and a critical threshold.
If a metric is over its warning threshold (but below its critical threshold), it is considered to be in a warning state.
If a metric is over its critical threshold, it is considered to be in a critical state.
ÃÛ¶¹ÊÓƵ Managed Services sets the thresholds, which you can view in Cloud Manager. In most cases, thresholds are consistent between customers, but there are cases where ÃÛ¶¹ÊÓƵ Managed Services edits thresholds to match specific customer requirements. Direct any questions that you have about the thresholds to your Customer Success Engineer (CSE).
Access system monitoring accessing-system-monitoring
-
Log into Cloud Manager at and select the appropriate organization and program.
-
Click the ellipsis button of the program that you want to monitor.
-
In the menu, under the Manage heading, click Show Monitoring to open the Reports page that shows system monitoring information.
.
System monitoring overview system-monitoring-overview
The System Monitoring section of the Reports page lists the monitored environments in the program. It reports on their high-level health across the following four separate categories:
- Host
- Storage
- Network
- Application
The status in each category is a summary of individual metrics. If any metric in a category is in the critical state, the entire category is in a critical state for the purpose of the overview page. The same summarization can be viewed at an environment level and at an instance level.
System monitoring detail system-monitoring-detail
To view the details of specific metrics, click one of the category columns of a specific instance or the category title in the left navigation. Each detail page shows a series of graphs for the metrics within that category. You can either view the metrics for all instances in an environment or for a specific instance. You can switch between the environment and instances using the dropdown boxes in the top-right corner.
The navigation on the left shows the available metrics within the currently selected category for which there is data for the currently selected environment and instances.
An individual graph shows the status and a graph of the data over time along with the thresholds. If multiple instances are displayed, each instance’s data are in a separate series.
Individual series can be hidden on a graph by clicking on the series in the legend.
For example, if you click the warning threshold series, you see only the critical threshold.
Metric definitions metric-definitions
Host host
- Load Per Core: The number of processes that the CPU is executing. Or, the number of queued processes that are in a waiting state averaged over a one (load1), five (load5), and fifteen (load15) minute period.
- Process Count: The number of processes currently open.
- User Count: The number of users with an active shell session.
- Memory Usage: The percentage of system memory currently allocated.
- JVM Memory: The size (in megabytes) of the allocated Java heap.
- Old Generation Space: The percentage of JVM old generation memory currently allocated.
Network network
- CQ Port Check: The response time in seconds to access the AEM or Dispatcher port. There are different metrics for author, publish, and Dispatcher.
Storage storage
- Disk Space: The used disk space (in megabytes) for each mount point on the host. There are different metrics for each mount point. At a minimum, there are metrics for
/and/mnt, but additional mount point metrics may be available depending on the specific instance configuration. - Folder Size
- AEM Segment Store: The used disk space (in gigabytes) for the AEM Segment Store.
Application application
- Replication Agent: The time (in seconds) for a test replication event
- There are separate metrics for each replication agent.
- Dispatcher Flush: The number of items currently in the Dispatcher flush queue
SLA reporting sla-reporting
You can see the performance of your production AEM environment relative to your contracted service level agreement (SLA).
The following graph shows the monthly SLA attainment for 2019.
As with the system monitoring graphs, rolling over a data point shows the specific values for that month.
The Event Analysis section under this graph shows the set of incidents that occurred for the program during the currently selected year. Each incident has a time range, a cause, and a set of comments.
SLA metrics sla-metrics
- Author Contract: The SLA defined in your contract with ÃÛ¶¹ÊÓƵ Managed Services for the author tier.
- AMS Author SLA: The measured uptime of the production author tier, factoring incidents caused by vendors or by ÃÛ¶¹ÊÓƵ.
- Author SLA: The measured uptime of the author tier ignoring scheduled downtime such as maintenance windows.
- End User Contract: The SLA defined in your contract with ÃÛ¶¹ÊÓƵ Managed Services for the publish tier.
- AMS End User SLA: The measured uptimes of the production publish tier, factoring incidents caused by vendors or by ÃÛ¶¹ÊÓƵ.
- End User SLA: The measured uptime of the publish tier ignoring scheduled downtime such as maintenance windows.
Video tutorial video-tutorial
This video provides and overview of using the charts produced by Cloud Manager Reports for a view into your program environments.