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

[Discover] Add responsive layout #8

Conversation

andreadelrio
Copy link
Collaborator

@andreadelrio andreadelrio commented Sep 28, 2020

Summary

  • Added a flyout which shows the content of the sidebar in mobile
  • Added Fields button to trigger flyout
  • Added EuiAccordions for Available Fields and Selected Fields (@kertal can you please double check that the implementation is correct, it seems like they do something a bit more complex in Lens).

image 45

ezgif com-resize

Notes:

  • @kertal need your help with making the selected field counter in the Fields button work. Note that if there are no fields selected it should say 0. Thanks :)
  • The file discover_sidebar_mobile.tsx could likely be simplified and cleaned up.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

For maintainers

@andreadelrio
Copy link
Collaborator Author

@kertal Added some improvements for the Expanded Document flyout on mobile (still room for more improvements). It'd be great to change that table to use EuiTable at some point, not a priority but good to keep it in mind.
image 45

@kertal
Copy link
Owner

kertal commented Sep 29, 2020

@kertal Added some improvements for the Expanded Document flyout on mobile (still room for more improvements). It'd be great to change that table to use EuiTable at some point, not a priority but good to keep it in mind.
image 45

Nice, yes, so the actions are already visible, and users don't need to 'discover' them. Wonder if it makes sense to do this by default? it was handled that way in older Kibana versions.
image

However it's more a question of taste. +1 for EuiTable here in a later step

Comment on lines 191 to 203
<EuiAccordion
id="dscSelectedFields"
initialIsOpen={true}
buttonContent={
<EuiText size="xs">
<strong>
<FormattedMessage
id="discover.fieldChooser.filter.selectedFieldsTitle"
defaultMessage="Selected fields"
/>
</strong>
</EuiText>
}
Copy link
Owner

Choose a reason for hiding this comment

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

Heavy +1 for removing this legacy stuff and moving to EuiAccordion
I think badges like in Lens displaying how much fields are available / selected would be useful for the user:
Bildschirmfoto 2020-09-29 um 12 47 59

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@kertal I added the badges, not sure how we would handle the case where there's Filters by type on? In Lens they show the badge with the accent color if there are filters on. Would we want to do something similar in Discover? if so, how do we implement that?

See
https://github.com/elastic/kibana/blob/9a9a8b0c32fa808b83f891a2cd7f98b80c2bd57b/x-pack/plugins/lens/public/indexpattern_datasource/fields_accordion.tsx#L105

Copy link
Owner

Choose a reason for hiding this comment

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

sounds good, I'll have a look at lens

Copy link
Owner

Choose a reason for hiding this comment

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

I think we should adapt the lens behavior
easiest way to find out whether a filter is active or not would be using lodash isEqual like this:

const filterChanged = isEqual(fieldFilterState, getDefaultFieldFilter());

@andreadelrio
Copy link
Collaborator Author

@kertal Added some improvements for the Expanded Document flyout on mobile (still room for more improvements). It'd be great to change that table to use EuiTable at some point, not a priority but good to keep it in mind.
image 45

Nice, yes, so the actions are already visible, and users don't need to 'discover' them. Wonder if it makes sense to do this by default? it was handled that way in older Kibana versions.
image

However it's more a question of taste. +1 for EuiTable here in a later step

We usually avoid showing repetitive icons in multiple rows (e.g. table) in order not to overcrowd the UI. In mobile we make them visible at all times because there's no hovering. It's the same reasoning why we only show the add/remove icons in the sidebar upon hovering (on desktop).

@kertal
Copy link
Owner

kertal commented Sep 30, 2020

We usually avoid showing repetitive icons in multiple rows (e.g. table) in order not to overcrowd the UI. In mobile we make them visible at all times because there's no hovering. It's the same reasoning why we only show the add/remove icons in the sidebar upon hovering (on desktop).

@andreadelrio thx for the context!

@kertal
Copy link
Owner

kertal commented Sep 30, 2020

