Search: "http statistics"

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.

HTTP Statistics

advanced-monitoring-http-statistics-exercise

{{/warning}} This exercise will provide practical guidance on interpreting the detailed level metrics in eMagiz for your HTTP traffic in your model by observing the data in the HTTP Statistics overview in Manage. Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]]. == 1.

Exercise == Navigate to Manage and execute the following steps: * Open the "Monitoring" section * Open the "HTTP Statistics" overview * Select an endpoint that you want to analyze further * Analyze each of the metrics provided to you on this page and try to understand them == 3. Solution == In this short movie, you will find the solution for viewing the HTTP statistics and analyzing them for a single operation.

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.

Manage - Monitoring - HTTP Statistics: For models with containers deployed on the next generation eMagiz runtime: A new dashboard is introduced, providing an overview of failed and successful requests over all resources allowing users to identify problems more easily.

API statistics has been renamed to HTTP statistics. Manage - Monitoring - Runtime statistics: For models with containers deployed on the next generation eMagiz runtime: A new dashboard is introduced, providing an overview of memory and CPU usage of all runtimes allowing users to identify problematic runtimes more easily.

. ** Manage - Monitoring - HTTP Statistics: For models with containers deployed on the next generation eMagiz runtime: *** A new dashboard is introduced, providing an overview of failed and successful requests over all resources allowing users to identify problems more easily. *** A detail view for resources is introduced to show requests per user, request methods, response status and response times. *** API statistics has been renamed to HTTP statistics. ** Manage - Monitoring - Runtime statistics: For models with containers deployed on the next generation eMagiz runtime: *** A new dashboard is introduced, providing an overview of memory and CPU usage of all runtimes allowing users to identify problematic runtimes more easily. *** A detail view for runtimes is introduced to show memory usage, CPU usage, log events, threads, data measurements, as well as fifteen new graphs providing detailed JVM metrics. ** Manage - Monitoring - Queue statistics: For models with containers deployed on the next generation eMagiz runtime: *** A new dashboard is introduced, providing an overview of the messages in queue, as well as queue throughput over all queues users to identify problematic queues more easily. *** A detail view for queues is introduced to show the total messages added to queue, messages in queue, message throughput, queue consumers, data measurements as well as fourteen new graphs providing detailed queue metrics. * Deploy - Cloud Templates: New Cloud Templates are available for single-lane environments to execute a maintenance update.

Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it.

. * Manage - Monitoring: HTTP statistics page now displays all the resources. (#960) * Manage - Alerting: congestion control will be enabled by default with ten alerts per ten minutes, and the user cannot see or change it. * General - Infra: Changed the library for storing metadata in the eMagiz Control Tower.

Minor changes Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected.

====Minor changes==== * Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change and can be multiply selected. * Deploy - Architecture: The container calculations are improved.

. (#544) (#869) Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052) Bug fixes Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes.

. (#544) (#869) * Manage - Monitoring: Variable values in HTTP statistics details dashboards are sorted, refreshed on time change, and can be multiply selected. (#1042) (#1046) (#1052) ====Bug fixes==== * Deploy - Architecture: Users with edit rights in deploy can edit certificates. (#1054) * Deploy - Containers: We fixed an issue that some unconfigured flows are deployed incorrectly in the new generation runtimes. * General: In some places, the context menu showed too much horizontal whitespace; this has been fixed. * Create - Flow Designer: Flow designer styling implementation has been updated as part of a set of measures to solve styling issues.

. (#696) Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it. Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856) Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486) Bug fixes Design - Solution design: We hide systems without functional integration now. (#714) Create - API Gateway: Security header case insensitive Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow.

. (#696) * Manage - Explore: "Save as test message" button opens a pop-up that allows you to edit your test message's name, description, content, and headers before saving it. * Manage - HTTP statistics: Fixed a typo in the HTTP statistics dashboard. (#856) * Manage - Alerting: By default, no filter is applied to the status when navigating to the "Notifications" overview or resetting the filters on the "Notifications" overview. (#486) ====Bug fixes==== * Design - Solution design: We hide systems without functional integration now. (#714) * Create - API Gateway: Security header case insensitive * Create - Flow designer: Enabling redelivery for your integration is applied after resetting your offramp and exit flow.

Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases.

. * Manage - Monitoring: Detailed HTTP statistics will now show the correct user in case of API key authorization in more cases.

. (#1070) Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063) Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action.

. (#1070) * Manage - Monitoring: Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. (#1063) * Administration - My account: When an account password change request is made, even when this fails, a mail is sent to the account owner to inform on the action. * Administration - My account: When changing a password, it is compared to a list of known database breaches for security.