topic Re: What's the best way to parse GC logs? in Getting Data In

What's the best way to parse GC logs?

ddrillic — Wed, 06 Mar 2019 20:16:01 GMT

We would like Splunk to automatically parse our GC logs and we found a wiki link on configuring props.conf to do so at Community:Monitoring JVMs
HOWTO: Index your JVM garbage collection data

Should we do it at index time or search time?

Re: What's the best way to parse GC logs?

somesoni2 — Wed, 06 Mar 2019 20:49:30 GMT

From that link

On Indexers (or heavy forwarders)
props.conf

[sun_jvm]
AUTO_LINEMERGE=FALSE
SHOULD_LINEMERGE=TRUE
DATETIME_CONFIG=CURRENT
BREAK_ONLY_BEFORE=\d+\.\d+:

On search heads
props.conf

[sun_jvm]
REPORT-jvm = sun_jvm_gc

transforms.conf

[sun_jvm_gc]
REGEX = \[(Full\s)?GC\s(?<JVM_HeapUsedBeforeGC>\d+)K->(?<JVM_HeapUsedAfterGC>\d+)K\((?<JVM_HeapSize>\d+)K\),\s(?<JVM_GCTimeTaken>\d+.\d+)\ssecs\]

Re: What's the best way to parse GC logs?

ddrillic — Wed, 06 Mar 2019 21:53:49 GMT

Gorgeous @somesoni2 - you know, our sales engineer says - Always at search time - what do you think?

Re: What's the best way to parse GC logs?

somesoni2 — Wed, 06 Mar 2019 22:02:00 GMT

He must be talking about field extractions which are recommended during search-time. Above config does exactly that.

There are cases where we do index-time field extractions, e.g. for data which we want to use data model acceleration or want to use the fields in tstats. They occupy space on indexers (and will be replicated in case of indexer clusters) and will cause slightly slowness in indexing process, hence they should be avoided unless you're OK with that impact.

Re: What's the best way to parse GC logs?

ddrillic — Wed, 06 Mar 2019 22:09:36 GMT

Gorgeous @somesoni2 !!!