Project Description
The goal of this project is to create a tool to monitor changes in a log file or any text file between specific events in the system.
The specific events can mean any start of end of a process or many processes. Or such events could also be triggered by the user. Or we can set a timer at appropriate start and end times.
And during these 2 specific events some log files are assumed to be changed in the system.
The tool being developed will extract only the changed logs and display them on the UI.
Current Status
The project is still conceptual and nothing has been implemented yet.
Usage
The use for this project is specifically for someone who is learning some software programs and wish to know what all changes take place when a program runs and executes some tasks.
This project will also help to debug a software program.
And also will help to file bugs with precise logs.
Goal for this Hackweek
The goal for this hackweek is conservative.
A simple GUI using perl-tk or python-django framework or similar tools.
Provision to show parts of any textfile on the UI.
Provision to set the starting point and ending point inside the logfile to acquire the logs.
Resources
The source code and documentation will be maintained in : https://github.com/sudarshannm/grab_logs
Looking for hackers with the skills:
This project is part of:
Hack Week 23
Activity
Comments
Be the first to comment!
Similar Projects
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/
Bring to Cockpit + System Roles capabilities from YAST by miguelpc
Bring to Cockpit + System Roles features from YAST
Cockpit and System Roles have been added to SLES 16 There are several capabilities in YAST that are not yet present in Cockpit and System Roles We will follow the principle of "automate first, UI later" being System Roles the automation component and Cockpit the UI one.
Goals
The idea is to implement service configuration in System Roles and then add an UI to manage these in Cockpit. For some capabilities it will be required to have an specific Cockpit Module as they will interact with a reasource already configured.
Resources
A plan on capabilities missing and suggested implementation is available here: https://docs.google.com/spreadsheets/d/1ZhX-Ip9MKJNeKSYV3bSZG4Qc5giuY7XSV0U61Ecu9lo/edit
Linux System Roles: https://linux-system-roles.github.io/