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!

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas

Watch Now Painting a Clearer Picture: Creating Cross-Domain Visibility with AI Canvas     Do you ever feel ...