how to access jmx console(s) in a production cloud env?

[TB3dock]

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)

[Jörg_Hoh]

The console are not available, that's right. What information do you need/want to monitor?

[TB3dock]

We want to monitor servlet response times, number of calls per minute, number of errors, and the same for calls which our servlets make to 3rd party apis. Without this, we are blind to problems or slowdowns.

[Jörg_Hoh]

That is a very good usecase for it, although I would question that you need direct access to the JMX console for it. You rather an interface for a monitoring system, which can pick up data created by this integration. Can you create a feature request for it, at best here in the Forums and as well as via Support.

[Jörg_Hoh]

Besides that the only way I can imagine is to create a servlet which you can query from an external system and which provides that data (in whatever format). I agree that there should be a more standardized way to achieve this.

[TB3dock]

Im thinking of integrating either New Relic Event + log API, or Application Insights (aka Azure monitoring). When we signed up for AEM, the Adobe sales and technical team told us we would get New Relic for server side and custom event monitoring and alerting, then once we paid, they told us it had been withdrawn. Not good.

[Jörg_Hoh]

I cannot comment on NewRelic, but I would suggest you to push that topic to get a definitive answer.

[TB3dock]

is system/console/configMgr also blocked for Cloud? If so, how does create or edit osgi configurations?

[moek18753296]

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.