Quantcast
Channel: THWACK: Message List
Viewing all articles
Browse latest Browse all 20396

Re: hyper-v polling's side effects

$
0
0

Hi Balki 1429.

 

Here is my node. Hyper-V polling not yet enabled. "Edit Node" is there.

Screen Shot 2014-07-16 at 9.40.02 PM.png

 

I do "List Resources", select "Hyper-V", and end up on "Virtualization Summary -> Hyper-V Host Details" now instead of "Node Details":

Screen Shot 2014-07-16 at 9.48.20 PM.png

 

I don't see "Edit Node" here any more, and can't get to it from "find node":

 

Screen Shot 2014-07-16 at 9.49.56 PM.png

Clicking on the node in the view above gets me to the same "Hyper-V Node Details" view.

 

To sum up my experience thus far with enabling "Hyper-V Polling":

  1. Changes the default view of the node to "Hyper-V Node Details" as if Hyper-V was its only function now, rather than just a role. Unexpected and undesired behavior.
  2. Changes "machine type" as if... see (1), with unexpected and undesired results, such as breaking existing monitoring, logging and alerting - as it did in my case. That's potentially catastrophic if you unexpectedly lose alerts for something mission-critical just because you enabled a Hyper-V role and Hyper-V polling in Solarwinds.
  3. "List Resources", like "Edit Node" is no longer available in this view, i.e. one can't go back the same way one came. I enabled "Hyper-V polling" by using "List Resources", and now I have to dig into docs and google around to figure out how to disable it - as "List Resources" is nowhere to be found. This is unexpected, undesired and ... annoying, especially for someone new to SW (that'd be me).

Viewing all articles
Browse latest Browse all 20396

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>