-
Notifications
You must be signed in to change notification settings - Fork 8.1k
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
[Logs Onboarding] System logs onboarding flow #154929
Labels
8.10 candidate
apm:test-plan-8.10.0
APM UI Test Plan for v8.10.0
apm:test-plan-done
Pull request that was successfully tested during the test plan
design
Feature:Logs Onboarding
Logs Onboarding feature
Team:obs-ux-logs
Observability Logs User Experience Team
Comments
Pinging @elastic/apm-ui (Team:APM) |
This was referenced Jul 26, 2023
ogupte
added a commit
to ogupte/kibana
that referenced
this issue
Jul 27, 2023
yngrdyn
pushed a commit
that referenced
this issue
Aug 1, 2023
This addresses the UI code required for #154929. The API work can be accomplished separately. The existing APIs (for custom logs) are used in their place for this PR. ![Screenshot 2023-07-27 at 13 03 50](https://github.com/elastic/kibana/assets/1967266/f27a2063-822a-4169-bd98-f22985661349) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
This was
linked to
pull requests
Aug 1, 2023
ThomThomson
pushed a commit
to ThomThomson/kibana
that referenced
this issue
Aug 1, 2023
…re generic (elastic#162706) This PR is a preparation work for elastic#154929. ### Changes: - Rearranged code to make routes more generic (Most of the changes). - Added `type` to onboarding savedObject. - Removed `status` route since it was not being used.
ThomThomson
pushed a commit
to ThomThomson/kibana
that referenced
this issue
Aug 1, 2023
…tic#162654) This addresses the UI code required for elastic#154929. The API work can be accomplished separately. The existing APIs (for custom logs) are used in their place for this PR. ![Screenshot 2023-07-27 at 13 03 50](https://github.com/elastic/kibana/assets/1967266/f27a2063-822a-4169-bd98-f22985661349) --------- Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
yngrdyn
added a commit
that referenced
this issue
Aug 4, 2023
…62972) Closes #154929. This PR along with #162654, #162706 and #162600 completes the work required for collect system logs. ### Changes - `ObservabilityOnboardingType` now could be `logFiles | systemLogs`. This help us to identify (without changing the script) whether we need to retrieve the yaml configuration for customLogs or for systemLogs. - Added `generateSystemLogsYml` which generates a specific configuration for system logs. - `get_has_logs.ts` was modified so we are querying the proper index depending on the type of logs. #### Demo https://github.com/elastic/kibana/assets/1313018/47eca890-37b2-401e-9e41-67c978ab50ad
This was tested in o11y-test qa serverless environmnet. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
8.10 candidate
apm:test-plan-8.10.0
APM UI Test Plan for v8.10.0
apm:test-plan-done
Pull request that was successfully tested during the test plan
design
Feature:Logs Onboarding
Logs Onboarding feature
Team:obs-ux-logs
Observability Logs User Experience Team
The system logs flow for logs onboarding should be implemented based on the existing design. The user should be guided having no logs through the steps to configure streaming system logs via elastic agent. Then the user waits for the agent to be set up and logs to be ingested before directing them to logs exploration / Discover.
Step 1 - System logs as a card in the Observability landing page
![Image](https://user-images.githubusercontent.com/121812915/235875289-e56630e4-d3b6-4bdb-a93e-7a98bc5e521c.png)
Step 2 - Install shipper
![Image](https://user-images.githubusercontent.com/121812915/235874717-6efe58a6-65fe-4848-be04-71fd292564df.png)
Step 3 - Collect logs
![Image](https://user-images.githubusercontent.com/121812915/235875607-85a5d708-7cd2-4711-89ec-e154ba84bde3.png)
The text was updated successfully, but these errors were encountered: