Changes for page Determining cause of log entry
Last modified by Erik Bakker on 2024/02/22 12:35
From version 1.1
edited by Erik Bakker
on 2022/06/13 11:22
on 2022/06/13 11:22
Change comment:
There is no comment for this version
To version 3.1
edited by Erik Bakker
on 2022/06/13 11:24
on 2022/06/13 11:24
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - advanced-monitoring-apigateway-statistics1 +Monitoring API Gateway statistics - Content
-
... ... @@ -1,13 +1,8 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 +In your API Gateway solution, it is important to be able to review the API Gateway statistics. These statistics are available in Generation 3 based runtimes, and available via the Manage phase -> Monitoring Gen3 2 2 3 -# Monitoring API Gateway statistics 4 -In your API Gateway solution, it is important to be able to review the API Gateway statistics. These statistics are available in Generation 3 based runtimes, and available via the Manage phase --> Monitoring Gen3 5 - 6 6 Should you have any questions, please get in touch with academy@emagiz.com. 7 7 8 -* Last update: March 17th, 2022 9 -* Required reading time: 5 minutes 10 - 11 11 == 1. Prerequisites == 12 12 * Advanced knowledge of the eMagiz platform 13 13 * Complete relevant API Gateway microlearnings from Crash course to Intermediate ... ... @@ -15,52 +15,47 @@ 15 15 == 2. Key concepts == 16 16 The API Gateway statistics are geared towards understanding the level of interaction between the API callers and the webservice of the API gateway. With the objective to understand the bredth and depth of the usage of the operations published 17 17 13 +== 3. API gateway statistics == 18 18 19 - 20 - 21 -## 3. API gateway statistics 22 - 23 23 Navigate to the Manage phase and select Monitoring Gen3. On the left hand side select API Management Statistics which opens a page as below. Ensure to select for what environment you want to see these statics 24 24 25 25 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-1.png]] 26 26 27 - ###3.1 API Requests19 +=== 3.1 API Requests === 28 28 This section displays the total number of requests made to the API Gateway. Can be valuable to understand if in a give timeframe requests are made or not. It contains all the requests * other sections will illustrate which requests more specifically. 29 29 30 30 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-7.png]] 31 31 32 - ###3.2 Static resource request24 +=== 3.2 Static resource request === 33 33 This shows the number of request made by the SwaggerUI which is considered a static resource. This can help to understand how often that SwaggerUI is used. 34 34 35 35 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-8.png]] 36 36 37 - ###3.3 Status per user29 +=== 3.3 Status per user === 38 38 This displays per application user what the HTTP response codes where. Based on that response code insight is provided around the behavior of that user such as unauthorized requests. Users are identified by part of their access credential (first part of API key or Client ID). 39 39 40 40 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-6.png]] 41 41 42 - ###3.4 Resources per user34 +=== 3.4 Resources per user === 43 43 This displays per applciation user what resources are specifically used by that user. The colors indicate the resource which are listed as legend to the graph. By selecting a resource in the legend, you can toggle that resource to not display. The graph shows the total number of requests made. 44 44 45 45 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-5.png]] 46 46 47 - ###3.5 Status per resource39 +=== 3.5 Status per resource === 48 48 This display shows the HTTP response codes for every resource/operation available. Could help to understand the health and/or the validity of the operation for the application users. 49 49 50 50 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-2.png]] 51 51 52 - ###3.7 Methods per resource44 +=== 3.7 Methods per resource === 53 53 Shows what HTTP methods are used for every resource/operation 54 54 55 55 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-3.png]] 56 56 57 - ###3.8 Status for status resource / methods per static resource49 +=== 3.8 Status for status resource / methods per static resource === 58 58 Shows the HTTP response codes and what HTTP methods are used by the Swagger UI 59 59 60 60 [[image:Main.Images.Microlearning.WebHome@advanced-monitoring-apigateway-statistics-4.png]] 61 61 62 - 63 - 64 64 == 4. Assignment == 65 65 66 66 Take a moment to review your API Gateway solution and find the Manage * Montoring section to see the API management metrics. Review if you can understand these values ... ... @@ -70,8 +70,6 @@ 70 70 * The API Management statistics are geared towards understanding the actual use of the API gateway. 71 71 * That insight is handy to understand who does what and how often. Yet can also be used for trouble shooting. 72 72 73 - 74 - 75 75 == 6. Suggested Additional Readings == 76 76 77 77 If you are interested in this topic and want more information, please read the release notes provided by eMagiz.