I've playing around with this PR, and it works pretty well 👍 . One thing that breaks and that's no surprise is the legacy grid view, sidebar doesn't show fields at certain dimensions (we could fix that in a follow up). So I wonder, do you think, also the legacy grid would work in this layout, it's now a react component with angular under the hood, so it can be used like datagrid in the new responsive layout? and could be solve the collapsing/uncollapsing of the sidebar like it is solved today?

button to expand / unfold:

https://github.com/elastic/kibana/blob/a21a8325423fb9aafcf04c7d1f64df079aeb21d1/src/plugins/discover/public/application/components/discover_legacy.tsx#L194

state:

https://github.com/elastic/kibana/blob/a21a8325423fb9aafcf04c7d1f64df079aeb21d1/src/plugins/discover/public/application/components/discover_legacy.tsx#L122

this may be out of scope of this PR, just wonder if could continue in a direction to have one layout with 2 different grids , lot's of legacy removed , goodbye bootstrap!

@andreadelrio
Copy link
Collaborator Author

I've playing around with this PR, and it works pretty well 👍 . One thing that breaks and that's no surprise is the legacy grid view, sidebar doesn't show fields at certain dimensions (we could fix that in a follow up). So I wonder, do you think, also the legacy grid would work in this layout, it's now a react component with angular under the hood, so it can be used like datagrid in the new responsive layout? and could be solve the collapsing/uncollapsing of the sidebar like it is solved today?

button to expand / unfold:

https://github.com/elastic/kibana/blob/a21a8325423fb9aafcf04c7d1f64df079aeb21d1/src/plugins/discover/public/application/components/discover_legacy.tsx#L194

state:

https://github.com/elastic/kibana/blob/a21a8325423fb9aafcf04c7d1f64df079aeb21d1/src/plugins/discover/public/application/components/discover_legacy.tsx#L122

this may be out of scope of this PR, just wonder if could continue in a direction to have one layout with 2 different grids , lot's of legacy removed , goodbye bootstrap!

@kertal did some cleanup of the legacy file to remove Bootstrap and reuse what we have in the datagrid version. The collapse button works 👍, don't want to spend too much time on it because it will be replaced by the features coming to EuiResizableContainer anyways. One thing, the flyout is not opening in mobile legacy, would you mind taking a look?

@kertal
Copy link
Owner

kertal commented Oct 1, 2020

@kertal did some cleanup of the legacy file to remove Bootstrap and reuse what we have in the datagrid version. The collapse button works 👍, don't want to spend too much time on it because it will be replaced by the features coming to EuiResizableContainer anyways. One thing, the flyout is not opening in mobile legacy, would you mind taking a look?

Excellent work! I just wanted to ask if it's possible. Will have a look!

let flyout;

