Monitoring Splunk

Universal Forwader - Cap CPU, memory, Disk usage

nhurtaud
Explorer

Hi everyone,
Thank you for your time. My question is sample:
is it possible to cap this three parameters:
- CPU
- RAM
- DISK
On a Universal Forwarder, installed like a agent for monitoring file and fschange. I think that UF don't write on Disk, just on RAM. is it true ?
I know that is possible to cap bitrate in output.conf and EventQueue, but for CPU and RAM footprinting of process itself, not Queue ?

Thank you and have a nice day.
Nicolas.

Tags (3)
0 Karma

jtrucks
Splunk Employee
Splunk Employee

This must be accomplished outside the Splunk application(s). Use OS level controls, so as ulimit settings on *Nix systems, or things like Cgroups in RHEL based systems.

--
Jesse Trucks
Minister of Magic

nhurtaud
Explorer

OK.
Thank you for your answer.
But, I regret not having the opportunity to cap CPU and RAM footprint.
Customers are worried.
Is it possible to gives some ideas for roadmap ?

Nicolas.

kranzrm
Path Finder

I second this. Worries are abound. We just had a DNS server crash and splunk-regmon was using almost 4GB of virtual memory.....

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!

Laser Bananas and Edge Hubs: Exploring Operational Technology (OT) Data Through a ...

  OT is a different environment to traditional IT and can have interesting challenges when interfacing the ...

Event Series: Mastering AI Tokenomics and Splunk Agent Observability

Beyond the Black Box: Correlating AI Performance and Tokenomics with Splunk Agent Observability   As ...

span_metrics: The OpenTelemetry-Idiomatic Way to See Inside Your Services

You open a trace in Splunk Observability Cloud and everything looks fine. One root span, order-pipeline, with ...