jlhartsock · Monitoring Capability Owner · ✭✭✭✭✭

Is this new technology stack still in the works and will be delivered soon? We just upgraded to the newest available platform release and do not see the "eliminate the need for things such as the existing page refresh" functionality yet.

Second this comment. We've tried using groups for auto assignments of SAM monitors and have found very mixed results. Some groups work completely flawlessly and then others will have random members join and drop from the groups for no reason. I've went through multiple support cases and more diag captures than I could even…

Gladly. The main complaints all culminated around three points. The first complaint was about the view structure. The users liked the widget viewing structure and information better within the appliance vs the orion plaform. The second complaint was about the capacity planning visibility. Within the Orion platform, I…

rschroeder Sweet! I'm looking forward to it. We're not far behind so my expectations are a bit uplifted from the last experience. Orion Platform 2017.3, QoE 2.4, CloudMonitoring 1.0.0, SAM 6.4.0, NPM 12.2, IPAM 4.5.2, SRM 6.5.0, NTA 4.2.3, VIM 8.0.0, DPAIM 11.0.0, NCM 7.7, NetPath 1.1.2 aLTeReGo​ HAHAHA! Definitely took…

We're having the same problem (compounded with every event going from SW to SN instead of just alerts) so we ended up having to disable the built in integrations, unfortunately. We're currently using a python script that is called as part of the alert action to send alerts from SW to SN using the SN event API. Definitely…

Did you ever find a solution for the "Cannot remove this column" error? I'm getting the same thing when trying to look at the events table. I can query any other table without issue.

We're still in the initial phase. We have 1% of our apps in AWS and are working to mature a process to set the priority of which apps are next.

They're using the view as part of a metric to evaluate the priority that is getting assigned to apps in our journey to migrate many of our apps to AWS.

My IT support partners will not authorize moving away from the appliance until the AWS cloud cost view is added to the Orion platform.

Correct. It looks like this as soon as any other email addresses or variables are added. Here is an example that shows the setup within the to field and then the second screenshot is the results.

slinton​, You nailed it. I'm seeing the exact same behavior as I look closer. I also tried adding a second custom properties and it is doing the same thing with adding extra curly braces to both variable. When I remove everything else and only have the single variable, the alert works correctly and pulls the correct…

Hey benyin​, You have to create a new custom property field. This can be done from the all settings page.

One note (and I will open a case on this) after three days, this quit working for some reason. It started substituting the literal string into the TO field instead of addressing it as a variable.

You can actually simplify this by just using the custom property direct name. Not sure it really makes a difference but I've tested this in my NPM 12.3 environment and it works great.${N=SwisEntity;M=Application.CustomProperties.EmailTo}

* SAML Authentication Support !!!! Thank you, thank you, thank you! We have to get all of our tooling to support SAML by EOY as part of our new security policy.

I can't really help directly answering your question but I at least wanted to provide insight from our journey of trying to use the integrated VMAN polling within Orion. Long story short, we ended up going back to using the appliance because of the functionality and views that were lost by using the internal VMAN polling.…

Following this thread to see if anyone gets a straight answer. I was given the "build a bigger database server" response when my DBAs only see about 40% utilization of our current setup. They did double my available RAM on the SQL box but we're still seeing the errors with the same frequency but with even lower utilization…

Found this thread looking for the same answer. I opened a case but never got back an answer other than "build a larger database server".

Thank you for the post and answer. After working with support, I had a few of these monitors working and then hit a few that I could not figure out. Flipped over to x64 and away they went.

Replying in case this helps someone else out. I was able to get some time for one of my DBA's inhouse and created the following query that can be run using the database manager utility. I've not found a way yet to build this into a report so I execute this monthly and then update the HTML widget on my report. By changing…

Bump *Any sql devs our there that can help?*

We're seeing the same behavior on the AD template. Some work without any problems while other just randomly start displaying the mentioned error message. Following this thread while I wait on a response.

I'm going to perform another batch of upgrades within a month so hopefully I see the same experience. My last upgrade in October ran just under 4 hours when running the installer and config wizard on my primary server and 3 APEs.

If you don't have Solarwinds HA: * Why not?The lack of support for zero downtime upgrades turned this effort into a non-starter for the conversation within my company.* Cost? The cost could be easily justified if we did not incur outages during upgrades. However, since that wasn't on the table, I couldn't provide a…

I won't be much help here other than saying you're not alone. We have the agent running on about 100 nodes in our environment and since we upgraded to 2018.2, we've hit a few instances where the agent just start swallowing RAM. We restart the service and it goes away. I opened a support case for it but the only "solution"…