-
Try out the new Jake: AI Coding Assistant for LabVIEW (beta)!
Get answers to questions about LabVIEW and discuss your code.
Error Log by BenjaminR - Toolkit for LabVIEW Download
Version | 1.0.0.8 |
Released | Feb 19, 2022 |
Publisher | BenjaminR |
License | BSD |
LabVIEW Version | LabVIEW>=17.0 |
Operating System | Windows, Mac, and Linux |
Dependencies | jki_lib_json_serialization jki_lib_serialization jki_lib_unicode labview_open_source_lib_data_manipulation labview_open_source_lib_serializer labview_open_source_project_lib_serializer_jki_json oglib_error oglib_lvdata |
Project links | Homepage |
Description
A set of classes to provide comprehensive error logging functionality.
The Error Log library takes a modular approach and offers several categories of components: Logger, Handler, and Serializer.
- Loggerexposes the interface that application code directly uses. It keeps track of a set of Handler and send the log records to the appropriate destination.
- Handler is set of methods to effectively output (write/display) log records. Handler filters out log records based on their Level.
- Serializer specifies the layout of log records in the final output.
Levels:
- DEBUG : Detailed information, typically of interest only when diagnosing problems.
- INFO : Confirmation that things are working as expected.
- WARNING : An indication that something unexpected happened. The application is still working as expected.
- ERROR : Due to a more serious problem, the application has not been able to perform some tasks.
- CRITICAL : A serious error, indicating that the application itself may be unable to continue running.
When you set a logging level to an Handler, you’re telling the library you want to handle all events from that level on up. If you set the log level to INFO, it will include INFO, WARNING, ERROR, and CRITICAL messages. DEBUG messages will not be included here.