HTTP Monitoring landing page
- Last UpdatedApr 16, 2025
- 4 minute read
The HTTP Monitoring landing page in Pega Diagnostic Center (PDC) accurately monitors inbound network traffic patterns in Pega Cloud®.
You can use this information for performance tuning, reporting, and general application health checks. You can assess performance data for individual applications, even those that use the Pega Digital Experience (DX) API.
HTTP Monitoring is available only for Pega Cloud version 3 production environments in all Pega-supported AWS regions.
Use the HTTP Monitoring feature to view aggregated connection data for all your Pega applications and detailed data for individual Pega applications. HTTP Monitoring gives you an external perspective on the total response time of requests sent to Pega applications. These response times are measured through aggregated HTTP endpoint data from Amazon Web Services (AWS) Application Load Balancing (ALB) log files.
HTTP Monitoring measures total response time in Pega Cloud. To measure end-to-end response time, combine this data with the latency from your side and from the internet. Doing so gives you a holistic view of the time spent at every stage, to help with timely detection and resolution of connection performance issues.
The HTTP Monitoring overview displays HTTP Monitoring data for all your endpoint URLs. You can view specific endpoints by clicking Switch to the detail view and making a selection from the Endpoint URL drop-down list.
PDC automatically refreshes the HTTP Monitoring data every hour. You can also
manually refresh the data by clicking in the
upper-right corner and selecting Refresh.
The following table describes all the charts and tables on the HTTP Monitoring landing page:
Chart or table name | Description |
---|---|
Overview for all requests | This chart provides a summary for each HTTP status code group,
including HTTP 1xx, 2xx, 3xx, 4xx, and 5xx. These statistics display
only if HTTP data from these status code groups is available within
the selected time interval. You can display the request statistics for all the endpoint URLs in your system or filter them individually.
|
HTTP status codes | This chart displays the number of HTTP status codes that occurred within a specified time interval. |
HTTP 2xx requests response time | This chart displays the average duration of HTTP 2xx requests
within a specified time interval. It also displays the percentile of the duration of each request from the specified endpoint at a given time. Note: Click a point on the
timeline to open a popup and switch to Event Viewer. Filters are
set automatically on PEGA0001 ,
PEGA0011 , and PEGA0069
events. |
Request summary for configured endpoints | This table provides response time and volume data for client
requests to each configured endpoint URL in Pega applications. You can observe
performance over time. Columns are:
The static content aggregates files with the following extensions: .jpg, .jpeg, .png, .ico, .gif, .woff, .woff2, .js, .svg, .css, .htm, .html, .txt, and .json. Additionally, the following API endpoint placeholders are used in the endpoint names:
Both application endpoint types, for example,
You can create custom views for this table. For more information, see Creating new HTTP Monitoring views. |
Related content
- Creating new HTTP Monitoring views
You can configure new Request summary for configured endpoints table views on the HTTP Monitoring landing page in Pega Diagnostic Center (PDC).