Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

SWOSH Development in 2026 - What is your hope for the year?

Happy New Year to all THWACKsters!

With 2026 upon us, if you had a magic wand, what would you wish for SWOSH development for the year?

For me, I'd love to see #DarkTheme everwhere, as a default option per user. We saw great progress last year, but Modern Dashboards alone doesn't cut it for me or my users!

I would also love to see renewed focus on older features, like Device View. Having this expanded to all vendors and all models (with a default, non-branded view as placeholders) would help set SWOSH apart from what is an increasingly competitive arena.

Find more posts tagged with

darktheme

SWOSH

Comments

stuartd

As we move away from using SWOSH as our primary tool [not my choice but as it happens I now agree] then these are just some of my items that SWI have never properly addressed.

- Full and proper RBAC control over every aspect of the interface.
e.g. allow designated users full access to view and interrogate nodes (including audit trails) but no editing of any sort
- Proper granular monitoring of WAPs - see my feature request for this one.
- Much more flexible MAP creation and management to include aspects like import/export to industry standards like Visio. Drag and drop of nodes as Network Atlas still does when replacing/updating a node without having to delete, add, re-link, etc. More ability to control which individual auto-created links are shown (or not), etc.

- Give proper love and DEV time to offline tool, not just the cloud version as not everyone is willing to pump their data to a 3rd party that hide behind corporate walls.

That would have been my 2018 wish list. Actually, it was and nothing has changed in 7yrs so I don't expect much love to be shown to aspects SWI have successfully managed to ignore for over a decade!

fop

My main one is increased RBAC so we can have utterly non-priv'd users (customers) being able to view their own estates. There are workarounds for this. I realise this might be kind of difficult for a product that isn't designed to be multi-tenant though.

SSO auth for SWQL Studio. Currently I can't let my users access it because only the admin login works in our environment.

Dark Mode. (that originally came out as Fark Mode which would also be fun)

The other thing would be fixing the Azure Cloud bug that wipes out my cloud accounts from 2025.4 onwards 😁

bourlis

Oh man, too many to list! My head is spinning! Here' a small list of my wish list. I'm sure more wishes will pop into my head throughout the day.

RBAC
Advanced auditing paired with self-health stats.
- I want to know the 3 W's - who, what & when.
- I want to know the possible ramifications, for example if a server is deleted, I need to know:
  - What monitoring/alerting needs to be fixed or removed.
  - What reporting needs to be fixed or removed.
  - What NetPath functions needs to be fixed or removed.
  - What dashboard views need to be fixed or removed.
A centralized credential library with mandatory description & usage fields. An example would be.
- Credential - A
- Usage - VNQM
- Description - Use for VNQM monitoring in zone A.
- Credential - B
- Usage - WPM
- Description - WPM Domain service account.
Fully integrated & supported SWQL Studio in the settings dashboard.
More…, many more modern dashboards! I really want to have a modern dashboard view of Manage Nodes.
- If you do that then go for the 'home run' and add Modern Dashboard Views by Machine Type!!!!
Reports in a Modern Dashboard format.
Add 'export as..' function to all custom-built modern dashboards.
Add 'export as Viso function to all maps.
Bring SolarWinds Putting into the SolarWinds platform.
Some sort of integration with Dameware that uses the Dameware remote desktop interface natively in SolarWinds. Access to use this Dameware integration would be part of the RBAC rights.
More API functionality.

planglois

This year, I wish for:

A lot of improvements on Juniper monitoring (Spanning tree, routing, optics, VRFs, VLANs, VPNs etc…) to bring it to par to other manufacturers in SolarWinds.
Having the possibility to poll multiple SNMP contexts on a single node/IP without having to consume multiple licences
Have Hardware Health available for Dell servers via the DRAC interface (without having to monitor via OS)
a redesigned Network Discovery process/interface
love given to NCM (have "n/a" icons instead of all green, search bar, better use of real-estate…)
UnDP & groups assignation profiles based on node characteristics
A review of THWACK feature requests by PMs. There are so many FRs that can be closed, or that should be looked into! Heck… I found stuff I wrote back in 2013 still active…

I swear, I am not on the naughty list! 😉 Pretttyyy pleaaaaase!!!

Deltona

I have so many to mention but I will start with LA.

1.
I would really like a description field added to Custom Rules.
Adding all the rule-specific information in the Custom Rule name, makes reading the Custom Rules very difficult.

2.
I have around 400 pages of Custom Rules and they keep increasing.
I can search for a specific Custom rule name but I may not remember what the Custom Rule is called.
Even if I do remember the name, I might still need to sift through multiple pages to find the right one.
My suggestion is to implement tags (or Custom Properties) to Custom Rules.
Combine that with grouping/filtering functionality would make identifying Custom Rules so much easier.

I could have a bunch of Custom Rules tagged with Cisco ISE or Commvault, and I would then be able to see all <> rules w

marcrobinson

Just a couple.

RBAC for OSH. It has been a pain point for years and I agree with the choir.
SolarWinds API should use OAUTH2 and Bearer Tokens. This is my feature request from 2022. Still need it.
Integrate Solarwinds SDK with VS Code. Might not need SWQL studio then. Another feature request but not as old.
More love for NetPath - just because.