nerengm ✭✭✭✭✭

Thanks jvb...any chance you could get someone to add a wireless heat map to the demo site? I'd like to see an example without having to upgrade just to see it. I would create one in demo, but its not allowed.

What's the expected cadence to get this demo site upgraded: SolarWinds Hybrid Cloud Observability Demo | SolarWinds Demo - Summary Home - Summary Home ? Its now 2 major versions behind. I'd like to see this always on the latest version to quickly check out new features.

Thanks for the write up @"wluther", that makes me feel more confident moving forward with my upgrade next week. But I'm still worried I'll have your same experience and need a support case to actually get through it. I've had the same experience multiple times where opening a case and they do a tweak to the database is the…

done

So obvious its shouldn't need to be requested...

Then why isn't the feature request closed?

I upgraded my small dev environment yesterday and it was pretty smooth. The only issue was having to rebuild the website and re-run the config wizard about 4 times. This seems to be the case with every upgrade. Is that just me?

Can someone explain what drives the size and shape of the circles in wireless heat map? I'm just experimenting here with two access points (no clients). One access point appear to have a greater reach or signal strength than the other. But when I explore the details of an access point, there is no data or metric on the…

What is an Intelligent Map?? Is that the same as an Orion Map?

Meant to add that I spoke to Cheryl Nomanson about this in her office hours today, and she suggested that I pose the question here. @"cheryl1" 

This link doesn't work: "...outlining the differentiators on the Observability products to help everyone"

Same...I answered the first question 5 times before giving up.

tlally May I ask why level of support you have? When I open cases, my experience is rarely what I would call excellent.

Same problem here @"NetworkChunk" . What did you end up doing? I'm on 2023.3.1.

What do you say to that @"KMSigma.SWI" ? Is it true that there are publicized known bugs and internal only known bugs??

I'd be careful with the "always listed in the release notes." I've submitted more than one case only to be told that its a known bug and find that it is NOT in the release notes. I agree with the sentiment and it should work that way. But whomever oversees the process of documenting bugs could do a lot better.

I know...but I thought I was the only one that noticed. What's up with that? SolarWinds should divert some of the resources they dump into silly things like "Missions" toward improving their documentation.

Weird...they didn't mention deprecating verbs in the release notes?

First the nodes have to be NPM monitored. Then from the VNQM Settings, Add Nodes. Finally Add Operations.

Brilliant, that worked! Someone really should write up an official explanation because that wasn't intuitive at all.

In other words…if I created a map called Dallas, then went to the group details view for a group called Dallas, added that widget and selected the Group ${Name} from the drop down it would show the Dallas map?? Makes sense...but it doesn't work :-(

Yup, I see that...but what does it do?

Completely agree and was about to say the same thing msites. The known issues and fixed issues in the last several release notes does not reflect reality. Very frustrating.

We only use UDP Jitter and only on Cisco NCS 55A2-MOD-S devices. So it feels like it doesn't work at all. Even though none of my IPSLAs are working, it's encouraging to know that other device types still work. But what on earth could they have changed from previous versions to break only specific device types?? Something…

Ditto. No fix in 2023.1 GA. And no sign of 2023.1 RC2...

I'm afraid not. I looked and asked for a long time, no luck.

Same here.

The tech assigned to my ticket indicated that this would be fixed in a forthcoming 2023.1 RC2 !

The only devices we monitor SLAs on ASR 9Ks and NCS 5500s, both are affected.

Great, glad I'm not the only one. I also installed 2023.1 RC because someone suggested it might be fixed there. But it did not help. Maybe that'll save you the trouble.