DMC not displaying server metrics

[tlmayes]

On our Monitoring Console on the "Overview", it does not display any metrics under "Resource Usage" for each of the categories "Indexers", "Search Heads", etc.  Not the browser, have tried from different computers, same problem.  No WARN or ERROR messages on the host, no errors in the "Setup" page, and CPU/RAM utilization is extremely low.

Anybody else experienced this?

[tlmayes · Accepted solution]

Splunk says that it is an "as yet published" "known issue" since v9.1.0.  They will not classify it as a "bug" until they can verify.  How can it be classified as a known issue, and simultaneously not verified? 

[gcusello]

Hi @tlmayes,

bug and known issues are synonyms.

doe Splunk Support give an indication about when the known issue will be solved?

Anyway, let me know if I can help you more.

Ciao.

Giuseppe

P.S.: Karma Points are appreciated 😉

[gcusello]

Hi @tlmayes,

at first: did youconfigured yur DMC to take logs from the other servers?

To do this you have to connect the DMC to all the server to monitor on the 8089 port as a Search Head in Distributed Search.

Then, have you the message "N.A." or what else?

if you have "N.A.", are you using the last Splunk version (9.1.2)? because the previous version had a bug.

Ciao.

Giuseppe

[tlmayes]

@gcusello , appreciate the response.  
Yes, this is a DMC that has been operational for ~ 3years, and suddenly started doing this.  All sources are connected without error.  I even removed a few and added back to see what happened.  No immediate change.  The interface works..... some of the time, about 20% but cannot figure out why it suddenly works, and without any change, refresh the screen and it is broken AGAIN.  

I did update as soon as 9.1.2 appeared hoping that would fix it (updated the entire architecture).  No luck, still broken

About to the point what I am simply going to delete it, and start over

[gcusello]

Hi @tlmayes,

before restarting, open a case to Splunk Support, sending them a diag.

Ciao.

Giuseppe

[tlmayes]

Splunk support responded that this was a known, as yet published, bug in the software.  Was hoping 9.2 release fixed this but sadly it did not