jvb · Senior Product Manager · ✭✭✭✭✭

There is a hot fix that resolves the issue with the Recorder installation available now: Success Center

Yes, there is an update to the deprecated recorder that needs to be installed but it will still be the old recorder when finished. The new and old recorders are two distinct installs and can run side by side on the same machine. If you are having issues with the auto installer go get the bits from the "Manage Transaction…

You shouldn't need to. If you write your script in a way that allows for parameters to be passed in you can use the "Insert Variable" button (towards the right in my screen shot above) to pass in the name or IP of the triggering object.

There are some updated templates posted for MySQL 8 now: https://thwack.solarwinds.com/docs/DOC-203898 https://thwack.solarwinds.com/docs/DOC-203897

@"kpmarcin" I would say open a ticket with support so they can look over the diags for that particular environment and insure we get you the best solution. 

I think you are on the right track having a ticket open on both sides. Seems like something isn't quite right there but not certain exactly where. Feel free to ping the SolarWinds ticket number back here or in PM and I'll keep an eye on it.

According to the extended info in the detail it is what SQL server would like to use

The other way to possibly get closer to the result you want would be to adjust the sensitivity of the alert itself. Use the "Condition must exist for "X" minutes" feature on the Trigger Condition page...

Sorry for the delayed response here... We shuffled product managers a bit recently and I am just getting ramped up. I am actively researching if there is anything published that outlines the Orion based VMAN metrics in the same way as the chart related to the old appliance.

So it seems this is not as straight forward as a query unfortunately. There are no indications in the DB about what rule applied the tag. The only place to see what you are looking for is likely in the logs and only if the level is set to debug which can generate a great deal of info very quickly. This may be a situation…

Image match or image verification is not yet included in the new recorder. It is one of the feature parity items we are still working on. I believe in Ben's case he is talking about a simple click on the image rather than an attempt to match the image.

I should have asked... Do you already have a rule with quite a lot of them that isn't working or is the question more theoretical in nature?

Does it fail and show as down (red)? Or does it just never play at all (grey)? If the latter check and make sure that the SEUM accounts on the Orion box (or wherever playback is running from) are set as local admin.

M Cooper... There should not have been any reason for the 6.8 install to make that change. Can you open a ticket so the team can investigate how that happened?

Hi Matt... I just double checked the ticket and it is indeed being investigated by the dev team. Both myself and aLTeReGo​ are keeping an eye on it internally. Thanks for your patience while we investigate!

Thanks for the very complete response!

I think I pretty much verified this... I can't find anywhere that we are categorizing to the level of granularity you are hoping for. So, the Custom Property route will give you the results you need but will require some work up front. That being said, if you still wanted to group both on the original "Category" field and…

Yes, we recently closed out a beta test with the latest version of WPM which removes the reliance on IE. We are taking a little time to implement some things based on the feedback from the beta and are moving quickly towards the next milestone.

Support is correct that image verification still requires the old recorder. We are continuing work on the new recorder and hope to reach feature parity soon. That being said I am curious what you mean when you say you can't monitor or alert. All transactions should be eligible for monitoring and alerts regardless of which…

You don't need to re-record the whole transaction. You can edit text (like passwords) by opening the recording and then enter "Play action-by-action" mode (third button) and then you can click the three dots to the right of any action and select "Edit" (screen shots below). On your other ask for the ability to ignore…

vinay.by​ is correct. You would need one HA license for each server that you wish to cover (main instance + 2 pollers in your case). Each pool consists of two servers.

jxchappell​ is absolutely correct... It is not possible to merge multiple Orion DBs into one.

Yeah unless I am missing something it looks like it is broken again...

If you don't mind having two reports there is an out of the box report for the IIS based stuff. So you could use that and a custom report along the lines of what I posted above. I realize that kind of comes up short on the request for a single comprehensive report but it is an option.

Marc beat me to it.

As far as I know, renaming the hash will change the color but it randomly selects a new color. You don't get to choose. If there is a way to permanently affix a specific color to a hash I am unaware of how to do that but mandevil​ might know a way if anyone does

If the above doesn't work, ping myself or serena​

If you open the transaction in the recorder and play it back does this same step report 0.00 there as well?

Yep, any module running on Orion Core 2018.4 and higher will run on Server 2019. In addition to using the agent to monitor 2019 servers as mentioned in the OP there is also a SAM template for Server 2019 Windows Server 2019 Services and Counters

At the moment, no. We have what we need. Thanks!