Error handling API Gateway - Support perspective

{{container}}{{container layoutStyle="columns"}}(((

In a previous microlearning, we have discussed the error handling of the API Gateway from the perspective of the client that is calling the API. In this microlearning, we will focus on how you can provide support to those clients based on the information that is captured and stored in eMagiz. This will help you to better support your clients.

3

4

Should you have any questions, please contact [[academy@emagiz.com>>mailto:academy@emagiz.com]].

5

6

== 1. Prerequisites ==

7

8

* Intermediate knowledge of the eMagiz platform

9

10

== 2. Key concepts ==

11

12

This microlearning centers on error handling for API Gateway from a support perspective.

13

14

* The key aspects are:

15

** The client is responsible for handling the error correctly

16

** eMagiz will log the exception to provide support

17

** You can use the log to determine what went wrong where and when

18

19

== 3. Support Perspective ==

20

21

In a previous microlearning, we have discussed the error handling of the API Gateway from the perspective of the client that is calling the API. In this microlearning, we will focus on how you can provide support to those clients based on the information that is captured and stored in eMagiz. This will help you to better support your clients.

22

23

* The key aspects are:

24

** The client is responsible for handling the error correctly

25

** eMagiz will log the exception to provide support

26

** You can use the log to determine what went wrong where and when

27

28

As we learned from the previous [[microlearning>>doc:Main.eMagiz Academy.Microlearnings.Crash Course.Crash Course API Gateway.crashcourse-api-gateway-error-handling-from-a-client-perspective.WebHome||target="blank"]] surrounding this topic is that the error message is given back to the client. As a result, the client is primarily responsible for introducing proper error handling to safeguard against data loss. Having said that eMagiz does also log the exception. You can find these exceptions in the Manage phase of eMagiz under Monitoring -> Log entries. Here you can filter on the API Gateway runtime, on level warning, and message (Exception in message flow). This will provide you with a list of warnings on the API Gateway level.

29

30

[[image:Main.Images.Microlearning.WebHome@intermediate-understanding-error-handling-in-emagiz-error-handling-from-a-support-perspective--error-list-manage.png]]

31

32

Each of these warnings corresponds with an error message that has been sent back to the client. In case a client wants to have more information before resending a certain message you can help him by browsing through this page. Do note that these log entries disappear after fourteen days so you cannot get to them indefinitely.

== 4. Assignment ==

Check out if you have a project in which the API Gateway pattern is used. If so, check out if you can find any errors that have occurred and see whether you can interpret them.

37

38

== 5. Key takeaways ==

39

40

* The key aspects are:

41

** The client is responsible for handling the error correctly

42

** eMagiz will log the exception to provide support

43

** You can use the log to determine what went wrong where and when