Message call request data having error frequency metrics
A method for error management is provided. The method comprises receiving a message call request regarding an error event generated by a software application. The message call request comprises a message ID associated with an error type. In response to the call request a message cache is searched for the message ID. If the ID is in the cache, an error message associated with the ID is returned. The error message provides a description of the error and suggested remedial action. If the message ID is not in the cache, the error message is fetched from a message repository that contains error messages corresponding to respective message IDs. The fetched error message is loaded into the cache and returned. Message call request data is stored in a metrics repository. The message call request data comprises frequency metrics that describe how often the message ID is received.
1. A method for error management, the method comprising:
using a number of processors for:
receiving a message call request regarding an error event generated by a software application, wherein the message call request comprises a message identification (ID) associated with an error type;
searching a message cache for the message ID;
determining that the message ID is absent from the message cache;
fetching, responsive to determining that the message ID is absent from the message cache, an error message associated with the message ID from a message repository, wherein the message repository contains a number of error messages corresponding to respective message IDs, wherein fetching the error message associated with the message ID from the message repository includes:
forwarding, by a load balancing, an application programming interface call to a service to access an elastic container registry container that holds images of a message cloud application programming interface user interface, allowing access to the message repository stored in a database;
loading the error message into the message cache;
returning the error message; and
storing message call request data in a metrics repository, wherein the message call request data comprises error frequency metrics that describe how frequently the message ID is received from users.
2. The method of claim 1 , further comprising, if the error frequency metrics exceed a defined threshold, notifying a product owner.
3. The method of claim 1 , further comprising:
receiving a revised error message associated with the message ID from a product owner; and
storing the revised error message in the message repository.
4. The method of claim 1 , wherein the error message comprises at least one of:
text;
video;
audio;
hyperlink;
uniform resource locators;
chat; or
multilingual language support.
5. The method of claim 4 , wherein the error message comprises text and the text are in a default language of the software application and support multiple languages.
6. The method of claim 1 , wherein the message repository allows dynamic updates of message records by a product owner using a repository management user interface.
7. The method of claim 6 , wherein updates of the message records do not require changes to the software application.
8. The method of claim 1 , wherein metrics repository data can be monitored by a product owner using an analytics user interface.
9. The method of claim 1 , wherein metrics repository data can be analyzed by a product owner using an analytics user interface.
10. The method of claim 1 , wherein the metrics repository tracks specific message call requests received over time.
11. The method of claim 1 , wherein the metrics repository tracks contexts of the message call requests received over time.
12. The method of claim 1 , wherein the metrics repository tracks software applications generating the message call requests received over time.
13. The method of claim 1 , wherein the message cache and message repository are configured to serve a number of different software applications and act as a common hub interface for storing messages from the number of different software applications.
14. The method of claim 1 , wherein the load balancing is an elastic load balancing, wherein the service is a Fargate service, and wherein the images are docker images.
15. A system for error management, the system comprising:
a storage device configured to store program instructions; and
one or more processors operably connected to the storage device and configured to execute the program instructions to cause the system to:
receive a message call request regarding an error event generated by a software application, wherein the message call request comprises a message identification (ID) associated with an error type;
search a message cache for the message ID;
determine that the message ID is absent from the message cache;
fetch, responsive to determination that the message ID is absent from the message cache, an error message associated with the message ID from a message repository, wherein the message repository contains a number of error messages corresponding to respective message IDs, wherein fetching the error message associated with the message ID from the message repository includes:
forwarding, by a load balancing, an application programming interface call to a service to access an elastic container registry container that holds images of a message cloud application programming interface user interface, allowing access to the message repository stored in a database;
load the error message into the message cache;
return the error message; and
store message call request data in a metrics repository, wherein the message call request data comprises error frequency metrics that describe how frequently the message ID is received from users.
16. The system of claim 15 , further comprising, if the error frequency metrics exceed a defined threshold, notify a product owner.
17. The system of claim 15 , further comprising:
receiving a revised error message associated with the message ID from a product owner; and
storing the revised error message in the message repository.
18. The system of claim 15 , wherein the error message comprises at least one of:
text;
video;
audio;
hyperlinks;
uniform resource locators;
chat; or
multilingual language support.
19. The system of claim 18 , wherein the error message comprises text and the text are in a default language of the software application and support multiple languages.
20. The system of claim 15 , wherein the message repository allows dynamic updates of message records by a product owner using a repository management user interface.
21. The system of claim 20 , wherein updates of the message records do not require changes to the software application.
22. The system of claim 15 , wherein metrics repository data can be monitored by a product owner using an analytics user interface.
23. The system of claim 15 , wherein metrics repository data can be analyzed by a product owner using an analytics user interface.
24. The system of claim 15 , wherein the metrics repository tracks specific message call requests received over time.
25. The system of claim 14 , wherein the metrics repository tracks contexts of the message call requests received over time.
26. The system of claim 15 , wherein the metrics repository tracks software applications generating the message call requests received over time.
27. The system of claim 15 , wherein the message cache and message repository are configured to serve a number of different software applications and act as a common hub interface for storing messages from the number of different software applications.
28. The system of claim 15 , wherein the load balancing is an elastic load balancing, wherein the service is a Fargate service, and wherein the images are docker images.
29. A computer program product for error management, the computer program product comprising:
a computer-readable storage medium having program instructions embodied thereon for:
receiving a message call request regarding an error event generated by a software application, wherein the message call request comprises a message identification (ID) associated with an error type;
searching a message cache for the message ID, wherein the message;
determining that the message ID is absent from the message cache;
fetching, responsive to determining that the message ID is absent from the message cache, an error message associated with the message ID from a message repository, wherein the message repository contains a number of error messages corresponding to respective message IDs, wherein fetching the error message associated with the message ID from the message repository includes:
forwarding, by a load balancing, an application programming interface call to a service to access an elastic container registry container that holds images of a message cloud application programming interface user interface, allowing access to the message repository stored in a database;
loading the error message into the message cache;
returning the error message; and
storing message call request data in a metrics repository, wherein the message call request data comprises error frequency metrics that describe how frequently the message ID is received from users.
30. The computer program product of claim 29 , further comprising, if the error frequency metrics exceed a defined threshold, notifying a product owner.
31. The computer program product of claim 29 , further comprising:
receiving a revised error message associated with the message ID from a product owner; and
storing the revised error message in the message repository.
32. The computer program product of claim 29 , wherein the error message comprises at least one of:
text;
video;
audio;
hyperlinks;
uniform resource locators;
chat; or
multilingual language support.
33. The computer program product of claim 32 , wherein the error message comprises text and the text are in a default language of the software application and support multiple languages.
34. The computer program product of claim 29 , wherein the message repository allows dynamic updates of message records by a product owner using a repository management user interface.
35. The computer program product of claim 34 , wherein updates of the message records do not require changes to the software application.
36. The computer program product of claim 29 , wherein metrics repository data can be monitored by a product owner using an analytics user interface.
37. The computer program product of claim 29 , wherein metrics repository data can be analyzed by a product owner using an analytics user interface.
38. The computer program product of claim 29 , wherein the metrics repository tracks specific message call requests received over time.
39. The computer program product of claim 29 , wherein the metrics repository tracks contexts of the message call requests received over time.
40. The computer program product of claim 29 , wherein the metrics repository tracks software applications generating the message call requests received over time.
41. The computer program product of claim 29 , wherein the message cache and message repository are configured to serve a number of different software applications and act as a common hub interface for storing messages from the number of different software applications.
42. The computer program product of claim 29 , wherein the load balancing is an elastic load balancing, wherein the service is a Fargate service, and wherein the images are docker images.