Problems with first step going into critical mode

We just purchased SEUM and it's great, but we are having an issue with a few test recordings that we are doing. We have a simple 4 step recording and it all works fine except for the very first step that navigates to the webpage that you start always takes longer than it should. Has anyone else had an issue with this? Is it a firewall or security issue? I've attached a screen shot that shows the 95%tile over 6 times the typical. I think the issue is that the recorder works too fast and the actual player has a few more obsitcals to deal with.

Find more posts tagged with

step

into

critical

first

mode

with

problems

seum

going

Accepted answers

netlogix

I had the same jumpy graph too, and I got it to smooth out by forcing it to run only one playback at a time see http://thwack.solarwinds.com/message/167700#167700

But be careful, what I did could mess things up and is not SW supported. If you don't give enough time for everything to complete, then you can cause issues for yourself.

All comments

netlogix

Looks like your first step got set to 1/2 sec as it's "typical" speed, but the player is getting closer to 4 seconds on the initial step; do you feel 4 seconds is "ok" for the first step? I always edit the "typical" to something more realistic than the recorder set. I suggest you edit the transaction assignment and set Warning to 8, critical to 16 and typical to 4 (or what fits you needs best). Also, was the recorder local and the player remote? I have a player in my primary datacenter that has *really* low times, another that is in my other datacenter with low times, one with amazon in northern California that is slow and another through dell in Texas that is acceptable. For each assignment and step, I got the average step time and set that to the typical. I think it might just need a little tweaking to fit your environment.

jiri.tomek

Hello,

typical value that Recorder calculates is taken from one playback that Recorder does before saving recording. It may be affected by many things such as machine where Recorder runs, current network load etc. Because of this, this typical value may be lower or higher than actual average value that you get during playback on specific location. As Steve suggested, if you find 3.78s as standard step duration, just go to "Admin->SEUM Settings->Manage Transaction Monitors" and edit threshold values for the transaction as required.

FormerMember

I took your suggestion and it's working for now, but look at some of the graphs I think there might be a problem with the player. I'm running it off the same machine that I ran the recorder on. But if you look at the navigation times there is some extreme variation, but it's very patternized in its oscillation. Is this normal?

netlogix

I had the same jumpy graph too, and I got it to smooth out by forcing it to run only one playback at a time see http://thwack.solarwinds.com/message/167700#167700

But be careful, what I did could mess things up and is not SW supported. If you don't give enough time for everything to complete, then you can cause issues for yourself.