nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
- SolarWinds Academy
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
Store

SolarWinds lab environment for pattern testing

i_like_eggs

Is there a legitimate route to access a small SolarWinds lab, dev, or NFR-style environment for non-production pattern testing?

I’m not looking for anything customer-specific, and I’m definitely not looking for a shortcut around licensing.

The kind of work I’d like to test is more around reusable SolarWinds patterns:

dashboard layouts
custom widget behaviour
HTML/SVG approaches
JavaScript where supported
scaling techniques
alert presentation
state views
ways of making operational data easier to understand

Trials are useful, but they are short-lived. Production and customer environments are not really the right place to experiment with this kind of work properly.

Ideally, I’d like to keep this kind of personal R&D separate from employer or customer estates, so patterns can be tested cleanly, safely, and without any customer data involved.

For anyone who has done something similar, what route worked best?

sales-backed lab or dev licensing
partner or consultant routes
MVP/NFR licensing
small paid lab entitlement
rotating trials
something else entirely

Even a very-very small node-count entitlement would be enough for this use case. The goal is simply to have a proper, safe place to test, refine, and validate ideas before anything is reused, shared, or written about more widely.

Has anyone gone through this before, or found a good way to approach it?

Find more posts tagged with

30_day_trial

licencing

npm - network performance monitor

Comments

i_like_eggs

Thank you, that’s really helpful. That route sounds like the cleanest fit for a small, safe lab. Really appreciate it

HerrDoktor

I am using my MVP license on my personal lab.

We also have a partner NFR if I need more than the mvp license covers.

i_like_eggs

No worries at all, the egg appreciates the Grumpy Human guidance.

I’m really just trying to keep this completely separate from employer/customer environments so I can test patterns cleanly without production baggage 🛄

HerrDoktor

if you own a production license with Enterprise option, you have a LAB license included.

——

nevermind didn’t fully read the post, you want to keep it disconnected from your employer

Quick Links

PALO-ALG - Logging
PALO-ALG - Logging.xmlPalo Alto Networks ALG Security Technical Implementation Guide :: Version 2, Release: 3 Benchmark Date: 27 Oct 2022
Alert HTML Content
Alert Cleared.htmlHello, I would like to share the HTML template details we have prepared so that Solarwinds alarms can become more meaningful. It can list alarm object details and connected device details separately in HTML template. Except for object and device details, you can easily add custom property information…
Cisco ASR Devices
Cisco ASR Devices.pollerCisco ASR Devices
Basic SWQL Syntax
SWQL is built on the framework of SQL and as such supports most of the standard clauses as part of a query. A very simple example query is: SELECT Caption, IPAddress, Vendor, ResponseTime FROM Orion.Nodes Dissecting this query is relatively straightforward: show some fields (Caption, IP address, Vendor, and Response Time)…