if (isFlyoutVisible) {
flyout = (
Copy link
Owner

Choose a reason for hiding this comment

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

I think it's not displayed, because the flyout variable isn't used here, just assigned. Btw, would be neat to have a separate flyout react component, to deduplicate code ... but could also be done later

@andreadelrio
Copy link
Collaborator Author

Updated loading screens

Mobile
image 49
Desktop - legacy
image 48
Desktop - data grid
image 47

@kertal
Copy link
Owner

kertal commented Oct 5, 2020

@andreadelrio looks very nice, is it ready for final review/merge? thx

@andreadelrio
Copy link
Collaborator Author

@andreadelrio looks very nice, is it ready for final review/merge? thx

@kertal, yes! should be ready to go. Thanks!

@kertal
Copy link
Owner

kertal commented Oct 5, 2020

there's a problem with the legacy layout sidebar, it scales to the height of the main content, which doesn't work well when this section is low, second problem is the no results section. tried to solve it but didn't find a good solution so far
Bildschirmfoto 2020-10-05 um 13 38 31

@andreadelrio
Copy link
Collaborator Author

there's a problem with the legacy layout sidebar, it scales to the height of the main content, which doesn't work well when this section is low, second problem is the no results section. tried to solve it but didn't find a good solution so far
Bildschirmfoto 2020-10-05 um 13 38 31

This should be fixed now
image

@kertal
Copy link
Owner

kertal commented Oct 6, 2020

Thx for making those changes 👍
So, the new layout is perfect! But in legacy layout there are still issues (that's why it's called legacy ... another word for issue)

There is an "infinite scroll" functionality in legacy table, which renders the rows in batches, so when you scroll down, more and more rows are rendered. It takes the window height and scrollTop to determine how much to render. since now the height of the window (more the document, but it's labeled $window in angular) doesn't change. this functionality is broken (it should render 500 docs if the available doc count is >= 500, currently just a part of it are rendered). So my question is, if there's a way to change CSS to ? if not, I'm sure I can adapt this rusty old angular directive to work with a scrollable div element

Second thing that I've noticed is related to vertical sizing when there are just few table rows:
Bildschirmfoto 2020-10-06 um 16 59 15

I think the histogram in legacy world shouldn't be sticky, although it looks nice. Because users already complain about it's screen size and how to remove it, and are happy when we tell them, that we're working on it

sorry that legacy world is so hostile

@andreadelrio
Copy link
Collaborator Author

sorry that legacy world is so hostile

Agreed haha.

So I fixed the vertical sizing one but the infinite scrolling is not working yet :/

@kertal
Copy link
Owner

kertal commented Oct 7, 2020

So I fixed the vertical sizing one but the infinite scrolling is not working yet :/

this is a deep dive into legacy code with Angular 🐟 and jQuery 🐠 involved so I'm 🎣

@kertal
Copy link
Owner

kertal commented Oct 7, 2020

fixed the infinite scrolling (now there are 2 elements scrollable, depending on screen size, looking forward to remove all this)

then I've solved this, just in safari
Bildschirmfoto 2020-10-07 um 15 24 32
adapted it to the new layout, histogram is now also removeable
Bildschirmfoto 2020-10-07 um 15 34 45
could you have a final look? thx

@kertal kertal self-requested a review October 7, 2020 15:49
Copy link
Owner

@kertal kertal left a comment

Choose a reason for hiding this comment

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

Code LGTM, many thanks for taking care of this 🐰 hole!

@andreadelrio andreadelrio merged commit fbd920a into kertal:kertal-pr-2020-04-25-discover-data-grid Oct 7, 2020
kibanamachine added a commit that referenced this pull request Nov 8, 2022
* Updated EUI to version 67.1.2. Updated instaces of ButtonColor from EUI to EuiButtonColor.

* Updated to EuiCard instances that utilize the betaBadgeProps object to return an empty string instead of undefined when the label is unavailable

* Removed two instances of the deprecated internetExplorerOnly() mixin

* Updated two instances of the ButtonColor import to EuiButtonColor as is was renamed in PR elastic#6150

* Updated snapshots in Jest Test Suite #1 to account for EuiButton and EuiCard Emotion conversions. Updated snapshots for EuiTooltip as it now contains the new EuiToolTipAnchor component that replaced the tooltip anchor styles

* Updated snapshots in Jest Test Suite #2 to account forEuiButton, EuiDescriptionList, EuiButtonIcon, and EuiBadge Emotion conversions.

* Updated snapshots in Jest Test Suite #3 to account for EuiDescriptionList, EuiButton, and EuiBadge Emotion conversions. Updated snapshots for EuiTooltip as if now contains the new EuiTooltipAnchor component that replaced the tooltop anchor styles

* Updated snapshots in Jest Test Suite #4 to account for EuiButton Emotion conversion.

* Updated snapshots in Jest Test Suite #5 to account for EuiButton Emotion conversion.

* Updated snapshots in Jest Test Suite #8 to account for EuiButtonIcon and EuiButton Emotion conversions. Updated snapshots for EuiTooltip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles.

* Updated snapshots in Jest Test Suite #9 to account for EuiFlyout and EuiButton Emotion conversions.

* Updated snapshots in Jest Test Suite #10 to account for EuiButton, EuiBadge, EuiButtonIcon, and EuiCard Emotion conversions. Updated snapshots for EuiToolTtip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles

* Updated instances of EuiButtonIconColor to use EuiButtonIconProps['color'] as it was removed in PR elastic#6150

* Updated tests that target EuiButton to simulate click events to target a generic button to prevent undefined click event errors

* Updated snapshots in Jest Test Suite #1 to account for EuiButton and EuiCard Emotion conversions

* Added the EuiFlyout mixins and variables to Lens Sass file as EuiFlyout has been converted to Emotion and the Sass styles are no longer available in EUI

* Added the EuiCallOutTypes variable to Step Progress Sass file as EuiCallOut has been converted to Emotion and the Sass styles are no longer available in EUI

* Updated snapshots in Jest Test Suite #2 to account for recent Emotion conversions.
Updated snapshots in server_status.test.tsx to render EuiBadge before checking the snapshots to reduce the snapshot churn caused by Emotion.
Updated tests that target EuiButton to simulate click events to target a generic button to prevent undefined click event errors

* [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix'

* Added imports for the added flyout mixin. Removed references to EuiCallOut mixin as the component has been converted to Emotion and is no longer available for use.

* Updated unit tests and snapshots in Jest Test Suite #10.
Updated snaphshots to account for EuiBadge, EuiDescriptionList, EuiFlyout, and EuiCard Emotion conversions. Updated snapshots for EuiTooltip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles.
Updated tests that target EuiButton to simulate click events to target a generic button element to prevent undefined click event errors

* Updated unit tests in Jest Test Suite #11 that target EuiButton to simulate click events to target a generic button to prevent undefined click event errors

* Updated unit tests in Jest Test Suite #12 by updating tests that target EuiButton to simulate click events. Instead, these tests now target a generic button element to prevent undefined click event errors

* Updated unit tests in Jest Test Suite #1 by updating tests that target EuiButton to simulate click events. Instead, these tests now target a generic button element to prevent undefined click event errors

* Updated unit tests in Jest Test Suite #2 by updating tests that use EuiButton to simulate click events. Instead, these test have been updated to target a button element to prevent undefined click event errors.

* [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'

* Updated reference to mixins Sass file.
Updated snapshots for Jest Test Suite #5 to account for EuiButton Emotion conversion. Updated unit tests that target EuiButton to simulate click events. These tests have been updated to target a button element to prevent undefined click event errors

* Updated unit tests in Jest Test Suites 3, 7, 8, 13, and 14.
Updated snapshot to account for EuiButton Emotion conversion.
Updated tests that target EuiButton to simulate click events. These tests now target a generic button element to prevent undefined click event errors.
Updated a few snapshots by adding .render() before checking the snapshot. This will prevent large snapshots coming from recent Emotion conversions

* Updated snapshots in Jest Test Suite #10 to account for the recent EuiButton Emotion conversion

* Updated unit tests in Jest Test Suite #2 by editing tests that target EuiButton to simulate click events. These tests now target a button element in order to prevent undefinde click event errors

* Updated snapshots in Jest Test Suite #10 to account for EuiButton and EuiDescriptionList Emotion conversions

* Updated test cases in Jest Test Suites 3, 7, and 8. Updated snapshots to account for EuiButton and EuiPagination Emotion conversions.
Updated tests that target EuiButton to simulate click events. These tests now target a button element to prevent undefined click errors

* Updated test cases in Jest Test Suite 14. Updated snapshots to account for EuiButton Emotion conversion. Opted to use .render() when updating a few snapshots to reduce the large length of snapshots caused by Emotion

* [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'

* Revised a change to betaBadgeProps to ensure that the label is available. If not, the value for the badge with be set to undefined.

* Resolved two linting errors

* Resolved two linting errors

* Updated Jest unit tests in various suites.
Updated snapshots to account for EuiButton Emotion conversion. Updated snapshots for EuiTooltip as it now contains the new EuiTooltipAnchor component that replaced the tooltip anchor styles.

* Updated EuiFlyout in query_flyout.tsx to remove the onClick function from maskProps as it is no longer available. Updated this flyout to use ownFocus and not to close when the overlay mask is clicked.

* Removed the use of EuiButtonIconColor in favor of EuiButtonIconProps['color']

* [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'

* Updated Cypress test looking for strict equality on EuiPaginationButton class names to match a substring of the Emotion generated class name

* Removed unneeded debugging code. Updated snapshots for various test suites to account for the recent EuiButton Emotion conversion

* Updated a few EuiButton, EuiButtonEmpty, and EuiText components that set the color as ghost. The ghost color mode has been deprecated as of PR elastic#6150. These components now are wrapped in EuiThemeProvider with a dark colorMode to create the previous ghost color.

* Resolved  TS error with EuiCard betaBadgeProps

* [CI] Auto-commit changed files from 'node scripts/eslint --no-cache --fix'

* Remove references to now-removed EuiFlyout CSS classes/vars

* Remove now-removed euiBadge className references

- Convert directly to EuiBadge instead of using CSS

- Remove confusing and now-possibly-irrelevant CSS badge overrides - left/right icons are now set via JSX and not via flex-direction

* Pre-emptively fix various euiOverlayMask CSS overrides

- this data attr isn't technically in yet but will be once elastic/eui#6289 merges

- at the very least this isn't breaking any more than it currently already is!

* Update to v67.1.3

* v67.1.4

* Resolved test failing test case in Security/Manage/Blocklist. The test did not remove focus from the last combo box in the form, which didn't allow the disbaled attribute to be removed from the flyout submit button. I've updated the mock file for Blocklist to return focus to the first form element in the flyout to allow the disabled attribute to be removed.

* Updated snapshots to account for the recent EuiText Emotion conversion

* Fix Log's custom tooltips relying on EuiTooltip classNames that no longer exist

* Fix Vega vis custom tooltips relying on EuiTooltip classNames that no longer exist

- this one is trickier than Log's as it's not using React, so we need to use Emotion's Global to set a static className

* Convert remaining vega_vis.scss to Emotion

- as an example of how other global + non global styles could be handled in the future

* Fix references to removed `euiPaginationButton-isActive` className

- use aria-current attribute instead

* Added missing EuiFlyoutAnimation keyframes for EuiFlyout. This resolved test that failed because they used onAnimationEnd because the FlyoutAnimation could not be found.

* Reolved Jest Tests in suites 1 and 5. Updated snapshots to account for the recent EuiButton Emotion conversion. Updated snapshots for EuiToolTip as it now contains the new EuiToolTipAnchor component that replaced the tooltip anchor styles.

* iterate on rules_list.test.tsx

* bump eui to v67.1.5

* Updatde snapshots for jest test suites to account for the recent EuiButton, EuiOverlayMask, EuiTooltip, and EuiBadge Emotion conversions

* Resolved failing security test by updating the target element for CONNECTOR_TITLE. EuiCard has recently been converted to Emotion and the card title is no longer wrapper in a span.

* Resolved failing test case in Runtime Fields. The modify runtime field test was failing because the combobox responsbible for adding and updating scripts was not appearing. The textbox did not appear because the shared setFieldScript function targets and toggles the script textbox when opening the flyout. When a runtime field is being modified, the toggle is already active and using the shared function will trigger the toggle again (losing access to the script textbox).
Also resolved an issue that prevented the warning EuiCallout to appear when changing the type of a runtime field from its original type. Resolved this by adding an enter keypress at the end of setFieldType function to confirm the type selection, thus triggering the EuiCallout

* Resolved two tests that were failing in Lens. These test were failing because they were checking for equality in class names that no longer exist within EuiButtonGroup as it was recently converted to Emotion. These tests were updated to check for a substring of the new and longer class name

* Quick fix in test case failing because of misspelling in data-test-sub

* Updated snapshot for Jest test case as EuiButton as recently been converted to Emotion

* Removed console.log statement. Oops!

* Resolved a failing test case in Lens. They were failing because they were checking for equality in class names that no longer exist within EuiButtonGroup as it was recently converted to Emotion. These tests were updated to check for a substring of the new and longer class name.
Updated a Security test case by giving a target button the data-test-subj attribute for easier querying

* Removed reference to EuiFlyout mixin as it has been converted to Emotion. Updated the reference to an interal copy of EuiFlyout styles

* Corrected spelling error in EuiFlyout animation in Lens app

* Update EUI with latest backport

* Update button snapshots

* fix another button snapshot

* More snapshot fixes

* [EuiButton][Security] Fix button relying on now-removed `euiButton__text` CSS

- replace removed CSS with `eui-textTruncate` util instead

- combine/DRY out unnecessary span - was affecting min-width of truncation util

+ increase screenshot diff limit - this was smaller than updating the actual baseline screenshots for whatever reason (likely render diff between local and CI)

* Fix remaining Jest tests affected by Emotion conversions

- because Emotion creates its own wrapper, `.first()` can no longer be used - prefer `.last()` instead

* Fix Jest test affected by EuiButton Emotion conversion + removed modifier class

- targeting the native DOM node + filtering by disabled true/false gets us back to the 'correct' lengths

* Fix + improve flyout test

- `.last()` changes to account for EuiButton Emotion conversion is needed, but the last onClose assertion still fails due to us having modified inputs, and the confirm modal being displayed

- split test into two separate tests - one testing the onClose call, and the other testing the confirm modal

* derpin

* Skip rules_list Jest suite

* Update new EuiButton snapshot

* Upgraded EUI version to 67.1.7

* [EuiCard] Update snapshots

* [EuiPopover] Update snapshots

* [QA] Fix missing Vega warn/error message colors

;_;

* [CI] Auto-commit changed files from 'node scripts/generate codeowners'

* Fix Lens kbnToolbarButton regressions

- Caused by flattening of EUI button CSS specificity

- background-color was previously relying on isDisabled CSS specificity to override its #fff color

- `text` color modifier & `!important` is no longer needed and overrides Emotion CSS flatly

- isDisabled class is no longer needed - euiButton no longer sets `pointer-events: none` on disabled buttons (fixes tooltip bug in webkit as well)

* Backport EUI 67.1.8 fixes

* Update EuiCard snapshots

* Fix EuiModal form wrapper causing overflow issues

- see https://elastic.github.io/eui/#/layout/modal#forms-in-a-modal

* Workaround for `.kbnOverlayMountWrapper` mount point causing overflow issues

- not sure what all is using this modal service to be honest, but the wrapper is causing issues with the modal layout, this fixes overflow issues but will not fix any mask-image issues as a result

* more snapshot updates

* EuiButton - added textProps to EuiButton to prevent very long button names from spilling over outside of the container

* EuiButton - Update EuiButton related snapshots. Updated tests that target EuiButton directly to use a data-telementary-id for more specific element querying required by Emotion

* QA - Removed unnecessary comment in code

* Temporary fix for EuiCard[selectable][layout=horizontal] instances on security solutions' rule page

* Temporary fix for EuiCard[selectable][layout=horizontal] instances on osquery live query and canvas's datasource selector

* [CI] Auto-commit changed files from 'node scripts/precommit_hook.js --ref HEAD~1..HEAD --fix'

* Fix CSS specificity, where canvas's solutionToolbarButton's background-color now takes precedence over EuiButton's primary styles

* Removed update to search_marker_tooltip that removed the euiTooltip styles and replaced then with Emotion styling. Added EuiTooltip Sass styles for the component to rely on to test for a styling bug that is causing the tooltip and the tooltip arrow to be out of sync with each other.

* Lint Sass file

* Lint Sass file

* Removed overflow:hidden style from .vgaVis_view as it was causing euiScrollStyles not to present the scroll bars in Vega Vis

* Remove typo from EuiButton textProps object. 'className' should not have been included in the actual class name

* Revert tooltip Sass

This reverts commit 20e6ead, a5cd2de, and c605cbd

* Fix Emotion tooltip arrows

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Constance Chen <constance.chen@elastic.co>
Co-authored-by: Chandler Prall <chandler.prall@elastic.co>
kertal pushed a commit that referenced this pull request Sep 6, 2024
fixes
[#8](elastic/observability-accessibility#8)
fixes
[#7](elastic/observability-accessibility#7)
 
## Summary

Fixes APM breadcrumbs on serverless

| Serverless  |  Stateful  |
|---|---|
| <img width="700px" alt="image"
src="https://github.com/user-attachments/assets/944a7d58-7de3-4a7f-be02-3c8c1110a0e2">
|<img width="800px" alt="image"
src="https://github.com/user-attachments/assets/450664b1-ddfc-4395-9fa3-a7b941affb3b">|
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/944a7d58-7de3-4a7f-be02-3c8c1110a0e2">
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/450664b1-ddfc-4395-9fa3-a7b941affb3b">|
| <img width="500px" alt="image"
src="https://github.com/user-attachments/assets/944a7d58-7de3-4a7f-be02-3c8c1110a0e2">
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/cb8a39e2-ca33-4cf9-a8ac-4c84566d092d">|
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/151a3a9c-c81e-4558-9d00-e695e3d1d79c">|<img
width="500px" alt="image"
src="https://github.com/user-attachments/assets/2562e96f-d5e4-4aa4-a221-6721f8995883">|
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/8d877d11-8c3f-4ac5-8146-6a11125eae7c">|<img
width="500px" alt="image"
src="https://github.com/user-attachments/assets/36e588cb-4c18-4d66-a2c6-f0e66392f708">|
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/14253196-06de-4343-811f-61aa31ea0d1e">|<img
width="500px" alt="image"
src="https://github.com/user-attachments/assets/0cdfc83f-6545-433f-8c14-5bbf2a581175">|
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/89a58e2b-2cef-4188-b2be-f359ba6890db">|<img
width="500px" alt="image"
src="https://github.com/user-attachments/assets/f15e767f-5b60-4485-ac71-7b6fd850ec50">|
|<img width="500px" alt="image"
src="https://github.com/user-attachments/assets/a0f7bfae-bfda-4f49-b92a-e736d80fea4c">|<img
width="500px" alt="image"
src="https://github.com/user-attachments/assets/680db8ab-58b8-454b-a0d7-6e1681dbe616">|


### How to test
#### Serverless
- Start a local ES serverless instance: `yarn es serverless
--projectType=oblt --ssl -k/--insecure`
- Start a local Kibana serverless instance: ` yarn start
--serverless=oblt --no-ssl`
- Run some synthtrace scenarios
- `NODE_TLS_REJECT_UNAUTHORIZED=0 node scripts/synthtrace mobile.ts
--live --target=https://elastic_serverless:changeme@127.0.0.1:9200
--kibana=http://elastic_serverless:changeme@0.0.0.0:5601`
- `NODE_TLS_REJECT_UNAUTHORIZED=0 node scripts/synthtrace service_map.ts
--live --target=https://elastic_serverless:changeme@127.0.0.1:9200
--kibana=http://elastic_serverless:changeme@0.0.0.0:5601`
- Navigate to Applications and click through the links

### Stateful
- Start a local ES and Kibana instance
- Run the some synthtrace scenarios:
  -  `node scripts/synthtrace mobile.ts --live`
  -  `node scripts/synthtrace service_map.ts --live`
- Navigate to Applications and click through the links

---------

Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants