https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334540#M164409 <P>the pipeline itself (groovy code of Jenkinsfile) is always ran on master, the node step and steps inside node closure can run on agent nodes. plugin 1.7.1 version added exec_node info to track the node step execution info </P> <PRE><CODE>index=jenkins_statistics "stages{}.children{}.exec_node"=X </CODE></PRE> Wed, 19 Dec 2018 15:59:06 GMT txiao_splunk 2018-12-19T15:59:06Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334537#M164406 <P>I am using jenkins's splunk plugin version 1.6.3(latest). I have configured no executor in master, so no possibility for jobs to build in master. Have only one node configured and jobs needs to be running in that node only. From console log, i can see its running in slave node, but in splunk index, i could see its node value is master.<BR /> This case is only for pipeline jobs, but not for freestyle jobs.</P> Tue, 12 Dec 2017 07:59:43 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334537#M164406 rakesh635 2017-12-12T07:59:43Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334538#M164407 <P>Did you get anywhere with this? We are experiencing the same issue and trying to integrate splunk with our pipeline builds?</P> Fri, 21 Sep 2018 11:44:50 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334538#M164407 philsegal 2018-09-21T11:44:50Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334539#M164408 <P>we are having exactly the same issue where pipeline builds are accredited to the master despite running on multiple slaves. basically when I go to the "Jenkins slaves" section and look at Build Distribution across Slaves, all builds appear as running on the master which is not correct.<BR /> @txiao_splunk do you have any suggestions?</P> Wed, 19 Dec 2018 14:07:20 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334539#M164408 neluvasilica 2018-12-19T14:07:20Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334540#M164409 <P>the pipeline itself (groovy code of Jenkinsfile) is always ran on master, the node step and steps inside node closure can run on agent nodes. plugin 1.7.1 version added exec_node info to track the node step execution info </P> <PRE><CODE>index=jenkins_statistics "stages{}.children{}.exec_node"=X </CODE></PRE> Wed, 19 Dec 2018 15:59:06 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334540#M164409 txiao_splunk 2018-12-19T15:59:06Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334541#M164410 <P>app for jenkins 1.0.8 changed wording slaves to nodes and updated the agent build history tab to include <CODE>node step</CODE> execution (require plugin 1.7.1), but unfortunately no change for "Build Distribution" stats</P> Wed, 19 Dec 2018 16:14:15 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334541#M164410 txiao_splunk 2018-12-19T16:14:15Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334542#M164411 <P>agree with the fact that pipeline is run on master but, as we mentioned, we are interested in information about node steps execution information as well. reason for this is we want to find out if our Jenkins agents are being over/under-utilized and I didn't seem to find a way of displaying that information in the Splunk app for the pipeline builds.<BR /> silly question, the X in your query should be replaced by the master's hostname? are there quotes required?<BR /> just ran the query for one of the hosts and no results unfortunately.</P> Wed, 19 Dec 2018 16:58:32 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334542#M164411 neluvasilica 2018-12-19T16:58:32Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334543#M164412 <P>"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.<BR /> If you have latest app, the "Build History" tab of agent will include the "stages{}.children{}.exec_node" info. the underlaying spl used is </P> <PRE><CODE>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 </CODE></PRE> Tue, 29 Sep 2020 22:26:42 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334543#M164412 txiao_splunk 2020-09-29T22:26:42Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334544#M164413 <P>thank you, the spl works. is there a way of displaying the "number of builds" across multiple nodes/slaves over a specific period of time when using pipelines? something similar to visualizing "Build Distribution across Slaves" when for non-pipeline builds?<BR /> this would be very helpful in identifying if the number of nodes is over or under provisioned.<BR /> in other words, the "build history" in v1.7.1 is fine for individual nodes but is there a way of visualizing the builds history for all nodes connected to a pipelined master?</P> Tue, 15 Jan 2019 09:06:45 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334544#M164413 neluvasilica 2019-01-15T09:06:45Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334545#M164414 <P>@txiao_splunk are you aware of a way of achieving what I have described in my last comment? can I achieve this via a custom dashboard?</P> Mon, 28 Jan 2019 16:40:25 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334545#M164414 neluvasilica 2019-01-28T16:40:25Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334546#M164415 <P>of course you can use custom dashboard, you could try run the sample spl</P> <PRE><CODE> 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 </CODE></PRE> <P>Then "Save as Report". You can also create a custom dashboard with node filter and time filter, please checkout the free book <A href="https://www.splunk.com/goto/book">https://www.splunk.com/goto/book</A> and dashboard doc <A href="https://docs.splunk.com/Documentation/Splunk/7.2.3/Viz/WebFramework">https://docs.splunk.com/Documentation/Splunk/7.2.3/Viz/WebFramework</A></P> Tue, 29 Jan 2019 05:32:01 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334546#M164415 txiao_splunk 2019-01-29T05:32:01Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334547#M164416 <P>thank you. that is very useful. So in my syntax:</P> <PRE><CODE> index=jenkins_statistics host="FQDN-OF-JENKINS_MASTER" event_tag=job_event | rename "stages{}.children{}.exec_node" as exec_node | eval build_on_node=coalesce(exec_node, node) | chart count by build_on_node useother=f | sort -count </CODE></PRE> <P>I can see my jenkins slaves and the "count". However I am not too sure what "count"represents in this case. The number is quite high. For instance there are 60 events and 19420 for "count".Is there a way to display the number of builds in the count field instead of that high number which I am not sure what it represents?<BR /> appreciate your help.</P> Tue, 29 Jan 2019 14:57:33 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334547#M164416 neluvasilica 2019-01-29T14:57:33Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334548#M164417 <P>I think it counted pipeline steps, maybe we can try mvdedup, e.g.</P> <PRE><CODE>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 </CODE></PRE> Tue, 29 Jan 2019 15:24:30 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334548#M164417 txiao_splunk 2019-01-29T15:24:30Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334549#M164418 <P><a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/192618">@txiao_splunk</a> I have a strange case where for a Jenkins master stages are still attributed to the master instead of the slaves they are running on. Version of Jenkins and Splunk plugins(including the Extension plugin) are exactly the same on 10 masters, 9 of them correctly attribute the stages to the nodes they're running on but one doesn't. The builds structure is more or less the same so I don't think that can be the issue. The build's console definitely has entries like: Running on "hostname bla" but when I check splunk, stages{}.children{}.exec_node is always attributed to the master. Any idea of what can be wrong?</P> Wed, 30 Sep 2020 03:29:47 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334549#M164418 neluvasilica 2020-09-30T03:29:47Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334550#M164419 <P>Could you kindly check pipline related plugins (such as workflow-job, workflow-support) versions to make sure they are consistent with other masters</P> Tue, 31 Dec 2019 03:48:58 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334550#M164419 txiao_splunk 2019-12-31T03:48:58Z https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334551#M164420 <P>workflow related plugins(workflow-job, support, cps) seem to be exactly the same on all masters. <BR /> workflow-job:<BR /> Plugin-Version: 2.35<BR /> Hudson-Version: 2.138.4<BR /> Jenkins-Version: 2.138.4<BR /> Plugin-Dependencies: workflow-api:2.36,workflow-step-api:2.20,workflow<BR /> -support:3.3<BR /> workflow-cps:<BR /> Plugin-Version: 2.74<BR /> Hudson-Version: 2.138.4<BR /> Jenkins-Version: 2.138.4<BR /> Plugin-Dependencies: workflow-api:2.36,workflow-scm-step:2.4,workflow-<BR /> step-api:2.20,workflow-support:3.3,scm-api:2.2.6,script-security:1.62<BR /> ,structs:1.20,support-core:2.43;resolution:=optional,ace-editor:1.0.1<BR /> ,jquery-detached:1.2.1</P> Tue, 31 Dec 2019 12:04:13 GMT https://community.splunk.com/t5/Splunk-Search/Splunk-fetching-node-as-jenkins-master-instead-of-actual-slave/m-p/334551#M164420 neluvasilica 2019-12-31T12:04:13Z