Getting Data In

filtering process information

noliver
Engager

Hi,

I'm looking to get individual process performance data from Splunk, but only specific processes. (to reduce data)

What I have entered is:

[perfmon://Process]

index = main

object = Process

counters = Working Set - Private;Elapsed Time;% Processor Time;% UserTime

instances = process1;process2;process3

But it is still bringing back all process information for all processes. Does anyone know why its is not forwarding the data specified only?

Thanks

barbituate
Engager

I'm in the same boat. I'd like to have control over which process data is being gathered to conserve my license bandwidth. As it stands now, 10GB is being used by Perfmon :Process alone! I'm only interested in maybe 5 processes.

0 Karma

MuS
SplunkTrust
SplunkTrust

Hi noliver,

are you applying this props.conf on the universal forwarder or the indexer? It will not work on the forwarder, since it does not parse the data/events. You must apply it on the indexer or a heavy forwarder, they do data/event parsing.

Also, check that the name in the stanza is correct for this source type. Check the docs on route and filter data

hope this helps ...

cheers, MuS

0 Karma

mic1024
Path Finder

I think noliver is talking about the inputs.conf configuration rather than props.conf

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!

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...

Turn Cisco Telemetry Into Action with Cisco Data Fabric, powered by the Splunk ...

The surge in machine data is already hitting enterprise budgets, and the agentic era will only intensify it. ...

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