[Uptime] Monitors with public/private locations fail to 'run now' in private location

[andrewvc]

Creating a monitor with both public and private locations selected works fine, but using the run now feature attempts to 'run now' in all locations. The private location never returns results in the GUI, we should never show a status for that location.

ACs

• Run Now is available for any monitor configured to run on one or more public locations
  • Irrespective of it also configured to run on a private location
• When using Run Now, it only attempts to run the test on the public location(s) (not any private locations is may be configured to run on)
• Run Now behaviour should be consistent from:
  • Monitors (Overview) page in Uptime (monitor list, Test now column
  • Add/edit screen in Uptime (Run test button)

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[paulb-elastic]

@andrewvc is this with main? Thinking about how this relates to #138862 where it suggests it's not available (cc @awahab07)

I think the summary should be that:

• Run Now is available for any monitor configured to run on one or more public locations
  • Irrespective of it also configured to run on a private location
• When using Run Now, it only attempts to run the test on the public location(s) (not any private locations is may be configured to run on)
• Run Now behaviour should be consistent from:
  • Monitors (Overview) page in Uptime (monitor list, Test now column
  • Add/edit screen in Uptime (Run test button)

It would be good to consolidate these two tickets if agreed.

[andrewvc]

I think that description is right, I've updated the top comment with your text @paulb-elastic . @justinkambic hit the issue while recording our 8.4 release video, which I believe was on an 8.4 stack. I'm a bit confused since he could run it using test now.

You can see the bad behavior here: https://youtu.be/lG4OcV314_k?t=1612

[justinkambic]

Yes we were running an 8.4.1 stack when we recorded the release video. We attempted to use Run Now, which we showed while configuring the Private Location toward the end, and had to backpedal from that improvised part of the demo when it failed.

[andrewvc]

CC @awahab07 since he's the author of the other issue

[awahab07]

I'll look into both of the issues together. I need to confirm if both of the issues occur consistently and if they are related. The problem mentioned in issue #138862 depends on the order of records fetched, so it's not consistent, but definitely need to be fixed.