Join the Conversation
- Find Answers
- :
- Splunk Administration
- :
- Getting Data In
- :
- Reduce license usage for performance data from Add...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
i already did some research but seems our case is a bit special:
We colllect inventory and performance data from our vCenters with the Add-On for VMware (Splunk_TA_vmware) in version 4.0.2. The heavy forwarder running this TA is also the DCN.
I am not able to restrict data collection of performance data with the given options.
The interval can be set to higher or lower value but the data gathered from the worker is still the same. It collects all since the last input.
Due to the fact, that we dont need performance data every 20 seconds - i would prefer an 1 hour average event . Or if not possible 1 Events per 30 minutes with the latest values.
Is there a way to achieve this? Doesn't matter if it is by design or splunk workaround.
Example raw data:
vm-44 500c714d-861b-2f53-1f7f-16d8e72c4e28 aggregated 20 0.04 0.04 2.79 2.73 389 410
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A transforms INGEST_EVAL did the magic.
INGEST_EVAL = queue=if(match(_raw, "vm-") AND (random()%100)!=0, "nullQueue", "indexQueue")
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A transforms INGEST_EVAL did the magic.
INGEST_EVAL = queue=if(match(_raw, "vm-") AND (random()%100)!=0, "nullQueue", "indexQueue")
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Persistent Queue at TcpOut — One of Splunk's Most Practical Features
Build resilience for the agentic era: Join us at Splunk Go San Jose
Manage Edge Processor pipelines end to end with APIs
