All Apps and Add-ons

Some events in splunk do not correspond to Jenkins Console output.

schilds427
Explorer

Hey folks,

I suspect this is more of a Jenkins problem than a Splunk problem, but I figured I'd ask here anyway. Our Jenkins instances have the 'Splunk App for Jenkins' installed and set to send all console output from all jobs to Splunk on the "text::jenkins" sourcetype. Recently though I've noticed that there seem to be more events in Splunk than there should be. For example if I do a search to look for a specific job's console output , like

index=jenkins_console sourcetype="text:jenkins" earliest=-5d@d latest=now source=source_of_job_I_Want | stats values(_raw) by _time

I see: 

From Splunk queryFrom Splunk query

 

But if I go directly to Jenkins and look at the console output for this job I see: From Jenkins ConsoleFrom Jenkins Console

This is an issue because we have an alert for the "Cannot contact X: java.lang.InterruptedException" String to help detect agent failures, but it's confusing when that alert goes off but then we look at the console and don't see that message. 

Anyone come across anything similar? 

Labels (3)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Is the possible the message was generated by the TA rather than by Jenkins?

---
If this reply helps you, Karma would be appreciated.

schilds427
Explorer

Like from the 'Splunk for Jenkins' plugin? I don't think so. Looking at the configuration for the plugin it appears to be pretty much the default settings: config_1_LI.jpgconfig_2.PNGconfig_3.PNG

0 Karma
Get Updates on the Splunk Community!

SOC4Kafka - New Kafka Connector Powered by OpenTelemetry

The new SOC4Kafka connector, built on OpenTelemetry, enables the collection of Kafka messages and forwards ...

Your Voice Matters! Help Us Shape the New Splunk Lantern Experience

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Building Momentum: Splunk Developer Program at .conf25

At Splunk, developers are at the heart of innovation. That’s why this year at .conf25, we officially launched ...