All Apps and Add-ons

cpu.sh diffent log format

stenbryggen
New Member

cpu.sh logs are different from universalforwarder then splunk installations.

Splunk is adding a line for all and each cpu, but the universalforwarder is adding everything in one log entry. And the "Hosts" dashboard can't understand the combined logs from the universalforwarder.

What can I do to fix this issue?

0 Karma

araitz
Splunk Employee
Splunk Employee

I'm not sure I understand. We use the universal forwarder to run the *nix TA, and there is fundamentaly no difference between the output from UF and from our indexers. My guess is that you don't have the TA installed on the search head, which is required so that muliti kv mode is enabled by default. See a similar issue here:

http://answers.splunk.com/answers/129893/splunk-app-for-unix-homemetrics-empty

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!

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...

Manage Datasets and Connections in Catalog on Splunk Cloud Platform

Set Up Data Where You Use It Catalog already helps teams find and understand data across Splunk indexes, ...

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