views:

24

answers:

0

Hi all,

In our application, we log critical information to log text files for later debugging purpose. With splunk its easy to identify a problem if I already have some data points like order number or "object reference not found" type of error. But its challending for me to get an overall picture of a problem using splunk. To be able to identify an actual problem in software, I have to read through possibly multiple log files or an entire log file to see what application was doing before the problem happened. Reading entire log file in a human fashion helps me to identify how application behaved with other data points before the actual problem happened. In other words its hard for me to see the "real root cause" for the error with splunk. What has been your experience out there in the field of software development.