Have WPM fire a traceroute at the exact same time that a recording is being played back

Running traceroute as part of the alert actions is an ok addition.

As a team, we will still prefer a trace route and/or NetPath that will run concurrently with the WPM recording playback if it is possible to have in SW.

I've recently created another feature request similar to this thread, but with more elaborate and detailed set of concurrent tasks along with the WPM playback ->

Makes sense. The reason I mentioned Netpath is that it's always available for historical, etc. Would it be possible to use the alert for the step or transaction being down to trigger a traceroute and dump the results to a textfile? I think that might work for you.

Re data collection intervals - yeah, I think most shops of any size have to scatter it a bit.

Yes I've created NetPath monitors for it.

Our team has seen times / occurrences that the WPM monitor is down, but NetPath's doing ok.

However, in my knowledge, the data collection schedule and timestamp of the WPM monitor will not necessarily and will not exactly coincide with the playback of the WPM recording.

So, our team's conclusion is that we cannot exactly rely on the "WPM + NetPath" combo in doing RCA. Hence, the feature request.

As a side note, in general, that is also the same conflict that I see in the PerfStack feature.

You can stack various charts but the actual data points were collected from various data collection intervals.

In our environment:

ICMP data is collected every 2 minutes

SNMP data about CPU load, Memory used are collected every 10 minutes.

SNMP data about Disk space is collected every 15 minutes.

SNMP data about interface stats are collected every 9 minutes.

SW SAM component monitors run every 5 minutes.

SW WPM component monitors run every 5 minutes.

SW NetPath monitors run every 10 minutes.

It's a good idea. Upvoted.

While this doesn't directly address your concern, have you considered building a Netpath view to the Web resource in question? While not specifically a traceroute, the information it provides can be just as (if not more) useful for RCA isolation/tshooting.