Splunk Search

How to split a GC log using eval funciton?

aqaadi
Engager

Below is the sample GC log.
Could someone let me know how to split it using eval function?

2019-09-11T02:27:50.180-0400: 660007.803: [GC (Allocation Failure) [PSYoungGen: 21216K->224K(20992K)] 30129K->9137K(34816K), 0.0041367 secs] [Times: user=0.01 sys=0.00, real=0.01 secs]
2019-09-11T03:07:20.083-0400: 662377.706: [GC (Allocation Failure) [PSYoungGen: 20704K->288K(20992K)] 29617K->9201K(34816K), 0.0021393 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
2019-09-11T03:45:50.519-0400: 664688.142: [GC (Allocation Failure) [PSYoungGen: 20256K->288K(19968K)] 29169K->9201K(33792K), 0.0019324 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
2019-09-11T04:22:34.994-0400: 666892.617: [GC (Allocation Failure) [PSYoungGen: 19744K->224K(19968K)] 28657K->9137K(33792K), 0.0020489 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2019-09-11T04:58:40.467-0400: 669058.091: [GC (Allocation Failure) [PSYoungGen: 19168K->256K(18944K)] 28081K->9169K(32768K), 0.0022131 secs] [Times: user=0.01 sys=0.00, real=0.00 secs]
2019-09-11T05:34:08.080-0400: 671185.704: [GC (Allocation Failure) [PSYoungGen: 18688K->256K(18944K)] 27601K->9169K(32768K), 0.0023361 secs] [Times: user=0.00 sys=0.00, real=0.01 secs]
2019-09-11T06:08:40.817-0400: 673258.440: [GC (Allocation Failure) [PSYoungGen: 18176K->224K(17920K)] 27089K->9137K(31744K), 0.0016236 secs] [Times: user=0.00 sys=0.00, real=0.00 secs]
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Rather than tell us how to solve your problem, why not tell us the problem you need to solve and we'll suggest ways to do it? What result are you trying to get? Why do you have to use eval?

---
If this reply helps you, Karma would be appreciated.
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Catalog Is Now Generally Available on Splunk Cloud Platform

A Unified View of Your Data  Security logs, application events, business data, and historical telemetry often ...

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner

Your Path to AgenticOps: AI Experiences for Every Splunk Practitioner   Watch on demand us for a demo-driven ...