While I think this functionality belongs in the syslog-logger plugin rather than the logstash plugin, it might be useful to share the BuildData object I created for the logstash plugin across both.

cleclerc, what do you think? The logstash plugin sends data across as JSON. Would it be useful to split out BuildData.java in logstash out to share across both plugins so they share a common format?

https://github.com/jenkinsci/logstash-plugin/blob/master/src/main/java/jenkins/plugins/logstash/persistence/BuildData.java

Thanks for pinging me.

Could we imagine that this build details could be relevant for the Audit Trail Plugin which already has 2 outputs: file and syslog?

We could add a logstash output to the Audit Trail Plugin.

https://wiki.jenkins-ci.org/display/JENKINS/Audit+Trail+Plugin

Someone submitted a pull request for this feature: https://github.com/jenkinsci/logstash-plugin/pull/10

I'm all for merging it in to close this issue, but is this good long-term, cleclerc? (i.e. will this just be redundant when a future version of syslog-logger comes out?)

@rgerard I feel that it's good to offer this feature in the logstash plugin waiting for the audit trail plugin to offer something equivalent.

Most of the syslog logic is located in the syslog-java-client dependency, the quantity of code duplication between the 2 plugins (logstash-plugin and audit-trail-plugin) is limited.

Just want to let you know that the generated Syslog messages will comply to the CEE format. So, if you have a logging infrastructure based on Elasticsearch this feature will make log parsing way easier with rsyslog using the mmjsonparse and omelasticsearch module. I think it`s a good idea to have it in the Logstash jenking plugin because it's related to ELK.

Ref:
http://www.rsyslog.com/doc/v8-stable/configuration/modules/omelasticsearch.html
http://www.rsyslog.com/doc/mmjsonparse.html

sysadmin4j, that sounds good. I've commented on the pull request.

Implemented in v1.1.0. Thanks sysadmin4j!