Splunk AppDynamics

Machine Agent - Missing Hardware Resources CPU Metrics (User,System and IOWait)

CommunityUser
Splunk Employee
Splunk Employee

I have an issue with some missing Hardware Resources metrics.

Step 1.- Machine Agent is up and running. Also /HardwareMonitor/linux-stat.sh
Step 2.- I validated below info:
JavaHardwareMonitor is <enabled>false</enabled> and HardwareMonitor <enabled>true</enabled>
Step 3.- I checked the logs and didn't see any ERROR message


The Issue:
Missing metrics from Metric Browser:
...|Hardware Resources|CPU|User   - missing
...|Hardware Resources|CPU|System  - missing
...|Hardware Resources|CPU|IOWait - missing

and below metrics are reporting fine:
...|Hardware Resources|CPU|%Busy  - OK
...|Hardware Resources|CPU|%Idle    - OK

Does someone knows about this issue? 

Labels (1)
0 Karma
1 Solution

CommunityUser
Splunk Employee
Splunk Employee

I just found that below metrics are provided when the Server Visibility is enabled on Machine Agent and must have a Server Visibility license.

...|Hardware Resources|CPU|User   - missing
...|Hardware Resources|CPU|System  - missing
...|Hardware Resources|CPU|IOWait - missing

View solution in original post

CommunityUser
Splunk Employee
Splunk Employee

I just found that below metrics are provided when the Server Visibility is enabled on Machine Agent and must have a Server Visibility license.

...|Hardware Resources|CPU|User   - missing
...|Hardware Resources|CPU|System  - missing
...|Hardware Resources|CPU|IOWait - missing

Atyuha_Pal
Contributor

Hi Juan,

Can we have the machine agent log in debug mode.

Steps to enable debug mode

Goto <machineagent-install-dir>/conf/logging/log4j.xml and change level value to debug from info as show below

Look for

<logger name="com.singularity" additivity="false">

      <level value="info"/>

     <appender-ref ref="FileAppender"/>

</logger>

and change info to debug as show below

<logger name="com.singularity" additivity="false">

      <level value="debug"/>

     <appender-ref ref="FileAppender"/>

</logger>

run it for 10 - 15 min and attach the logs

 

Thanks,

Atyuha

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!

From Data to Insight: Announcing the Winners of the Splunk Dashboard Contest

Hi Splunkers, First off, thank you to everyone who participated in our very first From Data to Insight: The ...

Splunk Developers: Construct Your Future at the .conf26 Builder Bar

Calling all Splunk architects, platform admins, and app developers: the site is open, and the blueprints are ...

Quick connection discovery mode for forwarders

When a Splunk forwarder loses connectivity to its indexers, it does not always reconnect immediately. In many ...