Ingesting Static Files (.ini's)

Is anyone out there ingesting static .ini files with sumo logic? If not, does anyone think this is an unreasonable use of the tool?

One of the things we're attempting to use sumo logic for,is so that our customer care team can have easy access to log files. Additionally, they frequently require to know what some of our applications .ini files contain.

The innate nature of the .ini is that they are largely static. Ingesting an .ini file that does then change for the period of our retention period means we lose that data.

What I'd like to do is schedule via cron a script to ingest the contents of an .ini file.

Unfortunately, I'm not sure where to begin past the point of setting up a scripted source with a cron frequency to resolve this.

Does anyone have any suggestions, opinions, or comments?

Kevin Keech

November 22, 2014 18:32

Hi Aaron,

My suggestion would be to set up a Hosted Collector with an HTTP source configured. You can then create a cron job on the host that sends the .ini file to the HTTP source periodically via a simple Curl command.

Uploading_Files_to_an_HTTP_Source

Aaron Jayjack

January 16, 2015 20:48

Solved this with a script source. script: type <config file location>

Ingesting Static Files (.ini's)

Comments

Didn't find what you were looking for?