Monitoring Splunk

How is the Distributed Management Console Physical Memory Usage(%) value calculated?

adamblock2
Path Finder

We are currently running a distributed Splunk 6.2.3 infrastructure with multiple indexers.

According to the Distributed Management Console Resource Usage, each indexer shows "Physical Memory Usage(%)" as being > 96.5%.

I ran the command free -htlw on one of the indexers, and received the following results:

         total    used     free    shared    buffers    cache    available
Mem:     188G     2.1G     5.6G    24M       215M       180G     186G
Low:     188G     183G     5.6G
High:    0B       0B       0B
Swap:    4.0G     3.6M     4.0G
Total:   192G     2.1G     9.6G

Based on this information, I question the authenticity of that which is being reported by the Distributed Management Console. If someone could clarify exactly how these values differ, it would be greatly appreciated.

Thank you.

0 Karma
1 Solution

hexx
Splunk Employee
Splunk Employee

Up until Splunk Enterprise 6.2.5 included, the platform instrumentation records that the DMC leverages for its views have reported system-wide physical memory usage by including OS buffers & cache.

This did not yield a value that was representative of the physical memory actually available on the system, which is why starting with Splunk Enterprise 6.2.6, platform instrumentation reports system-wide physical memory usage without including OS buffers & cache.

Therefore, our recommendation is to upgrade all instances monitored by the DMC to 6.2.6 or later.

Please see this Splunk Answer for full details.

View solution in original post

hexx
Splunk Employee
Splunk Employee

Up until Splunk Enterprise 6.2.5 included, the platform instrumentation records that the DMC leverages for its views have reported system-wide physical memory usage by including OS buffers & cache.

This did not yield a value that was representative of the physical memory actually available on the system, which is why starting with Splunk Enterprise 6.2.6, platform instrumentation reports system-wide physical memory usage without including OS buffers & cache.

Therefore, our recommendation is to upgrade all instances monitored by the DMC to 6.2.6 or later.

Please see this Splunk Answer for full details.

Get Updates on the Splunk Community!

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...

Application management with Targeted Application Install for Victoria Experience

Experience a new era of flexibility in managing your Splunk Cloud Platform apps! With Targeted Application ...