Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Uptime] Overview link to Exploratory View should not filter by monitor #122907

Conversation

justinkambic
Copy link
Contributor

@justinkambic justinkambic commented Jan 13, 2022

Summary

Resolves #121348.

The Overview page should no longer filter the Exploratory View by monitor name when the link is clicked.

Testing this PR

Follow the steps in the linked issue. When running this branch you should see that the exploratory view link that the page generates does not contain a monitor-specific filter on the overview page. This monitor filtering should work on other pages.

  1. Index some data with Heartbeat.
  2. Go to the Overview page in Uptime.
  3. Drill into a monitor.
  4. Return to the Overview page without reloading the app.
  5. Click the Explore Data link.
  6. Ensure that the Exploratory View is not filtered down to a single monitor.

Repeat these same steps with the certs view. Start on the overview page, drill in, then go to certs and link to exp. view.

Ensure that when clicking from the detail page of a monitor, the exp. view is still filtered by monitor.

Checklist

Delete any items that are not applicable to this PR.

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk Probability Severity Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space. Low High Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks. High Low Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled. Medium High Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

@justinkambic justinkambic added bug Fixes for quality problems that affect the customer experience v8.0.0 Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v8.1.0 v7.17.0 labels Jan 13, 2022
@justinkambic justinkambic requested a review from a team as a code owner January 13, 2022 04:17
@justinkambic justinkambic self-assigned this Jan 13, 2022
@elasticmachine
Copy link
Contributor

Pinging @elastic/uptime (Team:uptime)

@justinkambic
Copy link
Contributor Author

justinkambic commented Jan 13, 2022

Note to reviewers, don't review this yet. We've had some offline discussion, some changes are needed.

This is now ready for review.

@justinkambic justinkambic force-pushed the 121348/explore-data-button-on-uptime-overview-filters-by-a-specific-monitor branch from f4eeef4 to 4bec0d1 Compare January 13, 2022 22:09
@justinkambic
Copy link
Contributor Author

@elasticmachine merge upstream

Comment on lines 62 to 68
/*
* The second condition exists because we don't want to link users to an
* exploratory view that is filtered by a specific monitor when they're on
* the Uptime Overview page.
*
* This condition is intended to allow monitor filtering on all other pages.
*/
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment is helpful but seems unnecessary :)
I think code is self explanatory, No?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was on the fence about it. I told myself if the reviewer mentioned it I'd delete it 😉

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done baa460e.

@justinkambic justinkambic force-pushed the 121348/explore-data-button-on-uptime-overview-filters-by-a-specific-monitor branch from 7b7b521 to baa460e Compare January 14, 2022 18:17
@justinkambic justinkambic added the auto-backport Deprecated - use backport:version if exact versions are needed label Jan 14, 2022
@justinkambic justinkambic enabled auto-merge (squash) January 14, 2022 18:18
@justinkambic justinkambic merged commit 939a642 into elastic:main Jan 14, 2022
@kibana-ci
Copy link
Collaborator

💚 Build Succeeded

Metrics [docs]

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id before after diff
uptime 688.3KB 688.3KB +64.0B

History

  • 💚 Build #17529 succeeded 7b7b521d37b37de3a42bcb55b0d4e339dfba2919
  • 💛 Build #17403 was flaky 4bec0d12dbc78dd8f7c0d63445f4b20a0496b6b1
  • 💚 Build #17160 succeeded f4eeef4152856a645d86475cb4ea7cfee0de3cb8

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

cc @justinkambic

@kibanamachine
Copy link
Contributor

💔 All backports failed

Status Branch Result
8.0 Backport failed because of merge conflicts

You might need to backport the following PRs to 8.0:
- Revert "[Uptime] redirect Uptime tutorials to the Elastic Synthetics Integration (#115229) (#115470)" (#118986)
- [Uptime] redirect Uptime tutorials to the Elastic Synthetics Integration (#115229)
7.17 Backport failed because of merge conflicts

How to fix

Re-run the backport manually:

node scripts/backport --pr 122907

Questions ?

Please refer to the Backport tool documentation

justinkambic added a commit to justinkambic/kibana that referenced this pull request Jan 18, 2022
…or (elastic#122907)

* Modify Exploratory View link to prevent filtering by monitor from Overview page.

* Modify route match so only detail page will include monitor name filter on exploratory view link.

* Remove unnecessary comment.

(cherry picked from commit 939a642)
justinkambic added a commit to justinkambic/kibana that referenced this pull request Jan 18, 2022
…or (elastic#122907)

* Modify Exploratory View link to prevent filtering by monitor from Overview page.

* Modify route match so only detail page will include monitor name filter on exploratory view link.

* Remove unnecessary comment.

(cherry picked from commit 939a642)
@justinkambic justinkambic deleted the 121348/explore-data-button-on-uptime-overview-filters-by-a-specific-monitor branch January 18, 2022 17:36
justinkambic added a commit that referenced this pull request Jan 18, 2022
…or (#122907) (#123262)

* Modify Exploratory View link to prevent filtering by monitor from Overview page.

* Modify route match so only detail page will include monitor name filter on exploratory view link.

* Remove unnecessary comment.

(cherry picked from commit 939a642)
@kibanamachine kibanamachine added the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jan 18, 2022
@kibanamachine
Copy link
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.

@kibanamachine
Copy link
Contributor

Looks like this PR has backport PRs but they still haven't been merged. Please merge them ASAP to keep the branches relatively in sync.

@kibanamachine kibanamachine removed the backport missing Added to PRs automatically when the are determined to be missing a backport. label Jan 20, 2022
justinkambic added a commit that referenced this pull request Jan 20, 2022
…y monitor (#122907) (#123268)

* [Uptime] Overview link to Exploratory View should not filter by monitor (#122907)

* Modify Exploratory View link to prevent filtering by monitor from Overview page.

* Modify route match so only detail page will include monitor name filter on exploratory view link.

* Remove unnecessary comment.

(cherry picked from commit 939a642)

* Fix `cherry-pick` error.

* Fix merge errors.

Co-authored-by: Kibana Machine <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Deprecated - use backport:version if exact versions are needed bug Fixes for quality problems that affect the customer experience release_note:fix Team:Uptime - DEPRECATED Synthetics & RUM sub-team of Application Observability v7.17.0 v8.0.0 v8.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Uptime] Explore data button on Uptime Overview filters by a specific monitor
5 participants