antoine-vigneau-sonarsource / sonar-logs Goto Github PK

Given a task uuid, extract all logs related to this task.
Careful: a simple grep is not enough as Java stack traces are not prefixed with task id in logs.

tasksand steps export can be quite large (mostly steps) to the point that it becomes hard to do anything with them in spreadsheet software (everything is slow). It would be good to have filtering capabilities to 1/ focus on what we want (probably after some previous investigations) and 2/ reduce CSV file size so it's ok to work with them

This could be generic but useful filters we can think of are:

• project for both tasks and steps export. So we only focus on one project (e.g. it had been identified that one project has some issues)
• task_id for steps export (useless for tasks) - Though it's similar to #5 then
• step for steps export (e.g. it had been identified that one particular step is always taking long, typically Persist live measures)
• type for tasks
• branch_type for tasks

Currently, the report command is designed (and simplified) to only extract the longest task. A top-10 would certainly be more useful in case there is a pattern to detect.
This could even be parameterized.

Usecase:

• export log window in the report command
• maybe it could be used to plot on a graph the CE load (number of workers occupied over time)

How
This will require parsing more than task information, ie. the log line itself to extract the date/time at the beginning.