## Summary
This PR changes the KPI colors to a more neutral color scheme.
| Before | After |
| ------ | ------ |
| <img width="1898" alt="image"
src="51bb78e1-cf17-4652-8c77-a3b5e28dbdbe">
|
|
## Testing
- Go to host view:
- Check the KPI tiles' colors
- Open the host flyout and check them again
- Go to inventory and click on a host in the waffle map
- Check the KPI tiles' colors inside the flyout
- Click on open as page and check the kpi tiles there:
- <img width="1658" alt="image"
src="a61126ca-9eaf-493e-9d48-bc34ce7843fd">
Support to restore baseline/deviation time ranges from url state on full
page refresh. Also updates functional tests to include a full page refresh after the
first analysis run for each dataset.
## Summary
Currently, the diagnostic task is enqueueing alerts onto the production
queue. This is problematic and likely causes a lot of EP alert telemetry
loss in busy clusters. There is also a 100/1m cap on the queue which is
also a bottleneck for the diagnostic feed. I'm following up with a
bigger PR to move this query to a
[PIT](https://www.elastic.co/guide/en/elasticsearch/reference/current/point-in-time-api.html)
query.
### Checklist
Delete any items that are not applicable to this PR.
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
## Summary
Security Data Analytics would like to know when these files are updated.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## 📓 Summary
Closes#171485
This fix guarantees the JSON doc view will always get a minimum space
independently of the available space, to avoid the current scenario
where a scrollable flyout does not reserve enough space for the JSON tab
content tobe displayed (see recording in the related issue).
2c539047-32cd-4213-bc6f-3062de151426
---------
Co-authored-by: Marco Antonio Ghiani <marcoantonio.ghiani@elastic.co>
### Summary
Address https://github.com/elastic/kibana/issues/82002 and
https://github.com/elastic/kibana/issues/75440
I think I found a breakthrough for this flaky behavior. I run the
integration test 800x locally, with different settings:
Adjusting both the delayed emission (send 1 char at a time), and the
socket idle timeout to have exacly the same value (e.g. `10 millis`), I
managed to get the `ECONNRESET` 100% of the times.
Thus, IIUC the ECONNRESET happens when the client tries to send a
character over the socket and at the same time the server responds with
the idle timeout.
Adjusting the values so that the delay between character emissions is
significantly larger than the idle timeout, e.g. 20 vs 5, I get `socket
hang up` 100% of the times.
Flaky Test Runner Pipeline - 300x 🟢https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/4030
This PR updates the URL to the Elastic Support Portal registered by the
Cloud plugin, to include the configured deployment ID as a querystring
parameter.
1. On serverless deployments, we set the projects unique identifier with
`?serverless_project_id=123ABC`
2. On stateful cloud deployments, we set the deployment's unique
identifier with `?cloud_deployment_id=123ABC`
3. On on-prem deployments functionality shall remain unchanged.
Where this link can be found in the UI:
I pushed this revert up initially via
e79ca5e9d6 while debugging an issue with
CI waiting for agents. This was not the root cause and can be
unreverted.
## Summary
Closes#160803
This PR removes the `CI Composite` story because it has been broken
since at least ac23dce29f (and possibly
since b862a6c181). The functionality is
covered by the generated `index.html` in
dda4498fee/.buildkite/scripts/steps/storybooks/build_and_upload.ts (L105-L120)
To fix the composite story requires generating `stories.json` for every
storybook, which requires migrating the repo off the deprecated
`storiesOf` API. That task is quite extensive and would be better
handled alongside an upgrade to Storybook 7.x
## Summary
Currently, Cypress is writing junit XML files that we are trying to map
to the expected CI format, but if the job fails the broken files are
still being uploaded and passed to the Flaky Test Reporter which causes
it to fail.
So the solution is to just delete the broken files before they are sent
to the Flaky Tests Reporter
Co-authored-by: Tiago Costa <tiago.costa@elastic.co>
## Summary
Fixes https://github.com/elastic/kibana/issues/168194
Under some circumstance, when navigating to the timelines page, we would
get a runtime exception for `state.tableById[action.id]` not being
defined. When that happened, the redux store would be in a broken state.
This PR makes the responsible destructuring assignment more save.
Closes https://github.com/elastic/kibana/issues/167577
## Summary
Previously, the Link embeddable used the whole redux embeddable package
- however, the overall state that needs to be managed for this panel is
very simple, so this ended up being overkill. This PR fixes that by
adding a `useLinksAttributes` hook to replace the redux package that
subscribes to changes made to the attributes instead.
I also made two smaller changes in this PR:
1. Called the "Organize imports" command from VSCode on all of the
touched files - this explains all of the seemingly unrelated import
changes.
2. I fixed the React warning that was being thrown due to calling
`setIsSaving` after the component was unmounted.
### How to Test
To test number 2 above, create a by-reference Links panel and refresh
the dashboard. Then,
1. Make some sort of change to the Links panel, such as re-arranging the
links
2. Save the changes - note that, without the mount check, the following
React error will be thrown:
3. Now, with the mount check, this no longer happens 🎉
### Checklist
- [x] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers)
### For maintainers
- [ ] This was checked for breaking API changes and was [labeled
appropriately](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process)
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Adds the ability to quickly create a categorisation anomaly detection
job from the pattern analysis flyout.
Adds a new `created_by` ID `categorization-wizard-from-pattern-analysis`
which can be picked up by telemetry.
Creates a new package for sharing our AIOPs ui actions IDs. I think we
should move the pattern analysis ID to this package too, but that can be
done in a separate PR.
51349f93-f072-4983-85f0-98741902fb5a
6e618581-8916-4e63-930f-945c96c25e6c
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
close https://github.com/elastic/kibana/issues/170758
This PR increases root breadcrumb max width from 160 to 320px to fit
more of project titles. It also slightly adjusts number of visible
breadcrumbs per breakpoint to account for potentially 2x longer root
breadcrumb. Note that responsiveness is still not ideal as the system
doesn't actually calculate the width of each breadcrumb.
Before:
<img width="1267" alt="Screenshot 2023-11-20 at 11 53 13"
src="6d2ba8d2-5bc0-4f85-a87a-a4185ae901f7">
After:
<img width="1284" alt="Screenshot 2023-11-20 at 11 52 31"
src="90a57e58-6836-4465-a21e-78f72dc4953e">
## Summary
Update new user details flyout to be consistent with Expandable Alerts
Flyout. The previous user details flyout implementation was hidden
behind a flag and never went live.
### What is included
* Update new user details flyout to use the expandable flyout component
* Update UI components according to the new design
* Keep the feature hidden behind newUserDetailsFlyout flag
* Supporting alert risk inputs
### What is NOT included
* Supporting multiple categories of risk inputs
* Host details flyout
* User and host pages
* Asset integrations (okta and azure)
* Update the flyout on the timeline (It is currently a technical
restriction of the expandable flyout, but the team is working to fix it)
### How to test it?
* Enable experimental flag `newUserDetailsFlyout`
`xpack.securitySolution.enableExperimental: ['newUserDetailsFlyout']`
* Create alerts and open alerts page
* Click on a username
- [x] Test edge cases
- [x] No cases permissions (it hides cases actions)
- [x] Basic license (it hides the risk score summary)
- [x] No risk score data for a user (It hides the risk score summary)
<img width="434" alt="Screenshot 2023-11-13 at 15 56 33"
src="4fc13042-cd3d-487b-9982-bfbf02f003b4">
### Checklist
- [x] Any text added follows [EUI's writing
guidelines](https://elastic.github.io/eui/#/guidelines/writing), uses
sentence case text and includes [i18n
support](https://github.com/elastic/kibana/blob/main/packages/kbn-i18n/README.md)
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html)
were updated or added to match the most common scenarios
- [x] This renders correctly on smaller devices using a responsive
layout. (You can test this [in your
browser](https://www.browserstack.com/guide/responsive-testing-on-local-server))
Fixes https://github.com/elastic/kibana/issues/168349
## Summary
Fix links to Logs view to point to Discover in Serverless.
As the Logs view UI is not available in serverless, the "Open in logs"
buttons should point to Discover instead. Rather than hardcode the url
in each of the places where is needed, I extracted a small component
that builds the two urls and allows switching in an easier way.
If in the future on of the two links will go away, it will be easier to
find those occurrences.
### Testing
Test for serverless following [these
instructions](https://github.com/elastic/kibana/pull/167976)
**Error logs in agent activity flyout**
- Enroll an agent and try to cause some error - for instance upgrading
an agent that is not upgradeable
- Click on "Agent Activity" and find the error and a button besides it
- On stateful the button says "Open in Logs"
- On serverless is "Open in discover"
- Check that both show the same logs:
**Agent logs**
(Same test as above)
- Enroll an agent
- Click on the agent and go to the "Logs" tab
- On stateful the button says "Open in Logs"
- On serverless is "Open in discover"
- Check that both show the same logs
**Custom Logs UI**
There is also a link to logs on custom logs UI but I just linked to
discover for that one:
https://github.com/elastic/kibana/pull/171525/files#diff-e337aa916d60d0d1033e3298c8c9c33c6a6fcd87a8ded971a4a87f5ccfc0981fR20-R22
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
