index=jenkins_console |stats values(host), values(source) host is Jenkins hostname configured in the plugin, probably you need disable them if you have multiple instances ... View more

looks like a config issue. the HEC token is either incorrect or does not have write access to jenkins_console, or jenkins_console index doesn't exist at all ... View more

the argument lines were discarded, [workspace-name] launcher-name(powershell/bash) arguments it may relate to https://issues.jenkins-ci.org/browse/JENKINS-52729 I verified on Jenkins 2.190.3 and it fine (1.642.4 isn't), Could you please try latest Jenkins LTS version https://jenkins.io/doc/upgrade-guide/? ... View more

Could you kindly check pipline related plugins (such as workflow-job, workflow-support) versions to make sure they are consistent with other masters ... View more

please simply remove the Custom Metadata configure and save, you donot need it for the app, it works out of box. The option is for advance users who want to develop their own app and custom index/source etc ... View more

I am afraid not. you have to replace js and conf files manually, such as ack 'jenkins_statistics' -l |xargs -IABC sed -i '' -E 's/jenkins_statistics/sky_statistics/g' ABC ack: https://beyondgrep.com/install/ or use ripgrep: https://github.com/BurntSushi/ripgrep ... View more

could you please try v2.0.2 ... View more

you can config it in Jenkins global config page "Custom Metadata" section, then run a jenkins job and check the build events. SplunkLogService.send method is not for public use and not documented. ... View more

I think EventType may help to category the logs ... View more

If you want to category jenkins build console log for specific failure text, could you please try EventType Console log can be located in index=jenkins_console. Note: single line match only, multiple lines will not work ... View more

I haven't heard any user complain about the default metadata config. I am wondering the splunk config, e.g. if you used a heavy forwarder for "Http Input" , you can not search the data on heavy forwarder, you have to go to search head or indexer. To verify it, pls run hec_host=<splunk-host> hec_port=8088 hec_token=<splunk-token> curl -k "https://${hec_host}:${hec_port}/services/collector/event" -H "Authorization: Splunk ${hec_token}" -d \ '{"host":"test-host","index":"jenkins_console","sourcetype":"json:jenkins","source":"logger://dummy","event":{"level":"INFO","log_source":"cmdline","message":"Test HEC"}}' ... View more

the HEC token doesn't have write access to jenkins_statistics, please config the token http://dev.splunk.com/view/event-collector/SP-CAAAE7F ... View more

can you see any data in the Search app, pls search index=jenkins* ... View more

The plugin version is pretty old, could you please upgrade to latest version on the Jenkins update center? ... View more

try this one index=jenkins_statistics type=completed|stats count by job_name,host ... View more

search for builds don't have test cases index=jenkins_statistics "test_summary.total"=0 search for test case keyword index=jenkins "keyword" | `expand_testcase` ... View more

Added exec_node for each pipeline step in 1.7.1 (Dec 7, 2018) https://wiki.jenkins.io/display/JENKINS/Splunk+Plugin+for+Pipeline+Job+Support ... View more

job_duration doesn't include queue time, only includes test time. please note test run time is different with test_summary.duration when you run tests in parallel. If your jenkins support pipeline, I suggest you mark it with different stages https://jenkins.io/doc/pipeline/steps/pipeline-stage-step/ so the app will show a summary for each stage (stage run time and result) ... View more

I think it counted pipeline steps, maybe we can try mvdedup, e.g. index=jenkins_statistics host="FQDN-OF-JENKINS_MASTER" event_tag=job_event type=completed | rename "stages{}.children{}.exec_node" as pipeline_nodes | eval exec_nodes=mvdedup(pipeline_nodes) | eval build_on_node=coalesce(exec_nodes, node) | chart count by build_on_node useother=f | sort -count ... View more

of course you can use custom dashboard, you could try run the sample spl index=jenkins_statistics host="FQDN-OF-JENKIS-MASTER" event_tag=job_event type=started ( node="JENKINS-AGENT-NAME" OR "stages{}.children{}.exec_node"="JENKINS-AGENT-NAME" ) | rename "stages{}.children{}.exec_node" as exec_node | eval build_on_node=coalesce(exec_node, node) | timechart count by build_on_node Then "Save as Report". You can also create a custom dashboard with node filter and time filter, please checkout the free book https://www.splunk.com/goto/book and dashboard doc https://docs.splunk.com/Documentation/Splunk/7.2.3/Viz/WebFramework ... View more

https://wiki.jenkins.io/display/JENKINS/Splunk+Plugin+for+Pipeline+Job+Support #scripted pipeline sendSplunkConsoleLog { node{ sh "echo testjob"; } } #declarative pipeline pipeline { agent any options { timeout(time: 1, unit: 'HOURS') sendSplunkConsoleLog() } stages { stage('Example') { steps { echo 'Hello World' } } } } ... View more

"stages{}.children{}.exec_node"=X where X is agent node name, where the node step got executed. It is added in jenkins plugin 1.7.1 released at Dec 7, 2018. If you have latest app, the "Build History" tab of agent will include the "stages{}.children{}.exec_node" info. the underlaying spl used is index=jenkins_statistics host="FQDN-OF-JENKIS-MASTER" event_tag=job_event ( node="JENKINS-AGENT-NAME" OR "stages{}.children{}.exec_node"="JENKINS-AGENT-NAME" )| dedup build_url sortby -_time ... View more

app for jenkins 1.0.8 changed wording slaves to nodes and updated the agent build history tab to include node step execution (require plugin 1.7.1), but unfortunately no change for "Build Distribution" stats ... View more