Having an option to send send the logs towards an ElasitcSearch backend in the background - but do not modify the way how Jenkins stores an displays the logs locally.
The problem
If we use ElasticSearch as the main logging backend, Jenkins can not be operate without Elastic. By this Elastic is becoming a critical infrastructure - and if it's offline or crashed, the whole Jenkins infrastructure will not work anymore due to logs are not visible to the user.
Therefore, having the logs duplicated would be awesome:
Staying on the Jenkins and visualized as if there was no change at all
Sending them into ElasticSearch for processing / data mining
Yes, the data would be duplicated - but this is totally fine
kuisathaverat
commented
3 months ago
What feature do you want to see added?
Having an option to send send the logs towards an ElasitcSearch backend in the background - but do not modify the way how Jenkins stores an displays the logs locally.
The problem
If we use ElasticSearch as the main logging backend, Jenkins can not be operate without Elastic. By this Elastic is becoming a critical infrastructure - and if it's offline or crashed, the whole Jenkins infrastructure will not work anymore due to logs are not visible to the user.
Therefore, having the logs duplicated would be awesome:
Yes, the data would be duplicated - but this is totally fine
Upstream changes
No response
Are you interested in contributing this feature?
No response