You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For some resources you'll want to configure multiple probes of the same type with their own checks. If one of these probes/checks fails, you cannot find out easily which probe failed by requesting which URL.
Describe the solution you'd like
If GHC would show (or even better: provide a hyperlink), the user can quickly check if the error is still valid, or start debugging to solve the issue.
Describe alternatives you've considered
A work-around is to configure the same resource multiple times, each with a single probe.
Additional context
As an example: the demo site shows the geonode training is failing. This resource has two probes, but in the Last run result it doesn't show which probe fails and what URL was called to assert the resource (although, in this case it's a getCap and getMap probe, so it's quite obvious which one causes the error). Still: a hyperlink to a new browser window to call the exact URL would be appreciated.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
For some resources you'll want to configure multiple probes of the same type with their own checks. If one of these probes/checks fails, you cannot find out easily which probe failed by requesting which URL.
Describe the solution you'd like
If GHC would show (or even better: provide a hyperlink), the user can quickly check if the error is still valid, or start debugging to solve the issue.
Describe alternatives you've considered
A work-around is to configure the same resource multiple times, each with a single probe.
Additional context
As an example: the demo site shows the geonode training is failing. This resource has two probes, but in the
Last run result
it doesn't show which probe fails and what URL was called to assert the resource (although, in this case it's a getCap and getMap probe, so it's quite obvious which one causes the error). Still: a hyperlink to a new browser window to call the exact URL would be appreciated.The text was updated successfully, but these errors were encountered: