TRACING-5579: Support custom time range

[andreasgerstmayr]

Replace the custom <DurationDropdown> with <TimeRangeControls> from Perses, which supports selecting a custom time range. Additionally, use <TimeRangeProviderWithQueryParams> instead of <TimeRangeProvider> to let Perses manage the query params handling.

[openshift-ci-robot]

@andreasgerstmayr: This pull request references TRACING-5579 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Replace the custom <DurationDropdown> with <TimeRangeControls> from Perses, which supports selecting a custom time range. Additionally, use <TimeRangeProviderWithQueryParams> instead of <TimeRangeProvider> to let Perses manage the query params handling.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[andreasgerstmayr]

AssertionError: Timed out retrying after 40000ms: Expected to find content: 'Last 30 minutes' within the element: <div.pf-v6-c-menu-toggle.pf-m-full-width.pf-m-typeahead> but never did.

@IshwarKanse could you update the e2e test? The HTML structure changed as I'm using the component from Perses now.

[IshwarKanse]

@andreasgerstmayr Ack, will do.

[IshwarKanse]

/test upstream-amd64-aws-e2e

[IshwarKanse]

/test upstream-amd64-aws-e2e

[IshwarKanse]

@andreasgerstmayr Updated the tests, the job is passing now.

[IshwarKanse]

@andreasgerstmayr Are we cherry-picking all the recent PRs to release-1.0 and 0.4 branch ?

[andreasgerstmayr]

@andreasgerstmayr Are we cherry-picking all the recent PRs to release-1.0 and 0.4 branch ?

Yes, I'll do that in a single PR per branch, once all current PRs are merged.

[IshwarKanse]

/label qe-approved

[openshift-ci-robot]

@andreasgerstmayr: This pull request references TRACING-5579 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.21.0" version, but no target version was set.

In response to this:

Replace the custom <DurationDropdown> with <TimeRangeControls> from Perses, which supports selecting a custom time range. Additionally, use <TimeRangeProviderWithQueryParams> instead of <TimeRangeProvider> to let Perses manage the query params handling.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[zhuje]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: andreasgerstmayr, zhuje

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [andreasgerstmayr,zhuje]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[andreasgerstmayr]

/label ux-approved
same UX as in the monitoring view

[openshift-ci]

@andreasgerstmayr: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.