Comments
-
this reminds me of the Pepsi Jet! en.wikipedia.org/.../Leonard_v._Pepsico,_Inc.
-
Thanks for sharing with the community. You can share the PS1 file directly in the content exchange here Scripts or upload the entire SAM template here Application Monitor Templates
-
If you are already using SolarWinds/NPM to monitor other connections, Starlink shouldn't be any different. One of our customers has a couple of Starlink connections so I'll ask the question to see if they're doing anything differently.
-
I had asked previously whether there were any limitations with the number of subqueries SWQL could handle but didn't really get an answer.
-
Glad it's still helping people
-
It might sound silly, but make sure you haven't got something else running that may be wanting to use the same ports!
-
There's a feature request for this and it's set to "What We're Working On" thwack.solarwinds.com/.../support-sd-wan-for-fortigates-devices
-
We ran into the same problem, lowercase worked! Thank you
-
I didn't get anywhere when I raised the issue to SW support on 01447266 In the end, I had to rewrite my query using a LEFT JOIN of all the individual tables that were previously run through with a subquery. It's messy, but it gets the job done.
-
I've found the same with some links
-
is that more geared towards laptop users when you mean "mobile" as I wouldn't think you'd be downloading any of the shared cotnent to a phone with a smaller screen?
-
Turned out the device didn't have a route to the correct network for SNMP traffic to reach SolarWinds. All the same, not much can be monitored with SNMP so will be looking at possible UnDP or API Poller. Will update.
-
Thanks, I was actually looking for a workaround and obviously had a blonde moment! It doesn't look like there is an OOB way round this for now, but have put together the following and will monitor.
-
I was impatient and contacted Support. It's not currently possible, so I have raised a feature request. thwack.solarwinds.com/.../incidents-created-by-integration-with-solarwinds-platform-should-resolve-automatically
-
No further problems witnessed our side, we generally recommend to our customers to maintain upgrade paths. N-1 is what we generally recommend. 2023.3.1 has been out and stable for some time.
-
If Proxmox supports SNMP monitoring, you may be able to monitor a sufficient amount using that.
-
Just did an upgrade to 2023.3 - can confirm, you need to run DB Maintenance following the upgrade for the problem to clear.
-
Seconded... most have the option of "don't ask for 14 days"
-
I ended up doing the exact same thing... messy, but it worked!
-
I had exactly the same response... This does sound like a bug, I will see what I can do & if we have any contacts that could potentially escalate.
-
Ditto on 2023.2.1 but in standard Orion... looking to upgrade the customer to 2023.3 to see if it is working.
-
Fingers crossed
-
RC for 2023.3 has been announced today documentation.solarwinds.com/.../solarwinds_platform_2023-3_release_notes.htm
-
Yep they said the same for one of our customers. Resolved in the Q3 release. Hopefully July/August.
-
the .3 release will be July time hopefully
-
Do you have SAM? You could just use AppInsight for SQL or a SQL monitor to pull the data and then use SWQL to display the data on a dashboard or view.
-
We've got a customer willing to hold off until the Q3 2023.3 release as they've recently upgraded and have a large estate.
-
I've noticed that Cisco USC Managers are also showing as Machine Type = Unknown, Node Category = Other.
-
There seems to be a discrepancy with the way QNAP devices are displayed - some are QNAP SYSTEMS, INC. (all upper case) and others have the vendor presented as QNAP Systems, Inc. The all upper case Vendor type has the icon 24681.gif assigned. Everything else gets 0.gif. I've created custom pollers for the time being to stop…
-
Hi Joey That is indeed what I'm talking about. I have raised a feature request for this. Thanks thwack.solarwinds.com/.../customize-solarwinds-logo-in-technician-view-for-company-branding
