About anortrup_splunk

anortrup_splunk · ‎10-31-2019

For clarity, this question does not pertain to Splunk Investigate.

anortrup_splunk · ‎07-24-2017

Updated answer This is no longer an issue in the latest version of Go. crypto/tls now supports the ECDH-ECDSA-AES256-GCM-SHA384 certificates used by Splunk Cloud trial's HTTP event collector. I've tested this using this library which provides an io.Writer that writes to HTTP event collector.

anortrup_splunk · ‎05-24-2017

@Dnguyen Customers should avoid using logos that are similar to the Splunk logos including the splunk chevron. These are copyrighted items and should only be used by Splunk. Additionally apps built by 3rd parties should not have names starting with Splunk. For example "Splunk app for Awesome" is inappropriate, but "Awesome app for Splunk" is OK.

anortrup_splunk · ‎03-07-2017

@helge We target *nix systems for these standards because the overwhelming majority of installations for Splunk are on *nix and we are looking to follow best practices in that environment.

anortrup_splunk · ‎07-12-2016

I know that this is old, but wanted to give a clear answer. This means that your app has been packaged with the local directory and now your setup.xml is trying to overwrite existing configurations. I recommend removing the local directory from the app (or ignoring it when packaging with tar) then reinstalling (including removing the old copy of the app). Then when you go to setup the app a new local directory will be created and local configurations will be written there.

Posts	5
Solutions	1
Karma Given	25
Karma Received	3
Member Since	‎05-16-2016

Online Status	Offline
Date Last Visited	‎06-05-2020 02:04 AM

Re: Splunk Telecommunication App to ingest RADIUS ...

Re: HTTP Event Collector: How to troubleshoot why ...

Re: What does "Check that use of the Splunk logo a...

Re: Why is Splunk AppInspect failing with error "F...

Re: error while trying to update: In handler 'loca...