Generating an event log for the collection
 |
 |
 |
 |
 |
Prerequisites
- Access to the Management > Event log (SP026) menu.
- Access to the Execution > Data collection (SP006) menu.
- Configured event log rules.
- Configured occurrence.
- Executed data collection.
Introduction
After defining the occurrences and configuring the event log rules, it is possible to generate the event log effectively. Its creation can be manual or automatic.
This feature allows for storing the records and then analyzing the performance of the data collections added in the system.
See below how to set both configurations:
Generating an event log manually
1. Access the Management > Event log (SP026) menu.
2. Expand the More button and click on the 3 quadrants option.
3. Select a data collection and, in the 3rd quadrant, click on the 
button.
4. On the event log data screen, check if the Date and Time fields are correct.
5. Fill in the Sample # field with the identification of the sample in which the anomaly was found. Use the 
button to locate the record.
6. In the Occurrence field, select the previously created occurrence that will be associated with the event log.
7. Provide an explanation for generating the event log.
8. Click on the 
button.
Generating an event log automatically
1. Access the Execution > Data collection (SP006) menu.
2. Select the desired collection and click on the 
button.
3. Fill out the readings (if the characteristic is of the variable type) or the number of items (if the characteristic is of the attribute type).
4. Click on the Save and next characteristic button.
5. If a value that does not comply with the rules configured in the event log has been inserted, the event log screen will be displayed. In this case, fill in the Occurrence field to enter the previously added occurrence that will be associated with the event log.
6. In the Explanation field, provide more details about the generation of the event log.
7. Click on the Save button.
By taking these steps, it is possible to notice that, whereas the manual event log is filled out by the user to identify a problem, the automatic event log is activated when the rules are not followed. For further details, access the Configuring the event log rules article.
As of version 2.1.09, SoftExpert SPC considers the user's browser, no longer the server's time, to record the time of both the data collection sample and the event log.
Conclusion
This article allowed for understanding how to generate a manual or automatic event log in order to analyze data collections created in the system.
Now that the event log is properly created, it is possible to identify and specify the causes of detected problems To do so, access the Analyzing an event log article.