Details
-
New Feature
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
None
Description
We want a standardized method for storing the logging generated by Hop as well and querying this logging in a standardized way.
While we have generic ways of storing logging we don't have methods of reading them. It would be great if the current logging GUI (using Neo4j) could be made to use a standard log reader so that other logging serialization can be used as well.
One obvious idea to read logging information is to use pipelines for retrieval of workflow, action, pipeline and transform logging. 4 new transforms could accept the data in the pipelines in a standardized way. The system wouldn't know where the data came from. We could define a few standard variables which contain the filters that need to be applied (the transforms to get for a particular pipeline, the log channel ID of a workflow, ...)
It's also important then to have a way to query the logging from the command line as well. "Hop Log" would be a great tool to have on a remote server when trying to see what happened in a workflow or pipeline. We could have basic ways of finding keywords in the logs, executions with errors and so on.
