nerengm ✭✭✭✭✭

@"tdanner" that is a very helpful explanation for IsRelative. Where would someone find that important detail other than in this Thwack post? Where is that sort of thing fully documented?

Same here. If someone at Solarwinds goes to the trouble of building these checks into the diagnostics, take the extra time to spell out the condition that lead to a failure/warning. If it were a port restriction as alterego suggests, the result description should say "Target xx does not respond on port xx." If the…

This link no longer works. Can you repost the equivalent please?

Ah ha, that explanation makes perfect sense. It has a parent and the parent is Down. Thank you very much!

@"aLTeReGo" can you point me to an updated article citing support for TDE? This link no longer works.

Oh, good point. I was only thinking about myself again...

Ah yes, I can see how that would be done in Atlas. Can IP SLAs and their metrics be added to Orion Maps?

Wow, that worked. I've never seen double single quotes before. You learn something new everyday.

I'm on 2018.2, thus no enhanced node status. The two different statuses sound very redundant. Doesn't DOWN mean its unreachable??

I'd love some clarification on how to do this. I've done a pure SQL AVG on all the PercentAvailability entries in the ContainerStatus table, and its not the same value that the Data Aggregator: Average generates in a report.

Yeah, I've experienced the same thing with the account / password used on the report schedule. In my case I've tried every type of account type and the results are always the same. The whole process seems bizarre...why does a server generated report need an account specified at all??

Can you elaborate on the bit about migrating community platforms? Is this going to be another big effort like the last one?

Same here...my Controls folder has only file in it....ChartImagePipe.aspx. Version 2020.2

Nope, I've just gotten use to extra warnings...

We just upgraded to version 2020.2 HF1 a few weeks ago. I opened a case and it was suggested that are some known issues like this and NTA 2020.2.1 HF 1 will fix it. I wasn't planning on another upgrade so soon, so I have not tried it yet.

Was this fixed in HF5?

Ugh...the curly brackets are what I was missing...thank you very much.

Did anything ever come of this?

I know its been 8 years but...did you ever figure out how to do this in Atlas or Orion Maps?

How can we verify we've been awarded points correctly? Like @"mdhtbm" asked.

Seems like a reasonable request to me @"gkjono" . I've been wondering the same thing, but ...

@"mrxinu" ever make any progress on this?

Did you figure this out? I'm looking for the same thing.

Same issue going from 12.3 to 2019.4...any advice on how to move past this error?

Ditto!

Same here...did you make any progress on this?

Whats the equivalent way to get existing CLI credentials used for IP SLA operations???

This is cool and interesting, but doesn't the platform details page show you the same thing without having to modify code?

I'm interested in this as well. Any hints?