jvb · Senior Product Manager · ✭✭✭✭✭

@"geats" The documentation you linked is specific to our SaaS based SolarWinds Observability platform instead of VMAN which is part of the on-prem HCO platform. Unfortunately the old snapshots report you are working with is specific to VM snapshots running on-prem in a hypervisor (VMware). I am not aware of a report in…

@"sdest" You should be able to make a copy of the out of the box "All VMs" report and change the selection criteria so that NodeID being empty is used in the selection. NodeID should only be assigned a value if the VM has been fully managed so using that should show your remaining unmanaged virtual nodes:

It has been awhile since I looked at the specific logic but as Adam said, some stuff will stop monitoring. I believe it is generally a FILO situation or, said another way, stuff that has been "in" for awhile will stay "in" but there are some situations where that might not work perfectly so it is best to use the…

Got it, thanks!

Yeah, I see it now. OK, I am going to push for some escalation on this. It is concerning that the workaround did not fully resolve it for you. Other customers are having good results with the workaround so we need to dig a bit deeper to see what is different in your case. Thanks for your patience!

I replied to you in the other thread as well but just in case you didn't see it over there (much longer thread) I did not see reference to the extra arg being applied and not fully working in your ticket @"jklundy"

Do you have a ticket open @"nmoura38"? We are tracking this issue internally so it would be helpful to have your environment added to the research.

The WPM issue referenced in this thread is specifically not solved in 2023.2.1. There is a fix coming in 2023.3 and there is a workaround available but it sounds like you have applied that workaround (the extra arg in the config) and it is not resolving for you on some players. Make sure that you update your support ticket…

Under the hood the platform is trying to identify relationships between entities that it knows about so that you can utilize this info when troubleshooting. (Topology, Orion Maps, AppStack etc.) If the underlying volumes you mention are where the VM storage is allocated then what you are seeing would make sense. If what…

I believe this is what you are looking for: https://hco.demo.solarwinds.com/Orion/Login.aspx

Thanks @"kpmarcin" I will ask the engineering team to look into this.

What version are you currently running? Once upon a time we did some matching based on MAC address and so converted machines might get confused based on that but as far as I know we do not match like that any longer. It might be a good idea to open a ticket and ask support to help pinpoint where the problem is. If they…

@"adam.beedell" I'll put an item in the backlog for the engineering team to check on a possible option to just ignore. Thanks!

Generally speaking that error and it's causes should have been resolved in a version well before what you are running so I would ask you to open a ticket with support so they can investigate that with you. Without logs and some other info it is hard to tell why you are seeing this in 2022.4.1. Thanks!

@"adam.beedell" This is great! Thanks for providing a solution to a problem many have encountered. I'll ask the team to take a look at it for consideration as part of an out of the box alert. 

This is the SWQL we have internally SELECT TOP 1000 TransactionId, TransactionStepId, RecordingId, StepId, TransactionSteps.Step.Name, WarningThreshold, CriticalThreshold, OptimalThreshold, TransactionSteps.Transaction.LastDateTimeUtc, ScreenshotId, ScreenshotDateTimeUtc, TransactionSteps.LargeData.Screenshot FROM…

@"adam.beedell" Good catch! I read and responded too quickly thinking @"s-bolyard" was looking for the complete history of screenshots good or bad. Let me find the location of the images in the "last 10" widget and also see if we have any suggestions for extraction for longer term storage... The last 10 can cycle out…

The screenshots are stored in the database at dbo.Screenshots and SEUM_TransactionSteps However, WPM only keeps the current screenshot from the most recent poll. There is no history of the screenshots maintained. 

If the problem continues to present itself, please open a new ticket with support so we can investigate further. That is certainly not expected or by design behavior. If you need to, feel free to ping the ticket number back to this thread and I can check on it internally.

Can you open a ticket on that so our team can investigate? 

The QNAP and Synology devices are open feature requests but they are not on the near term roadmap for support. If you have NPM or SAM you might be able to add those as SNMP nodes and get some basic data from them that way. The Dell ME4024 might work if you use the "Dot Hill" template when you are adding it to SRM. The…

If you can ping the ticket number here I will try to give it a nudge internally. Also as @"stuartd" suggested, the sales rep and / or the customer success manager assigned to your account can also help with escalation.

@"MarkyB" That sounds like something we should investigate with you through a support ticket. That does not sound like "by design" behavior. The support team can take a diagnostic look and they will escalate to engineering if they need to.

This issue has been identified and fixed in a release that is slated to be available hopefully in the next handful of weeks barring any unforeseen circumstance.

I don't have an Isilon handy to check directly at the moment but off the top of my head if the non-auth events cannot be set to emit as traps or syslogs, I am not aware of any other way beyond a custom API call. Those would be best suited to either a scripting component or API call from SAM rather than SRM.

You should be able to do that with a standard report rather than recommendations. Screen shot below shows the basic criteria to select in the report. Make sure to also include the column "Average CPU Used" from the "VM Statistics History" grouping.

There are advanced settings where you can tell VMAN to ignore IP addresses, MAC etc. Perhaps setting the cluster address to be ignored would fix that. The advanced settings are at: http://my.orion.server/Orion/Admin/AdvancedConfiguration/Global.aspx Then search for "SolarWinds.VIM.Common.VimSettings"

Unfortunately VMAN does not store any user information that you could use to augment the alert in the way you want.

Hi Adam, Can you direct message me the ticket number so I can get a little context around the conversation with support? With that in hand I will try to get you some more clarity on the subject. Thanks!

The X/Y mode can record a click at a specific location. There is also the keyboard combo of "Ctrl + ~" that can sometimes be used although that is usually more effective at solving for hover over / fly outs that don't register with regular clicks.