Dashboards & Visualizations

Query with multiple values in cell

rangarbus
Path Finder

Hey friends, I am facing a problem with my new dashboard. 

My Event:

{ 
   kubernetes: { 
     container_name: adapter
     docker_id: a15db0337d70979f0f6e042f5bd609bfe1c42a97472faea56c77924c2ec43158
     namespace_name: default
     pod_name: adapter-767585d989-x5fj7
   }
   log: {"thread":"simpleMessageListenerContainer-2","level":"INFO","loggerName":"adapter.repository.S3Repository","message":"Getting s3object bucket=adapter-test, key=in/1234.json","endOfBatch":true,"loggerFqcn":"org.apache.logging.slf4j.Log4jLogger","instant":{"epochSecond":1615350586,"nanoOfSecond":904000000},"threadId":14,"threadPriority":5,"app_name":"adapter"}

   log_processed: { 
     app_name: adapter
     endOfBatch: true
     instant: { 
     	epochSecond: 1615350586
     	nanoOfSecond: 904000000
     }
     level: INFO
     loggerFqcn: org.apache.logging.slf4j.Log4jLogger
     loggerName: adapter.repository.S3Repository
     message: Getting s3object bucket=adapter-test, key=in/1234.json
     thread: simpleMessageListenerContainer-2
     threadId: 14
     threadPriority: 5
   }
   stream: stdout
   time: 2021-03-10T04:29:46.90639262Z
}

When i create a dashboard out of this event, I get 2 entries on each cell of the dashboard.

My dashboard query is as below

index=logs sourcetype=test
| rename log_processed.app_name as AppName
| rename log_processed.loggerName as LoggerName
| rename log_processed.level as LogLevel
| rename log_processed.message as Message
| rename kubernetes.pod_name as EKS_POD
| table _time, AppName, LoggerName, LogLevel, Message, EKS_POD
| where Message!=""

Output is like:

rangarbus_0-1615395376727.png

Ideally the output should be :

rangarbus_1-1615395567660.png

Could you please help on this. 

 

Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust
| foreach * [ eval <<FIELD>>=mvdedup('<<FIELD>>') ]
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Does the props.conf file contain both KV_MODE=JSON and AUTO_KV_JSON=true?  If so, that's why the fields are doubled.

---
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 ...

Build resilience for the agentic era: Join us at Splunk Go San Jose

AI is changing how organizations build, operate, and secure digital services. As teams adopt AI agents and ...

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...