Search: "http statistics"

. (#792) Manage -> Monitoring (HTTP Statistics): The details page will now show the display name of the user that initiated a request instead of the Id.

. (#792) * Manage -> Monitoring (HTTP Statistics): The details page will now show the display name of the user that initiated a request instead of the Id.

We will explore various statistics and functionalities, such as queue statistics, HTTP statistics, runtime statistics, message redelivery, queue browser, and data sink, to understand how eMagiz facilitates message tracing and monitoring across the integration platform.

For more information on queue statistics, please check out the following [[Crashcourse Messaging>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course Messaging.crashcourse-messaging-interpreting-queue-statistics-gen3||target="blank"]]. ===== 3.1.2 HTTP Statistics ==== In addition to the queue statistics, there are the HTTP statistics used for the API Gateway.

For more information on HTTP statistics, please check out the following [[HTTP Statistics>>doc:Main.eMagiz Academy.Microlearnings.Advanced Level.Advanced monitoring.advanced-monitoring-http-statistics.WebHome||target="blank"]]. ===== 3.1.3 Runtime Statistics ==== The overview of the runtime statistics provides similar information to the summary of the HTTP statistics.

[[image:Main.Images.Release Blog.WebHome@183-release-blog--runtime-statistics-key.png]] [[image:Main.Images.Release Blog.WebHome@183-release-blog--queue-statistics-key.png]] [[image:Main.Images.Release Blog.WebHome@183-release-blog--http-statistics-key.png]] Once you click on a runtime, queue, or resource, you will navigate to a detailed page containing the key graphs & metrics and various other graphs that will help you monitor your solution. [[image:Main.Images.Release Blog.WebHome@183-release-blog--runtime-statistics-detail.png]] [[image:Main.Images.Release Blog.WebHome@183-release-blog--queue-statistics-detail.png]] [[image:Main.Images.Release Blog.WebHome@183-release-blog--http-statistics-detail.png]] {{info}}In future releases, we will unlock additional Manage capabilities within the platform, such as alerting and notifications based on the information shown in the graphs.

This means that runtime statistics are sorted by "Process CPU usage" (highest first), queue statistics are sorted by "Messages in queue" (highest first), and HTTP statistics are sorted by "Unsuccessful requests" (highest first).

//__Alphabetical sorting on user level in HTTP statistics__// Variables in the 3rd generation runtimes HTTP statistics detail pages are now sorted case insensitive. == **Bug Fixes** == //__Flow designer styling__// The styling of the flow designer's left component panel has been restructured, solving a rare bug which would break the styling of certain functionalities.

//__Fixed a typo in the HTTP statistics overview__// We fixed a typo in the HTTP statistics overview.

The release notes of this can be found [[here>>doc:Main.Release Information.Runtime Images.WebHome||target="blank"]]{{/info}} //__Detailed HTTP Statistics now show user info in specific additional cases__// To solve a bug for a specific client we changed the logic to show the user info (i.e. first part of the api key) in a specific implementation just as we already do in our standard implementations.

. == **Next generation improvements and bug fixes** == //__Enhanced overview of the HTTP Statistics__// As of now all resources that have been called atleast once since deploying them will now show up in the left-bottom graph of the HTTP Statistics. This will make it easier to see whether a particular operation was called within a timeframe.

This removes the need for custom XSD to validate incoming request to the SOAP webservice. The new HTTP Statistics page can be leveraged to review SOAP traffic as well. * The Docker Cloud templates are now also connected to the eMagiz support infrastructure providing cloud instance level alarms === **Improvements** === * Performance Deployment plan When running a Deployment plan on a large environment, the browser would consume a significant amount of CPU.

. ** Runtime Statistics - Other Metrics *** Data measurements ** Queue Statistics - Other Metrics *** Data measurements * The following graphs now show the maximum value within the selected time frame ** Runtime Statistics - Overview *** Memory usage *** CPU usage [[image:Main.Images.Release Blog.WebHome@release-228-runtime statistics.png]] * The following tables have an improved styling. ** HTTP Statistics - Overview *** Problematic requests *** All requests == **Feedback Items** == //__Failover deployment plan__// The deployment plan steps with type 'Failover' are now deprecated, meaning they can no longer be added to a deployment plan.

{{/info}} === **User name shown in HTTP Statistics**~* === The details page will now show the display name of the user that initiated a request instead of the Id.