We have already used the Production Process Monitor a lot for debugging in the last unit. You can skip this lesson if you already have a good feeling about the function of the app from the videos in the last unit.
The entry page offers you a list of all the production processes that were executed in the last hour by default. You can use the filter bar (1) on top of the page to narrow down the search. Typical cases include:
- Search for all production processes that failed during the last week using the status filter. This might be a very interesting query to execute in your productive system to check if the processes do as they are supposed to do.
- Use the Production Process filter to only view the production process you are currently working on.
- Use the Parameter/Variable Value filter to search for a specific SFC to check which processes were working on the SFC, so you can explain certain data you found in the SFC report.
The gear at the top right of the table (2) allows you to add additional columns. Sometimes, it can be interesting to see, for example, the trigger name or type of the production process. In the preceding graphic, the column selection is open. (We will soon discuss the different options to trigger the production process.)
Lastly, from the overview screen, you can also jump to the production process statistics (3), which summarizes different aspects of the execution, such as the duration.
When selecting a production process log from the list, you will be taken to the log itself, which offers all the details according to the log level selected. The following screenshots are all done with the log-level debug, so all information is present.
Note
The following numbered list is related to the numbered elements in the preceding screenshot.- The log header contains all the basic information about the production process. The links behind the process name and design name allow you to navigate directly into the design app. The Process Instance ID is unique and very valuable if you want others to check the log. You can just share the Instance ID and they can find it in the Production Process Monitor themselves by using the specific filter.
- On top of the Process Instance Steps, you can select between the steps of the selected instance and the call stack leading to the instance (Process Instance Hierarchy). In this example, we will only analyze the Process Instance Steps, as the call hierarchy is flat. However, if you build production processes using multiple layers of subprocesses, this view might become interesting. If you select a step in the list, the details view on the right side of the screen will adjust accordingly, whether you are in the Graphic View or the Process Parameter View.
- Like for the list on the main selection, you can also configure the columns of this list. This might be especially interesting if you analyze performance issues. You can see the number of retries of the services and the individual start and end times allowing you to check for waiting times between the steps. For example, in this execution from the graphic, you will see massive waiting times as it was executed in debugging mode and waited for the user's input between the steps.
- In the screenshot, the graphic view showing the production process itself is selected, but most of it is behind the column selection. (The process is the one from the last unit, so you already know it quite well, and so the column selection was moved on top of it.)
- In the Log View, you can find all details of the execution as a classic log.
- In case the log is not fully visible by scrolling down, you may select Technical Details to see the full log.
- In the Process Parameter View, you will find all inputs and outputs of the selected element in the Process Instance Steps list. If no data is displayed, double-check if you have selected the proper log level to see the information.