Knowledge Management

How to avoid duplicate fields in CIM Data Normalization?

Atchyuth_P
Path Finder

Hi Team,

I am using field aliases as in my sourcetype i have two common fields (dest & dest_ip) which have same values.
When i applied field aliases both were reflecting.

Atchyuth_P_0-1676313476036.png

Atchyuth_P_1-1676313720897.png

How to avoid duplicate fields

Kindly help in this scenario

Labels (2)
Tags (1)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

Having two aliases for the same field will result in 3 fields (the original plus 2 aliases) with the same data.  That may be necessary for some use cases, which means you have to live with it.  Fortunately, aliases are search-time operations so no storage is consumed.  If you don't have a need for multiple aliases for the same data then remove one of them.

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