Search: "http statistics"

Minor changes Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80% Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (Gen3 only) Manage - Queue statistics: They are now all visible for models with a vast number of queues.

====Minor changes==== * Manage - Alerting - Triggers: The non-editable trigger for Event streaming topic size has been changed to trigger on 95% of the configured size instead of 80% * Manage - Monitoring: Viewing runtime, queue, and HTTP statistics are now limited to 7 days at a time. (Gen3 only) * Manage - Queue statistics: They are now all visible for models with a vast number of queues.

HTTP Statistics

advanced-monitoring-http-statistics

{{/warning}} In this microlearning, we'll delve into the HTTP statistics available through each hosted web service.

With the objective to understand the bredth and depth of the usage of the operations published. == 3. Monitoring HTTP Statistics metrics == Below the various insights provided for HTTP traffic on an API Gateway. === 3.1 Dashboard metrics === When browsing to the HTTP Statistics page, accessible via the Manage - Monitoring section, you can find a view similar to the one below.

[[image:Main.Images.Microlearning.WebHome@advanced-monitori-apigw-http-statistics-6.png]] ==== 3.2.4 Response status ==== In this view, the HTTP response codes can be analyzed.