All Apps and Add-ons

Best practice to centralize rails logs

cutmedia
Engager

Hi All,

I would like to know what is the best way to centralize rails productions logs across multiple server. So far I have gathered:

  1. Simply monitoring log/production.log. - Physically works, but it get all the fields wrong.
  2. Rails app - This works great when I can point it to a local log/production.log.

I'm using a universal forwarder to send the current production.log to the indexing server, but without properly understanding of the fields of the logs it gets all the data wrong.

What would you suggest to use to get data from universal forwarders into a readable format?

Thanks!
Justin

1 Solution

mikelanghorst
Motivator

Use #1, you can control how field extractions occur. What sourcetype is being detected for your input? You may need to override it either in inputs.conf or props.conf on the forwarder. Then setup your own field extractions either with the UI or directly in props.conf doc here

View solution in original post

mikelanghorst
Motivator

Use #1, you can control how field extractions occur. What sourcetype is being detected for your input? You may need to override it either in inputs.conf or props.conf on the forwarder. Then setup your own field extractions either with the UI or directly in props.conf doc here

Get Updates on the Splunk Community!

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...

Splunk App Dev Community Updates – What’s New and What’s Next

Welcome to your go-to roundup of everything happening in the Splunk App Dev Community! Whether you're building ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...