Posting an idea that was shared by josh.haberman: "...It would be nice to have a Visual Studio Code extension for SWQL. Ideally it would be nice to duplicate the capabilities of SWQL Studio in VScode but, even a simple linting capability would be great. My main push for this is that I use a Chromebook full time at work…
Currently the SolarWinds API supports Basic Auth. There ought to be options to configure and use OATH2 and/or Bearer/Token. Microsoft is deprecating Basic Auth currently, leaving the SolarWinds API in a less than desirable position. The SolarWinds API monitoring supports multiple authentication methods, so why can't the…
Recently, we found that only basic authentication is available against the SWIS Rest API. We would like to have token based authentication avalible to allow for a more secure and scalable way to use the SWIS Rest API
in certain scenarios we do not want a HA pool to fail over too quickly. The maximum timeout setting is 60 seconds, we would like to have this maximum increased to 180 seconds. if a VM reboots it is mostly back within a short period of time, but maybe a bit more than 60 seconds. This increase should accommodate the quick…
Be able to the use the signal -## gathered from the access point and the modern dashboard to present if the signal is weak, bad, good or great with an image
Solarwinds does a good job while monitoring the standalone databases, but there are limited templates available to support the advanced database technologies like always-on, failover clusters, log shipping, mirror database. Below are some use-cases for which standard support is very much required. 1) SQL always-on -- For…
Stealing this from a comment by @planglois It would be nice if SWQL Studio was converted to a VS Code extension! We could leverage other tools within it (i.e git, formatters, etc... ). PLEASE CONSIDER THIS! Many of us already use VS Code - this would make it a lot simpler and quicker to leverage the SDK.
I would love to use recurring maintenance mode for our patch windows, but the current options are a limited. The main issue I have is I need a way to base reoccuring maintenance based off a different day of the week. Say maintenance begins on the 3rd Tuesday of the month for dev, Wednesday for test and Thursday for…
Currently it's not possible to amend the SELECT query in any way, it is fixed. It would be beneficial to be able to amend this for advanced alerting and reporting.
Container and Kubernetes monitoring could be much deeper like pod-level visibility, service mesh metrics, and autoscaling insights. This is something we really need in modern environments.
It looks like you're new here. Sign in or register to get started.