Comments
-
Thumbsed up, adding that one extra table to the alert object-type-selector resolves the core problem of not being able to alert on a 2nd-to-nth bad drive per VM
-
Thanks and TY for bringing the office :)
-
Hi James @"jvb", this post is tagged as updated recently but actually has no WPM content and links to a page with no WPM content on it, beware!
-
Doesnt this work via powershell/bash?
-
Any DellEMC Powerstore support coming up?
-
(You can get decently close with a Custom Properties import to the Latitude and Longitude values without having to mess around with the API (google has answers for address/postcode -> lat/long))
-
The GET or POST request action element could reeeeeally use an update
-
Once upon a Tuesday dreary, while I pondered, weak and weary, Over many a quaint and curious KB of forgotten lore- While I nodded, nearly napping, suddenly there came mass ringing,- and of several someone's mumbling, bumbling past each other on the floor "'Tis some MI" I muttered, "something went wrong for the floor"…
-
Thanks @"kpina"!
-
ty I've upvoted I've made an API poller for it if ya struggling
-
3. Could bodge but should 100% be a feature
-
You can do this via Manage Nodes -> change the grouping to be by polling engine, check all, schedule mute
-
What Stuart said
-
I think I had something simmilar a year or two back, I'm afraid i dont have any notes though I'd put this in the bucket of stuff-likely-fixed-with-a-website-rebuilt/config-wizard-run though
-
There's more wizardry possible, depends how often you'd reuse it really - You could have one application template that checks the total list of 57 (for example), then outputs that to message comma seperated, then in an alert could assign that message value to a property, disable the original, and enable something to look…
-
To confirm - It does both install and import without error though? Weird Might actually lean toward a security thing
-
Had a look about- Yes you can do what you're trying to get done No not easy to edit that component port field in powershell as far as I can tell. There's a few ways of achieving this in a range of difficulties. * 1)* Make a application template with a port monitor on it for port 1 * duplicate 27 times changing the port…
-
What command/s are you running that give you that error? Install-module or import-module or something else? Posh7 does requre a later .net than 5, but if it's running at all you should have that
-
Yeah kinda, I'd literally join from the primary polling engine ID if I were doing it like in your screenshot You could also do it via the events alerting section Or put a monitor on it, and then alert via SAM etc The thing I was really responding to was if you've got one bit of SWQL that works, you can attach it to another…
-
Ah, I think I understand you now, i'll put one in the lab and test
-
Are you running this in local or remote mode? Just tested the core of this in a server 2022, seems ok. These are the important lines: $objStore = new-object System.Security.Cryptography.X509Certificates.X509Store("\\${IP}\My","LocalMachine") # Opens the Cerificate store and places contents into the object as ReadOnly…
-
I might give this a try later, need to put a passive agent in the lab somewhere first. You can probably do a ~ Select id, ip from agents where like passive | addNode.ps1
-
Nino's point 3 is where I expect you're stuck You can add as a node and as a vcenter, and the latter is what shows up in the virtualization summary
-
Check the creds are imported/assigned correctly Check the devices which are grey arent all clusted on one polling engine Check if those devices have security on them to only talk to the previous environment's Ip/hostname/cert/etc Check if you can test connection in edit node successfully
-
You can LEFT/RIGHT JOIN in the box immediately below if you really need to access something weird in the DB that that SWQL condition drop down doesn't allow. That's a workaround mind, and can make some weirdness with the alerting object being tangentially related to what you're actually alerting on
-
Worked OK for me: PS F:\Code\SolarwindsLab> $psversiontable Name Value ---- ----- PSVersion 7.5.1 PSEdition Core GitCommitId 7.5.1 OS Microsoft Windows 10.0.22631 Platform Win32NT PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…} PSRemotingProtocolVersion 2.3 SerializationVersion 1.1.0.1 WSManStackVersion 3.0 PS…
-
You can use SUBSTRING and REPLACE, but usually there's a more efficient JOIN, might be worth expanding on the scenario
-
AG health is probably what you want, there's a windows event log for errors and then health can be done with powershell SAM or simmilar, perhaps just SQL SAM
-
The code would be like Select COUNT(AA.ID) as [Count] FROM Orion.AlertsActive aa WHERE aa.STATUS like x You could join to the Orion.StatusDescription table for easier text selection or Alerthistory and whatnot for more details but for a count specifically it shouldnt matter much Wrote that freehand not validated, yell if…
-
There's a genuine difference if talking about the linux-flavoured-hostOS vmware ESXs are running, and if it's a random linux VM Similarly in the host scenario there's additional metrics exposed using one licensing type with Nvidia Also if it's a host (spot who had more hosts with GPUs to monitor) you can sometimes get by…