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

Set relative date for host details link in onboarding flow #205622

Merged
merged 1 commit into from
Jan 7, 2025

Conversation

mykolaharmash
Copy link
Contributor

@mykolaharmash mykolaharmash commented Jan 6, 2025

This change sets a relative date range to the host details link from the auto-detect onboarding flow. This prevents a situation when host details page would open saying there is no data and it would be stuck on a fixed date range unable to load data even if user refreshes the page.

Somehow, even when onboarding flow can detect that the data was already ingested, the host details page might not see it for some reason. This requires a further investigation, but relative data range is a fix for the time being.

@mykolaharmash mykolaharmash requested a review from a team as a code owner January 6, 2025 15:57
@mykolaharmash mykolaharmash added backport:skip This commit does not require backporting backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) Team:obs-ux-logs Observability Logs User Experience Team and removed backport:skip This commit does not require backporting labels Jan 6, 2025
@elasticmachine
Copy link
Contributor

Pinging @elastic/obs-ux-logs-team (Team:obs-ux-logs)

@mykolaharmash mykolaharmash added the release_note:skip Skip the PR/issue when compiling release notes label Jan 6, 2025
@@ -183,6 +183,12 @@ export const AutoDetectPanel: FunctionComponent = () => {
href: assetDetailsLocator.getRedirectUrl({
assetType: 'host',
assetId: integration.metadata?.hostname,
assetDetails: {
Copy link
Contributor

Choose a reason for hiding this comment

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

What is the current default time range?

Copy link
Contributor Author

@mykolaharmash mykolaharmash Jan 7, 2025

Choose a reason for hiding this comment

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

Also from -15 minutes to now, but it was not relative, once user navigated to the page it would get converted to an absolute timestamp and never change

@elasticmachine
Copy link
Contributor

💚 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
observabilityOnboarding 269.8KB 269.8KB +51.0B

@mykolaharmash mykolaharmash merged commit 212b192 into elastic:main Jan 7, 2025
18 checks passed
@kibanamachine
Copy link
Contributor

Starting backport for target branches: 8.x

https://github.com/elastic/kibana/actions/runs/12649643522

kibanamachine pushed a commit to kibanamachine/kibana that referenced this pull request Jan 7, 2025
…05622)

This change sets a relative date range to the host details link from the
auto-detect onboarding flow. This prevents a situation when host details
page would open saying there is no data and it would be stuck on a fixed
date range unable to load data even if user refreshes the page.

Somehow, even when onboarding flow can detect that the data was already
ingested, the host details page might not see it for some reason. This
requires a further investigation, but relative data range is a fix for
the time being.

(cherry picked from commit 212b192)
@kibanamachine
Copy link
Contributor

💚 All backports created successfully

Status Branch Result
8.x

Note: Successful backport PRs will be merged automatically after passing CI.

Questions ?

Please refer to the Backport tool documentation

kibanamachine added a commit that referenced this pull request Jan 7, 2025
…5622) (#205698)

# Backport

This will backport the following commits from `main` to `8.x`:
- [Set relative date for host details link in onboarding flow
(#205622)](#205622)

<!--- Backport version: 9.4.3 -->

### Questions ?
Please refer to the [Backport tool
documentation](https://github.com/sqren/backport)

<!--BACKPORT [{"author":{"name":"Mykola
Harmash","email":"[email protected]"},"sourceCommit":{"committedDate":"2025-01-07T10:22:07Z","message":"Set
relative date for host details link in onboarding flow (#205622)\n\nThis
change sets a relative date range to the host details link from
the\r\nauto-detect onboarding flow. This prevents a situation when host
details\r\npage would open saying there is no data and it would be stuck
on a fixed\r\ndate range unable to load data even if user refreshes the
page.\r\n\r\nSomehow, even when onboarding flow can detect that the data
was already\r\ningested, the host details page might not see it for some
reason. This\r\nrequires a further investigation, but relative data
range is a fix for\r\nthe time
being.","sha":"212b1926743ca5821992c2877d9c68f621e1875e","branchLabelMapping":{"^v9.0.0$":"main","^v8.18.0$":"8.x","^v(\\d+).(\\d+).\\d+$":"$1.$2"}},"sourcePullRequest":{"labels":["release_note:skip","v9.0.0","backport:prev-minor","Team:obs-ux-logs"],"title":"Set
relative date for host details link in onboarding
flow","number":205622,"url":"https://github.com/elastic/kibana/pull/205622","mergeCommit":{"message":"Set
relative date for host details link in onboarding flow (#205622)\n\nThis
change sets a relative date range to the host details link from
the\r\nauto-detect onboarding flow. This prevents a situation when host
details\r\npage would open saying there is no data and it would be stuck
on a fixed\r\ndate range unable to load data even if user refreshes the
page.\r\n\r\nSomehow, even when onboarding flow can detect that the data
was already\r\ningested, the host details page might not see it for some
reason. This\r\nrequires a further investigation, but relative data
range is a fix for\r\nthe time
being.","sha":"212b1926743ca5821992c2877d9c68f621e1875e"}},"sourceBranch":"main","suggestedTargetBranches":[],"targetPullRequestStates":[{"branch":"main","label":"v9.0.0","branchLabelMappingKey":"^v9.0.0$","isSourceBranch":true,"state":"MERGED","url":"https://github.com/elastic/kibana/pull/205622","number":205622,"mergeCommit":{"message":"Set
relative date for host details link in onboarding flow (#205622)\n\nThis
change sets a relative date range to the host details link from
the\r\nauto-detect onboarding flow. This prevents a situation when host
details\r\npage would open saying there is no data and it would be stuck
on a fixed\r\ndate range unable to load data even if user refreshes the
page.\r\n\r\nSomehow, even when onboarding flow can detect that the data
was already\r\ningested, the host details page might not see it for some
reason. This\r\nrequires a further investigation, but relative data
range is a fix for\r\nthe time
being.","sha":"212b1926743ca5821992c2877d9c68f621e1875e"}}]}]
BACKPORT-->

Co-authored-by: Mykola Harmash <[email protected]>
kowalczyk-krzysztof pushed a commit to kowalczyk-krzysztof/kibana that referenced this pull request Jan 7, 2025
…05622)

This change sets a relative date range to the host details link from the
auto-detect onboarding flow. This prevents a situation when host details
page would open saying there is no data and it would be stuck on a fixed
date range unable to load data even if user refreshes the page.

Somehow, even when onboarding flow can detect that the data was already
ingested, the host details page might not see it for some reason. This
requires a further investigation, but relative data range is a fix for
the time being.
CAWilson94 pushed a commit to CAWilson94/kibana that referenced this pull request Jan 13, 2025
…05622)

This change sets a relative date range to the host details link from the
auto-detect onboarding flow. This prevents a situation when host details
page would open saying there is no data and it would be stuck on a fixed
date range unable to load data even if user refreshes the page.

Somehow, even when onboarding flow can detect that the data was already
ingested, the host details page might not see it for some reason. This
requires a further investigation, but relative data range is a fix for
the time being.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport:prev-minor Backport to (8.x) the previous minor version (i.e. one version back from main) release_note:skip Skip the PR/issue when compiling release notes Team:obs-ux-logs Observability Logs User Experience Team v8.18.0 v9.0.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants