Knowledge Management

for a data set with a common request ID but data is scattered in different rows but want to get in 1 line for and just 1 row

varunawasthi9
New Member

I have a data like I am searching with a request ID

and I get below data like
time 1: request id=1 account details and elapsed time
time 2 request id=1 account codes
time 3 request id= 1 viewname and view 2
time 1: request id=2 account details and elapsed time
time 2 request id=2 account codes
time 3 request id=2 viewname and view2

I want like the below

request id accountdetails accountcd viewname view2
1 abc abc_cd skyview earthview
2 xyz xyz_cd sky1view earthview1

can you please help how can i achive this , thanks in advance

Tags (1)
0 Karma

somesoni2
Revered Legend

Give this a try (adjust the field name per yours)

your base search fetching all 3 type of events
| stats values(account_details) as account_details values(accountcd) as accountcd values(viewname) as viewname values(view2) as view2 by request_id
0 Karma

varunawasthi9
New Member

also in above the account details contain more than 1 account details for which need those in it like all ones

0 Karma

somesoni2
Revered Legend

Could you explain this with an example? (what you're getting right now and what you want)

0 Karma

varunawasthi9
New Member

what to do for date if I want to get along with above columns

0 Karma

somesoni2
Revered Legend

Based on which time you want, you can include max(_time) as _time OR min(_time) as _time in the stats.

0 Karma
Get Updates on the Splunk Community!

Get Early Access to AI Playbook Authoring: Apply for the Alpha Private Preview ...

Passionate about security automation? Apply now to our AI Playbook Authoring Alpha private preview ...

Reduce and Transform Your Firewall Data with Splunk Data Management

Managing high-volume firewall data has always been a challenge. Noisy events and verbose traffic logs often ...

Automatic Discovery Part 1: What is Automatic Discovery in Splunk Observability Cloud ...

If you’ve ever deployed a new database cluster, spun up a caching layer, or added a load balancer, you know it ...