About mcweens

mcweens · ‎07-09-2021

We ended up routing this data to the HF instead of it going straight to splunk cloud. We heard that the approval process for an app to get accepted is painful and also apparently Splunk Cloud doesn't want you having inputs on your search head anyways (it had been there for like 3 years though before they said anything). Thanks!

mcweens · ‎07-09-2021

Hello, we use the AWS AddOn for Splunk for all of our AWS Inputs. For a few months, after many years of this showing correctly, we no longer see data under this search: sourcetype=aws:config:notification configurationItem.resourceType = AWS::S3::Bucket The thing is, nothing changed other than updates to the AWS AddOn. AND we still get data under here for every resourceType that I can think of EXCEPT S3, so the AWS side configuration and the inputs I have to assume are set fine. sourcetype=aws:config:notification I have looked over this in every facet I can think possible and have had a support case open for a while now. Any thoughts or similar cases? Thanks!

mcweens · ‎05-08-2019

Note: I just noticed I also need to use this since we have Pipeline jobs: https://wiki.jenkins.io/display/JENKINS/Splunk+Plugin+for+Pipeline+Job+Support I need to have someone else install that and I will update this ticket when I get to try the addiontal plugin. I will note that for some reason the Connection Test is no longer working, the only change was Splunk Support making the HEC public facing.

Posts	6
Solutions	0
Karma Given	0
Karma Received	0
Member Since	‎12-12-2018

Online Status	Offline
Date Last Visited	‎12-06-2023 03:47 PM

awsAddOn sourcetype=aws:config:notification config...

Dropping Logs Sent Straight to Splunk Cloud

Jenkins to Splunk, Only Connection Test Success

Re: Dropping Logs Sent Straight to Splunk Cloud

awsAddOn sourcetype=aws:config:notification config...

Re: Jenkins to Splunk, Only Connection Test Succes...