topic Re: Monitoring Cloud Pega application in Open Q&A

Monitoring Cloud Pega application

AravindhanV — Tue, 03 Feb 2026 07:07:18 GMT

Dear Experts,

We are using a cloud‑based Pega deployment, where OneAgent installation is not possible. I’m looking for the best way to monitor Pega in Dynatrace under this limitation.

Specifically, I’d like your recommendations on:

Best monitoring approach for Pega without OneAgent
(Custom Extensions, JMX, REST API polling, log ingestion, etc.)
Any existing Dynatrace Extensions for Pega metrics
(e.g., requestors, agents, queue processors, system health)
Suggested integrations using Pega’s diagnostic endpoints or AES
for:
- performance metrics
- node health
- background processing
- queue/agent statistics
Known limitations or challenges when monitoring Pega Cloud with Dynatrace

If anyone has implemented monitoring for Pega Cloud using Dynatrace, please share any guidance, examples, or best practices.

Thanks!

Re: Monitoring Cloud Pega application

gmanims — Tue, 07 Apr 2026 23:55:45 GMT

Hi @AravindhanV , I am looking for the same option for Pega cloud application monitoring. Any luck? Thanks in advance!!

Re: Monitoring Cloud Pega application

MaximilianoML — Mon, 20 Apr 2026 15:48:44 GMT

Hello, @AravindhanV

I haven’t implemented this myself, but given that the OA installation isn’t possible, I’d probably look at this more as an external monitoring use case than a classic full APM setup.

A few ideas that seem worth exploring are Synthetic Monitoring for availability and key user journeys, polling Pega health/diagnostic endpoints for node and platform health, and custom metric ingestion into Dynatrace for things like requestors, queue processors, agents, or general system health. Log ingestion could also be useful if your Pega Cloud exposes relevant logs, alerts, or exports, and a custom extension might make sense if you want to package the polling and metrics collection in a clean way.

My guess is that the most realistic outcome here would be a solution with focus on availability, performance indicators, node health, background processing health, and queue statistics, rather than deep code-level observability.

The main limitations I’d expect are the lack of deep tracing visibility without OneAgent, the fact that JMX may not be practical in a managed cloud model, and that success would depend heavily on what your Cloud actually exposes through the APIs, endpoints, or log exports. Because of that, it may end up being more of a health + KPI + synthetic monitoring integration than a full observability.

So if anyone here has already done something similar, I’d be very interested to hear what worked best in practice 😀

Re: Monitoring Cloud Pega application

AravindhanV — Tue, 21 Apr 2026 05:13:33 GMT

Thanks @MaximilianoML Good to see you have found an option and great to see you shared over here as well!! Appreciate it