Management of log entries

Last modified by Erik Bakker on 2024/09/15 19:38

Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.

In this microlearning, we will focus on how you can quickly and easily determine the origin of log entries. In other words, what caused the logging.

Should you have any questions, please contact academy@emagiz.com.

1. Prerequisites

Basic knowledge of the eMagiz platform
Understanding of Monitoring concept
One or more log entries raised in the last two weeks within the context of your (Academy) project

2. Key concepts

This microlearning centers around determining the origin of log entries.
By origin, in this context, we mean: Identifying which flow wrote an entry to the log that might be in need of analysis.

Determining in which flow a log entry is raised can be done with the help of the Manage phase in eMagiz.
- In the Manage phase you have an option called Monitoring. In this overview, you will see all logging that is relevant within your project.
This overview allows you to filter on various elements, such as runtime, type, and timestamp. This way you can conduct a more focused search.
Double-clicking on a log entry provides you with the relevant details
Note that log entries are not shown in full when they exceed a certain size so takes this into account when logging
When you know the flow and the details you have determined the origin of the log entry

3. Determining the origin of log entries

You can determine the origin of a log entry with a two-step approach:

Search in the Monitoring overview for log entries
Select a specific log entry for further analysis

3.1 Monitoring overview Manage

To see and analyze the log entries you need to navigate to Manage -> Monitoring. This overview shows all log entries within your project that have been written to the log in the last fourteen days (assuming you did adhere to the fair use policy). Within this overview, you have the ability to search on various options such as runtime, type, and timestamp.

intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-unfiltered.png

intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-filtered.png

3.2 Select a specific log entry for further analysis

After you have filtered the log entries to your liking you can select a specific log entry by double-clicking on the log entry. By doing so a pop-up will be presented in which the details of the log entry are written. On this details page, the flow and message are the most relevant from a user perspective.

intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-log-entry-details.png

Note that some log entries are grouped as they appeared in short proximity after each other and have to do with the same logging.

intermediate-active-monitoring-determining-origin-of-log-entry--manage-monitoring-log-entry-details-grouped.png

4. Key takeaways

Determining in which flow a log entry is raised can be done with the help of the Manage phase in eMagiz.
- In the Manage phase you have an option called Monitoring. In this overview, you will see all logging that is relevant within your project.
This overview allows you to filter on various elements, such as runtime, type, and timestamp. This way you can conduct a more focused search.
Double-clicking on a log entry provides you with the relevant details
Note that log entries are not shown in full when they exceed a certain size so takes this into account when logging
When you know the flow and the details you have determined the origin of the log entry

5. Suggested Additional Readings

If you are interested in this topic and want more information on it please read the help text provided by eMagiz when executing these actions.