You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I would like to add continuous log monitoring and the ability to write log entries, along with a specified number of logs before and after the occurrence, to another log file.
Describe the solution you'd like
Implement a continuous log monitoring mechanism (like a search-tail agent) that reads new log entries as they are written to the log file.
The system should allow users to define keywords or regular expressions for key events in a config.
When a key event is detected, write the buffered log entries, the key event, and subsequent log entries to an output log file.
This log file would be a subset of the original log file. Search-tail should support monitoring different logs using various config entries in the config file.
Describe alternatives you've considered
Alternatives include manually extracting relevant log segments or using scripts to automate this process, but these methods are less efficient and do not provide the same level of integration and ease of use.
Additional context
This feature could include options to specify the number of log entries before and after a key event, as well as configuration settings for the output log file.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I would like to add continuous log monitoring and the ability to write log entries, along with a specified number of logs before and after the occurrence, to another log file.
Describe the solution you'd like
Implement a continuous log monitoring mechanism (like a search-tail agent) that reads new log entries as they are written to the log file.
The system should allow users to define keywords or regular expressions for key events in a config.
When a key event is detected, write the buffered log entries, the key event, and subsequent log entries to an output log file.
This log file would be a subset of the original log file. Search-tail should support monitoring different logs using various config entries in the config file.
Sample configuration is provided below:
Describe alternatives you've considered
Alternatives include manually extracting relevant log segments or using scripts to automate this process, but these methods are less efficient and do not provide the same level of integration and ease of use.
Additional context
This feature could include options to specify the number of log entries before and after a key event, as well as configuration settings for the output log file.
The text was updated successfully, but these errors were encountered: