my understanding of JMX is that its per VM. With AEM cloud, they will scale up VMs and servers as needed. In this case, how does one access and/or aggregate the jmx info? As Adobe dont offer any sort of monitoring / alerting solution, being able to query the number of errors, or the average time for API responses via jmx would be a good partial solution.
The jmx console seems to be available on local dev instances, but not on any. cloud instances (gives 403)
Solved! Go to Solution.
Views
Replies
Total Likes
New Relic One has following features, which might help you and closer to your requirements:
Direct access to a dedicated New Relic One account
Instrumented New Relic One APM agent that shows exact method calls with line numbers, including external dependencies and databases
Holistic performance optimization by combining key metrics from infrastructure-level monitoring and application (Adobe Experience Manager) monitoring
Exposure of AEM as a Cloud Service JMX Mbeans and health checks directly within New Relic Insights metrics, allowing for deep inspection of application stack performance and health metrics.
References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...
The console are not available, that's right. What information do you need/want to monitor?
New Relic One has following features, which might help you and closer to your requirements:
Direct access to a dedicated New Relic One account
Instrumented New Relic One APM agent that shows exact method calls with line numbers, including external dependencies and databases
Holistic performance optimization by combining key metrics from infrastructure-level monitoring and application (Adobe Experience Manager) monitoring
Exposure of AEM as a Cloud Service JMX Mbeans and health checks directly within New Relic Insights metrics, allowing for deep inspection of application stack performance and health metrics.
References: https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...
Is this an adobe hosted cloud environment, or self hosted AWS/Azure environment? The JMX console will be most likely secured and inaccessible by design. I would deploy the prod packages to a lower environment and try connecting there.
Views
Likes
Replies
Views
Likes
Replies