Edit online

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:

Table 1. HTTP Monitoring landing page displayed data
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.

Total requests
The total number of requests from a specified time interval.
Average requests
The average number of requests per second. PDC calculates this value by dividing total requests by the number of seconds in the specified time interval.
Max requests
The average time, in seconds, of the total number of requests made at the peak time during the specified time interval. Minutes are used to count the requests when the specified time interval is six hours or less. Hours are used to count the request when the specified time interval is longer than six hours.
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:

Group
The group for the endpoint URL. For example, Application, API, CDH, DX API v2, or Pega API v1.
Method
The method used to connect. For example, GET, POST, or PATCH.
Endpoint URL
The endpoint URL used to connect to the Pega application.
HTTP 1xx/2xx/3xx/4xx/5xx (1h)
The total number of requests that returned a 1xx, 2xx, 3xx, 4xx, or 5xx code within the past hour.
Previous HTTP 1xx/2xx/3xx/4xx/5xx (1h)
The total number of requests that returned a 1xx, 2xx, 3xx, 4xx, or 5xx code over the previous hour.
Avg time (10 m)
The average response time for all requests within the past ten minutes, in seconds.
Avg time (1h)
The average response time for all requests within the last hour, in seconds.
Previous Avg time (1h)
The average response time for all requests over the previous hour, in seconds.

Previous time displays connection data from 60 to 120 minutes ago.

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:

{resource_path}
Represents the specific resource or operation being requested in the API. This placeholder is added to the endpoint URL based on the regular expression patterns used for data aggregation.
{static_content}
Represents static content that aggregates files with specific extensions.
{dynamic_content}
Represents dynamic content that consolidates a variety of custom endpoints into a single application endpoint.
{email}
Represents anonymized email addresses.

Both application endpoint types, for example, application and application_, are aggregated into a single endpoint.

You can create custom views for this table. For more information, see Creating new HTTP Monitoring views.