Julia Bardi
2dda5b8439
[Fleet] added debug statements to track down stalling bug ( #149601 )
...
## Summary
Related to https://github.com/elastic/kibana/issues/149257
Added a few debug statements and added a condition not to return early
from update tags batch processing.
Couldn't reproduce the bug yet, so I'm not 100% sure this is the root
cause.
### Checklist
- [ ] [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
2023-01-27 14:46:40 +01:00
Marco Vettorello
5a2f51c347
[Lens] gracefully handle JS Object method names as field names ( #148118 )
...
The commit fixed the bits of code where we were using directly an index field name as an object key. This can cause errors if the field name is a reserved JS keyword.
The fix reconfigured that part of the code by replacing plain Objects with `Map` that doesn't suffer from this issue.
2023-01-27 14:40:51 +01:00
Nicolas Chaulet
22c693d17f
[Fleet] Fix Lock icon aligment for managed agent policies ( #149636 )
2023-01-27 08:34:24 -04:00
Sergi Massaneda
09de0d4531
[CellActions] Support for empty value in addToTimeline action ( #149527 )
...
part of: https://github.com/elastic/kibana/issues/145666
## Summary
This PR contains changes in the `dataProvider` function for the
addToTimeline action:
- add support for empty values excluding the field, to make it
consistent with the legacy implementation.
- id changes removing the "draggable" word.
- extracted `getIdForField` function to reduce the main function
complexity (linter warning appeared)
This PR also introduces the `CellAction` type for action creation:
- `isCompatible` method parameters uses the new
`CellActionCompatibilityContext` type instead of
`CellActionExecutionContext`, it omits the `field.value` and the
references values, they are not needed to check the compatibility and,
in some situations, it is not possible to pass them.
- use CellAction type in all SecuritySolution action creators
- action creators now return plain objects instead of using
`createAction` (deprecated) function.
- all actions now check `fieldHasCellActions(field.name)` in the
`inCompatible` function, to keep the consistency with legacy code.
- `useLoadAction` hooks now integrate the error control, components
don't need to check the `error` anymore.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-01-27 05:14:32 -07:00
Marco Liberati
475908fe93
[Graph] Enable allowJS flag in TS config ( #149671 )
...
## Summary
Fixes #144286
### Checklist
Delete any items that are not applicable to this PR.
- [ ] 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 )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/ ))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/ ),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US ))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker )
- [ ] 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 ))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers )
### Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.
When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:
| Risk | Probability | Severity | Mitigation/Notes |
|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx ) |
### 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 )
2023-01-27 12:21:26 +01:00
Walter Rafelsberger
b87d754e9e
[ML] AIOps: Fixes timefilter subscriptions. ( #149576 )
...
The `useEffect` hooks that set up subscriptions related to the
`timefilter` were missing `[]` to be only called when the code is
mounted, without it they were called on every render. This PR adds the
missing `[]` and also combines the two hooks into one.
2023-01-27 12:01:22 +01:00
claracruz
db7bc1423b
Add background image to flyout panel dark ( #149668 )
...
Rel #147383
### Screenshots
<img width="518" alt="Screenshot 2023-01-27 at 09 48 47"
src="https://user-images.githubusercontent.com/91763/215057006-94dde903-e40a-4126-889b-957bcff0175c.png ">
2023-01-27 10:59:10 +00:00
jennypavlova
616630e2ab
[Infrastructure UI] Fix: Metrics explorer padding issue ( #149609 )
...
Closes #149537
## Summary
This PR will fix the padding issue in metrics explorer. I tried to
investigate what caused the issue and couldn't find any lead in the
`toolbar` component history (nothing changed there). I opened our
monitoring cluster and there the only difference I saw was the
`gutterSize` defined in the flex groups and then all flex items inside
have the correct margins.
<img width="1808" alt="image"
src="https://user-images.githubusercontent.com/14139027/214890355-d5d682b9-4716-4ead-858c-0cf3718122bb.png ">
I tried to add `gutterSize` to both flex groups but unfortunately, it
didn't work - the flex items didn't get the margins. Probably the way
the `eu` component passes them is changed. I don't see this issue on any
of the other pages inside Infrastructure so it's maybe an edge case.
I got the "inspiration" for this fix from the [euiFlex
docs](https://elastic.github.io/eui/#/layout/flex#flex-grids-and-flex-groups-can-nest )
and by adding the existing 2 groups in another flex group with defined
`gutterSize` and `direction` to get the correct spacing between the
groups. I am also open to other ideas: I decided to still add this fix
and invest more time to investigate the cause of the bug only if this
fix is not a possible solution to the issue.
2023-01-27 11:48:52 +01:00
Shahzad
a17e630641
[Synthetics] Add beta labelling ( #149607 )
...
Co-authored-by: jennypavlova <jennypavlova94@gmail.com>
Co-authored-by: Casper Hübertz <casper@formgeist.com>
Fixes https://github.com/elastic/kibana/issues/146041
2023-01-27 03:15:09 -07:00
Julia Bardi
2d67837465
[Fleet] enabling diagnostics feature flag and changed query for files to use upload_id ( #149575 )
...
## Summary
Closes https://github.com/elastic/kibana/issues/141074
Enabled feature flag and tweaked implementation to find file by
`upload_id` rather than doc id.
How to test:
- Start local kibana, start Fleet Server, enroll Elastic Agent from
local (pull [these
changes](https://github.com/elastic/elastic-agent/pull/1703 ) )
- Click on Request Diagnostics action on the Agent
- The diagnostics file should appear on Agent Details / Diagnostics tab.
- The action should be completed on Agent activity
<img width="1585" alt="image"
src="https://user-images.githubusercontent.com/90178898/214805187-2b1abe34-ba7e-4612-9fad-7ef1f5942f47.png ">
<img width="745" alt="image"
src="https://user-images.githubusercontent.com/90178898/214805997-20fdaa01-e4c5-461c-b395-1b1e43117f8a.png ">
The file metadata and binary can be queried from these indices:
```
GET .fleet-files-agent/_search
GET .fleet-file-data-agent/_search
```
Tweaked the implementation so that the pending actions are showing up as
soon as the `.fleet-actions` record is created (it can take several
minutes until the action result is ready)
Plus added a tooltip for error status
<img width="948" alt="image"
src="https://user-images.githubusercontent.com/90178898/214841337-eacbb1fc-4934-4d8b-9d52-8db4502d2493.png ">
### Checklist
- [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
2023-01-27 11:14:07 +01:00
Walter Rafelsberger
0174705379
[ML] Fix race condition when updating data grid row count ( #149518 )
...
This fixes an edges case where handling the row count information (the
actual count and the relation (`eq/gte`)) could trigger two independent
state updates. Because of those multiple state updates the check whether
to show the mini histograms by default could fail. For example updating
from `count: 0, relation: eq` to `count: 10000, relation: gte` could
cause an intermediate state `count: 10000, relation, eq` which would
pass the check to show the mini charts. The fix here is to combine the
two settings to use only one `useState()`.
2023-01-27 11:07:08 +01:00
István Zoltán Szabó
b63be4484e
[ML] Review UI text of population, advanced, categ, rare, and geo wizards ( #149407 )
...
## Summary
This PR adjusts the anomaly detection UI text to be shorter, cleaner,
and more in line with the EUI guidelines. The field names above the
field selectors are removed.
2023-01-27 10:52:57 +01:00
Maryam Saeidi
7bce7c934d
[AO] Implement Alert Summary Widget new design ( #149348 )
...
Closes #149239
Closes #149238
## 📝 Summary
This PR implements the new design of the Alert Summary Widget. In the
new design, we removed the recovered chart and count to make it easier
to understand.
([design](https://www.figma.com/file/xnSsLoEMntX3VLG0qwmmnt/Alert-summary-widget-V2?t=m2Xd16Obz5OJz7A1-0 ))
After discussion with @maciejforcone, we decided to use blue color
instead of black since when we have one alert that triggers the whole
time during the selected period, the chart was not readable.
|Full-size|Compact|
|---|---|
|
- Generate some alerts
- Check the Alerts page; you should see the Alert Summary Widget show
the correct data
- Check the Rule details of one of the alerts to see the compact version
there
- Clicking on Alert Summary Widget compact version should work as
expected
Co-authored-by: Katrin Freihofner <katrin.freihofner@elastic.co>
2023-01-27 10:44:21 +01:00
Muhammad Ibragimov
0d613e58cf
[Console] Using Console to remote reindex with an incorrect password logs the user out of Kibana ( #143440 )
...
Fixes https://github.com/elastic/kibana/issues/140536
### Summary
Console mirrors ES response status code to the client in order to show the status of the request in the UI. However, if the status code is 403, for instance, in the case of reindexing with invalid credentials, the user is logged out of Kibana due to the [interceptor](https://github.com/elastic/kibana/blob/main/x
pack/plugins/security/public/session/unauthorized_response_http_interceptor.ts#L42) that is set up in the security plugin. This PR fixes that by setting the status code and status text as custom headers so that the client can access them in the response. This way, we can avoid logging out users if the status code is 403.
To test this, follow the steps described in
https://github.com/elastic/kibana/issues/140536
<img width="1502" alt="Screen Shot 2022-10-17 at 18 30 07"
src="https://user-images.githubusercontent.com/53621505/196190023-462cbadc-b155-4183-b9fd-47ce779a306e.png ">
Co-authored-by: Muhammad Ibragimov <muhammad.ibragimov@elastic.co>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-01-27 14:41:26 +05:00
Pablo Machado
482d1ced82
Delete CellActions from UI actions plugin ( #149522 )
...
## Summary
This PR only deletes the component from the UI action plugin.
@semd has already added the component to a new package here
https://github.com/elastic/kibana/pull/149057
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-01-27 10:37:04 +01:00
Marco Liberati
c4a0ed2c19
[Lens] Fix chart padding on reference lines/annotations icon on the left side ( #149573 )
...
## Summary
Fix #149414
Fixed margin computation for annotations icons on the left side. Added
unit tests.
<img width="1238" alt="Screenshot 2023-01-26 at 10 12 10"
src="https://user-images.githubusercontent.com/924948/214798802-6d176cf2-1bee-4f1e-bcaf-40bd970d857d.png ">
### Checklist
Delete any items that are not applicable to this PR.
- [ ] 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 )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/ ))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/ ),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US ))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker )
- [ ] 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 ))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers )
### Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.
When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:
| Risk | Probability | Severity | Mitigation/Notes |
|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx ) |
### 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: Stratoula Kalafateli <efstratia.kalafateli@elastic.co>
2023-01-27 10:35:42 +01:00
Marco Liberati
83dd5f84fc
[Lens] Enable nice rounding for scalar axis ( #149388 )
...
## Summary
Fix #145245
This PR adds the "axis rounding to nice values" enabled by default in
Lens. Other editors are not affected by this change.
The feature can be manually disabled by the user in the relative axis
popover menu, when a compatibility mode is chosen (`full` for metrics,
`dataBounds` for bucketed).
<img width="920" alt="Screenshot 2023-01-24 at 09 34 07"
src="https://user-images.githubusercontent.com/924948/214260732-712820e9-3127-4a7c-8851-9c093f321aeb.png ">
In case of incompatible mode the rounding option is hidden (and
internally ignored):
<img width="396" alt="Screenshot 2023-01-24 at 09 35 25"
src="https://user-images.githubusercontent.com/924948/214261330-8aece151-b972-4071-9474-06cf7539956c.png ">
<img width="476" alt="Screenshot 2023-01-24 at 09 35 42"
src="https://user-images.githubusercontent.com/924948/214261355-4a0dc9e0-d69d-4a59-bed9-3b69de23664f.png ">
<img width="396" alt="Screenshot 2023-01-24 at 09 36 08"
src="https://user-images.githubusercontent.com/924948/214261383-7c050366-0cb2-498e-a3af-2f7509a87934.png ">
Here's a dashboard with several combinations of Lens XY configurations
with (upper row) and without value nice-ing enabled (bottom row):
<img width="1497" alt="Screenshot 2023-01-24 at 10 08 27"
src="https://user-images.githubusercontent.com/924948/214261007-7bff4be1-16c1-40e6-95f4-b718973877a6.png ">
## Note
The PR was also an opportunity to do a little shared component
refactoring for axes.
### Checklist
Delete any items that are not applicable to this PR.
- [ ] 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 )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/ ))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/ ),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US ))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker )
- [ ] 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 ))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers )
### Risk Matrix
Delete this section if it is not applicable to this PR.
Before closing this PR, invite QA, stakeholders, and other developers to
identify risks that should be tested prior to the change/feature
release.
When forming the risk matrix, consider some of the following examples
and how they may potentially impact the change:
| Risk | Probability | Severity | Mitigation/Notes |
|---------------------------|-------------|----------|-------------------------|
| Multiple Spaces—unexpected behavior in non-default Kibana Space.
| Low | High | Integration tests will verify that all features are still
supported in non-default Kibana Space and when user switches between
spaces. |
| Multiple nodes—Elasticsearch polling might have race conditions
when multiple Kibana nodes are polling for the same tasks. | High | Low
| Tasks are idempotent, so executing them multiple times will not result
in logical error, but will degrade performance. To test for this case we
add plenty of unit tests around this logic and document manual testing
procedure. |
| Code should gracefully handle cases when feature X or plugin Y are
disabled. | Medium | High | Unit tests will verify that any feature flag
or plugin combination still results in our service operational. |
| [See more potential risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx ) |
### 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 )
2023-01-27 10:26:28 +01:00
Thomas Watson
2b276a9dca
Enable GitHub Code Scanning ( #148318 )
...
This enables [GitHub Code Scanning][1] to run on the `main` branch once a day.
The result of the scans can be found under [Security > Code scanning][2].
Running the code scanner takes about two hours, so it's not feasible to
run for every PR, and for now I think it's too much to run on every
pushed commit to `main` as well. However, this can always be enabled
later as needed.
The scan is configured to ignore test files and dev-dependency packages
hosted inside the Kibana repo. If these were included in the scan, it
would take three hours instead of two and the report would include more
noise taking focus away from the important findings affecting
production.
[1]: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/about-code-scanning
[2]: https://github.com/elastic/kibana/security/code-scanning
2023-01-27 04:03:16 -05:00
Alexander Wert
7ee827b844
Added Azure Functions support in the APM UI ( #149479 )
...
## Summary
Adds support for Azure Functions in the APM UI.
- adds serverless Azure Functions icon to the service_icons
<img width="584" alt="image"
src="https://user-images.githubusercontent.com/866830/214506733-ab50c9b3-977b-4730-9119-fef505329c58.png ">
- replaces 'time spent by span type' graph with 'cold start rate' graph
in service overview and transaction overview:
<img width="891" alt="image"
src="https://user-images.githubusercontent.com/866830/214507066-1a283f10-7a24-4b56-a5e4-85f94bb66724.png ">
<img width="1549" alt="image"
src="https://user-images.githubusercontent.com/866830/214507105-816341b4-09aa-48a6-b9c2-494d3115ebd6.png ">
- adds synthtrace scenario for Azure Functions
### Checklist
- [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
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-01-27 01:52:38 -07:00
Kibana Machine
5c97c487e8
[api-docs] 2023-01-27 Daily api_docs build ( #149659 )
...
Generated by
https://buildkite.com/elastic/kibana-api-docs-daily/builds/230
2023-01-27 01:00:40 -05:00
Khristinin Nikita
9e96440aaa
Strip field from events for event search ( #149113 )
...
Strip source, and keep only fields used for mappings for events search
of IM rule.
Tests on cloud env:
<img width="1182" alt="Screenshot 2023-01-19 at 16 42 19"
src="https://user-images.githubusercontent.com/7609147/213486861-1a0e5a20-b575-4ed6-ac9b-cf9fb8a8c14f.png ">
Threat Indicators - 1.500.000 documents
Source - 1.000.000 documents.
No changes:
<img width="564" alt="Screenshot 2023-01-19 at 16 30 19"
src="https://user-images.githubusercontent.com/7609147/213484465-ad20d5b2-c7a7-42d3-9d92-478c5d046636.png ">
Strip fields:
<img width="557" alt="Screenshot 2023-01-19 at 16 30 27"
src="https://user-images.githubusercontent.com/7609147/213484531-3ab68c61-c3f5-4e28-b2c4-c1e90a5b1775.png ">
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-01-27 06:58:02 +01:00
Lisa Cawley
7421a9737d
[DOCS] Create open API specification for create rule ( #149565 )
2023-01-26 18:07:23 -08:00
Tiago Costa
a13bfae14c
chore(NA): update versions after v8.6.2 bump ( #149596 )
...
This PR is a simple update of our versions file after the recent bumps
2023-01-27 01:05:12 +00:00
Tim Sullivan
a791e4c5be
Report: various improvements for troubleshooting ( #149431 )
...
## Summary
When reports are slow to execute or wait in the queue for a long time, a
couple of things have added to the difficulty of troubleshooting based
on the logs:
* there is no default-level log message stating when a job has been
claimed and is beginning to execute.
* the report job ID is not shown anywhere in the UI, making it hard to
correlate log messages with the job listing
This PR addresses those both of those things with minor changes.
**New log message:**
<img width="2022" alt="image"
src="https://user-images.githubusercontent.com/908371/214357980-bfcf7dc5-3bd4-40dd-9065-0ca520a5f859.png ">
**New field in the report job info panel:**
<img width="1758" alt="image"
src="https://user-images.githubusercontent.com/908371/214356657-344a116e-7d17-4683-b6da-0b868a4dc3ba.png ">
2023-01-26 16:51:10 -07:00
Jon
3727091344
[artifacts/container-image] Add annotation containing image metadata ( #149627 )
...
Adds a buildkite annotation with the built image tags.
https://buildkite.com/elastic/kibana-artifacts-container-image/builds/157
2023-01-26 16:34:43 -07:00
Zacqary Adam Xeper
d9197fc1d5
[RAM] Fix rewriting frequency param in _find API ( #149623 )
...
## Summary
Fixes an issue that was cropping up in the `_find` API where the
`rewriteRule` function was spreading all `frequency` props into the
action instead of applying them to a `frequency` prop
2023-01-26 16:53:29 -06:00
Rodney Norris
0554ded490
[Enterprise Search][ML Inference] UX improvements ( #149464 )
...
## Summary
Several UX improvements for the ML inference flyout as well as minor bug
fixes:
- aligned on a consisted title & paragraph for each step
- test step layout and copy improvements
- reworded create button copy
- auto-selected "New" when there are no existing pipelines to choose
- used correct class to scroll to error in flyout, updated from modal
- fixed bug where error was thrown from kibana when there are no
existing inference pipelines
### Screenshots
Configure Step
Test
Review
2023-01-26 15:59:24 -06:00
Mike Côté
275fdeba85
Add rule spaceId to APM transaction when a rule is running ( #149600 )
...
Resolves https://github.com/elastic/kibana/issues/149318
In this PR, I'm adding `alerting_rule_space_id` label to the apm
transaction whenever a rule is running.
2023-01-26 13:59:29 -05:00
Matthias Wilhelm
116492d6f0
[Discover][Embeddable] Remove redundant react component rendering when a custom title is set ( #148970 )
2023-01-26 19:56:15 +01:00
Melissa Alvarez
1496173cdf
[ML] Anomaly Detection geo wizard: ensure map examples reflect saved search ( #149291 )
...
## Summary
Fixes https://github.com/elastic/kibana/issues/149290
Ensure the map examples reflect the saved search query.
<img width="1179" alt="image"
src="https://user-images.githubusercontent.com/6446462/213820351-00cbca76-cafc-4820-a2df-333805ee9cde.png ">
### Checklist
Delete any items that are not applicable to this PR.
- [ ] 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 )
- [ ]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [ ] [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
- [ ] Any UI touched in this PR is usable by keyboard only (learn more
about [keyboard accessibility](https://webaim.org/techniques/keyboard/ ))
- [ ] Any UI touched in this PR does not create any new axe failures
(run axe in browser:
[FF](https://addons.mozilla.org/en-US/firefox/addon/axe-devtools/ ),
[Chrome](https://chrome.google.com/webstore/detail/axe-web-accessibility-tes/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US ))
- [ ] If a plugin configuration key changed, check if it needs to be
allowlisted in the cloud and added to the [docker
list](https://github.com/elastic/kibana/blob/main/src/dev/build/tasks/os_packages/docker_generator/resources/base/bin/kibana-docker )
- [ ] 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 ))
- [ ] This was checked for [cross-browser
compatibility](https://www.elastic.co/support/matrix#matrix_browsers )
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-01-26 11:35:38 -07:00
Kibana Machine
80b78d94cc
skip failing test suite ( #149163 )
2023-01-26 12:43:26 -05:00
Mike Côté
f49c3ac7bf
Fix issues around enabling and disabling tasks ( #148985 )
...
Resolves https://github.com/elastic/kibana/issues/148914
Resolves https://github.com/elastic/kibana/issues/149090
Resolves https://github.com/elastic/kibana/issues/149091
Resolves https://github.com/elastic/kibana/issues/149092
In this PR, I'm making the following Task Manager bulk APIs retry
whenever conflicts are encountered: `bulkEnable`, `bulkDisable`, and
`bulkUpdateSchedules`.
To accomplish this, the following had to be done:
- Revert the original PR (https://github.com/elastic/kibana/pull/147808 )
because the retries didn't load the updated documents whenever version
conflicts were encountered and the approached had to be redesigned.
- Create a `retryableBulkUpdate` function that can be re-used among the
bulk APIs.
- Fix a bug in `task_store.ts` where `version` field wasn't passed
through properly (no type safety for some reason)
- Remove `entity` from being returned on bulk update errors. This helped
re-use the same response structure when objects weren't found
- Create a `bulkGet` API on the task store so we get the latest
documents prior to a ES refresh happening
- Create a single mock task function that mocks task manager tasks for
unit test purposes. This was necessary as other places were doing `as
unknown as BulkUpdateTaskResult` and escaping type safety
Flaky test runs:
- [Framework]
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1776
- [Kibana Security]
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1786
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-01-26 12:23:30 -05:00
Lisa Cawley
f78236a2e4
[DOCS] Create open API specification for run connector ( #149274 )
2023-01-26 08:53:47 -08:00
jennypavlova
0e3ae210d7
[Infrastructure UI] Hosts technical preview discovery ( #149351 )
...
Closes #148235
## Summary
This PR adds an option for the user to enable the hosts view and makes
the hosts navigation link always visible.
### Code Review
I know that this PR looks big (it actually is 😅 ) and not "fun" to
review but I will try to make it easier by splitting and pointing out
the different parts here:
- [Change in the
Navigation](https://github.com/elastic/kibana/pull/149351/files#diff-1f9338fabab6f332f6b4b11dbcec00f10b89097720c94b6087c53b186659c976 ):
Contains also a
[component](https://github.com/elastic/kibana/pull/149351/files#diff-9f8d59f3f98855c2cc6c4bd8ad93f69ad06181809a8769121fc1a3714c848f5e )
to show the icon next to the name
- [Hosts view navigation link enabled by
default](https://github.com/elastic/kibana/pull/149351/files#diff-f66e54f3274b7dd4c72b54011c1b4a1d2e4d91aa47341e14b048377437574655 )
- [The Hosts View Landing
page](https://github.com/elastic/kibana/pull/149351/files#diff-c3aa95031634008b7384dd670ca12c8266bead5f2cd461fdc6070fe84ae9e4e4 )
: Using the
[EnableHostViewPage](https://github.com/elastic/kibana/pull/149351/files#diff-a0704adf74ea9605858160dfbe6ee04021b8161a63a54852009847fb5caeb5e8 )
component passing different `actions` based on the use case.
- [Link on the inventory
page](https://github.com/elastic/kibana/pull/149351/files#diff-181e8eeab11591c40565d6636c1b0fc6099bc555af71efe612d1da3f406d7101 )
- [Functional
Tests](https://github.com/elastic/kibana/pull/149351/files#diff-cdf2ef63d7f0db051d569b09fbd2ba39eb852d3d75bf3b29d85e57de2da3af35 )
### Flow
#### How to navigate to Hosts View
- The link from the inventory page which will navigate the user to a
separate page where he will have the option to enable hosts view (if the
user has permission to enable it otherwise he will see a message to
contact his administrator to do it for him). In order to enable the
hosts view the user should have permission to modify advanced settings.
- The navigation link will be always visible. After enabling the host
view the user will see the hosts view page
(links highlighted in green): <img width="2055" alt="image"
src="https://user-images.githubusercontent.com/14139027/214123141-e3d8a156-839f-4dbf-ae6f-b564eccb16f7.png ">
#### After navigating to host view
- When hosts view is disabled
| Admin User | User with read-only permission |
| ------------ | ------------------------------- |
|
|
|
- When hosts view is enabled (Both Admin User and User with read-only
permission ) <img width="1713" alt="image"
src="https://user-images.githubusercontent.com/14139027/214125673-8976047c-7653-4345-bfee-41413f080e05.png ">
## Testing
- Remove the override (if any) in the`kibana.yml` for
`observability:enableInfrastructureHostsView`
- Use `elastic` user (or user with permission to modify advanced
settings) to enable the host view (navigating from the inventory page or
from the nav menu)
- to disable the host view you should set
`observability:enableInfrastructureHostsView` to `false` in Stack
Management > Advanced Settings: <img width="1724" alt="image"
src="https://user-images.githubusercontent.com/14139027/214127034-fc245d12-0e56-4aa3-9b35-bdfeb7760960.png ">
- create a new role and set the `Management` permissions to `none` and
observability permissions to `read`: <img width="1726" alt="image"
src="https://user-images.githubusercontent.com/14139027/214127744-27e3014f-c181-4cd0-9b91-8868580a909b.png ">
- Assign this role to a user
- Open hosts view (for both cases
`observability:enableInfrastructureHostsView` set to `false`/`true`)
❓ Testing telemetry
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-01-26 17:30:17 +01:00
Kevin Delemme
088a6bb5af
feat(slo): dashboard with sparkline and badges ( #149445 )
2023-01-26 11:15:50 -05:00
Nicolas Chaulet
da83d96ff6
[Fleet] Fix add fleet server flow from agent policy page ( #149507 )
2023-01-26 08:55:36 -07:00
Alejandro Fernández Gómez
1d5e25ae27
[Synthetics UI] return 404 in project monitor APIs with non-existing spaces. ( #149136 )
...
## Summary
Closes #148930
Returns a 404 when the project monitor APIs are called with a
non-existent space.
When testing, note that the API _does_ return 404, but the
@elastic/synthetics package seems to ignore this.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: shahzad31 <shahzad31comp@gmail.com>
2023-01-26 10:54:20 -05:00
renovate[bot]
cf907f7a98
Update dependency core-js to ^3.27.2 (main) ( #149560 )
...
[](https://renovatebot.com )
This PR contains the following updates:
| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [core-js](https://togithub.com/zloirock/core-js ) | [`^3.27.1` ->
`^3.27.2`](https://renovatebot.com/diffs/npm/core-js/3.27.1/3.27.2 ) |
[](https://docs.renovatebot.com/merge-confidence/ )
|
[](https://docs.renovatebot.com/merge-confidence/ )
|
[](https://docs.renovatebot.com/merge-confidence/ )
|
[](https://docs.renovatebot.com/merge-confidence/ )
|
---
### Release Notes
<details>
<summary>zloirock/core-js</summary>
###
[`v3.27.2`](https://togithub.com/zloirock/core-js/blob/HEAD/CHANGELOG.md#​3272---20230119-httpsgithubcomzloirockcore-jsreleasestagv3272 )
[Compare
Source](https://togithub.com/zloirock/core-js/compare/v3.27.1...v3.27.2 )
- [`Set` methods
proposal](https://togithub.com/tc39/proposal-set-methods ) updates:
- Closing of iterators of `Set`-like objects on early exit,
[proposal-set-methods/85](https://togithub.com/tc39/proposal-set-methods/pull/85 )
- Some other minor internal changes
- Added one more workaround of a `webpack` dev server bug on IE global
methods,
[#​1161](https://togithub.com/zloirock/core-js/issues/1161 )
- Fixed possible `String.{ raw, cooked }` error with empty template
array
- Used non-standard V8 `Error.captureStackTrace` instead of stack
parsing in new error classes / wrappers where it's possible
- Added detection correctness of iteration to `Promise.{ allSettled, any
}` feature detection, Hermes issue
- Compat data improvements:
- [Change `Array` by copy
proposal](https://togithub.com/tc39/proposal-change-array-by-copy )
marked as supported from V8 ~ Chrome 110
- Added Samsung Internet 20 compat data mapping
- Added Quest Browser 25 compat data mapping
- Added React Native 0.71 Hermes compat data
- Added Electron 23 and 24 compat data mapping
- `self` marked as fixed in Deno 1.29.3,
[deno/17362](https://togithub.com/denoland/deno/pull/17362 )
- Minor tweaks of minification settings for `core-js-bundle`
- Refactoring, some minor fixes, improvements, optimizations
</details>
---
### Configuration
📅 **Schedule**: Branch creation - At any time (no schedule defined),
Automerge - At any time (no schedule defined).
🚦 **Automerge**: Disabled by config. Please merge this manually once you
are satisfied.
♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the
rebase/retry checkbox.
🔕 **Ignore**: Close this PR and you won't be reminded about this update
again.
---
- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box
---
This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/ ). View
repository job log
[here](https://app.renovatebot.com/dashboard#github/elastic/kibana ).
<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNC4xMTEuMSIsInVwZGF0ZWRJblZlciI6IjM0LjExMS4xIn0=-->
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Jonathan Budzenski <jon@elastic.co>
2023-01-26 09:50:14 -06:00
Jon
c5400cee35
Revert "[build] Fix canvas shareable runtime" ( #149595 )
...
Reverts elastic/kibana#149165
Node 18 was downgraded to Node 16, this flag is not supported -
https://github.com/elastic/kibana/pull/149531
2023-01-26 09:47:13 -06:00
Christiane (Tina) Heiligers
b9f31afc23
Flags core mocks packages as devOnly ( #149466 )
...
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Fix https://github.com/elastic/kibana/issues/145064
2023-01-26 08:46:06 -07:00
Kirti Sodhi
da929fc667
[ML] Fix datafeed of auth_high_count_logon_events_for_a_source_ip anomaly detection job ( #149524 )
2023-01-26 10:31:17 -05:00
Nathan Reese
85b5351c90
unskip test/functional/apps/maps/group4/discover·js ( #149554 )
...
Fixes https://github.com/elastic/kibana/issues/137408 and
https://github.com/elastic/kibana/issues/149358
flaky test runner
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1790
Tests flaky because clicking on `Visualize` button not registered. This
resulted in test failing because the test started looking for elements
in Maps even though the page was still in Discover. PR resolves
flakiness by adding retry around click to ensure `Visualize` button is
clicked as expected.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-01-26 08:29:39 -07:00
Elastic Machine
e8b368c8ab
[main] Sync bundled packages with Package Storage ( #149572 )
...
Automated by
https://internal-ci.elastic.co/job/package_storage/job/sync-bundled-packages-job/job/main/1525/
Co-authored-by: apmmachine <infra-root+apmmachine@elastic.co>
2023-01-26 08:20:05 -07:00
Nathan Reese
c48406947f
[Maps] unskip X-Pack Saved Object Tagging Functional Tests.x-pack/test/saved_object_tagging/functional/tests/maps_integration·ts - saved objects tagging ( #149356 )
...
Fixes https://github.com/elastic/kibana/issues/89073 and
https://github.com/elastic/kibana/issues/106547
Flaky test runner
https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/1785
Issue with flaky maps_integration.ts is that there was not await when
filtering maps list by tags. This resulted in list page refreshing after
`const links = await
this.find.allByCssSelector('.euiTableRow-isSelectable .euiLink');` and
then getting an elemented unmounted on future `await
links[i].getVisibleText()` calls.
A [similar fix](https://github.com/elastic/kibana/pull/82930 ) was
implemented for visualize and dashboard listing pages.
https://github.com/elastic/kibana/pull/82930 introduced
`listingTable.waitUntilTableIsLoaded` but did not introduce the method
in a consistent way. Other methods that search table were not updated to
use `listingTable.waitUntilTableIsLoaded`, but instead used
`this.header.waitUntilLoadingHasFinished()`. This PR resolved this issue
by updating all listingTable methods that search to use
`listingTable.waitUntilTableIsLoaded` and then updated
`listingTable.waitUntilTableIsLoaded` with a call to
`this.header.waitUntilLoadingHasFinished()`
https://github.com/elastic/kibana/pull/82930 did not update
maps_integration tests, only resolving the issue for visualize and
dashboard. To avoid future situations where fixes only resolve a few
usages, this PR moves selectFilterTags into listing_table and replaces
all implementations of selectFilterTags with
listingTable.selectFilterTags.
While investigating dashboard_integrations test, I found
`x-pack/test/functional/apps/dashboard/group2/dashboard_tagging.ts`,
which duplicated most of dashboard_integrations test. This PR removes
x-pack/test/functional/apps/dashboard/group2/dashboard_tagging.ts adds
the unique test case to dashboard_integrations
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2023-01-26 08:13:52 -07:00
Dzmitry Lemechko
50393be0a8
[ci] retry scalability testing step on failure ( #149399 )
...
## Summary
Quite often bootstrap
[fails](https://buildkite.com/elastic/kibana-scalability-benchmarking/builds/957#0185e31d-dcc8-42f4-ac3a-e0399a175519 )
on `kb-static-scalability-01` bare metal machine:
<details>
<summary>Bootstrap failure: [bazel] exited with code [1]</summary>
```
$ node scripts/kbn bootstrap
| 2023-01-24 11:00:50 CEST | HINT
| 2023-01-24 11:03:31 CEST | HINT If experiencing problems with node_modules try `yarn kbn bootstrap --force-install` or as last resort `yarn kbn reset && yarn kbn bootstrap`
| 2023-01-24 11:03:31 CEST | HINT
| 2023-01-24 11:03:31 CEST | ERROR [bootstrap] failed: [bazel] exited with code [1]
| 2023-01-24 11:03:31 CEST | output:
| 2023-01-24 11:03:31 CEST | INFO: Invocation ID: 207c041d-23b8-4f07-bf56-8cb961819546
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | <--- Last few GCs --->
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | [1304562:0x74b83a0] 154462 ms: Mark-sweep 4023.8 (4130.2) -> 4011.3 (4131.0) MB, 1677.3 / 0.0 ms (average mu = 0.149, current mu = 0.074) task; scavenge might not succeed
| 2023-01-24 11:03:31 CEST | [1304562:0x74b83a0] 155522 ms: Mark-sweep 4024.7 (4131.0) -> 4012.0 (4131.7) MB, 924.0 / 0.0 ms (average mu = 0.142, current mu = 0.128) task; scavenge might not succeed
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | <--- JS stacktrace --->
| 2023-01-24 11:03:31 CEST |
| 2023-01-24 11:03:31 CEST | FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory
| 2023-01-24 11:03:31 CEST | 1: 0xb6b850 node::Abort() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 2: 0xa806a6 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 3: 0xd52140 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 4: 0xd524e7 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 5: 0xf2fbe5 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 6: 0xf30ae8 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 7: 0xf40ff3 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 8: 0xf41e68 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 9: 0xfb1124 v8::internal::ScavengeJob::Task::RunInternal() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 10: 0xe2187b non-virtual thunk to v8::internal::CancelableTask::Run() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 11: 0xbd6684 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 12: 0xbd9aee node::PerIsolatePlatformData::FlushForegroundTasksInternal() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 13: 0x1652906 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 14: 0x1664e44 [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 15: 0x165326e uv_run [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 16: 0xaafa2d node::SpinEventLoop(node::Environment*) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 17: 0xbb11f4 node::NodeMainInstance::Run() [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 18: 0xb26c44 node::LoadSnapshotDataAndRun(node::SnapshotData const**, node::InitializationResult const*) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 19: 0xb2a83f node::Start(int, char**) [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | 20: 0x7fbc908be083 __libc_start_main [/lib/x86_64-linux-gnu/libc.so.6]
| 2023-01-24 11:03:31 CEST | 21: 0xaad7ee _start [/var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/nodejs/bin/node]
| 2023-01-24 11:03:31 CEST | /var/lib/buildkite-agent/.cache/bazel/_bazel_buildkite-agent/fbd7d220b25178fcebe6b4ba126fca45/external/nodejs_linux_amd64/bin/yarn: line 19: 1304562
2023-01-26 16:02:23 +01:00
claracruz
9e3cf8f0ec
Update guided onboarding flyout panel to use the background image. ( #149394 )
...
Fixes #147383
### Screenshots
<img width="525" alt="Screenshot 2023-01-25 at 16 59 19"
src="https://user-images.githubusercontent.com/91763/214629650-2db979f9-5726-4c75-8ace-8e8f1a0c7470.png ">
<img width="512" alt="Screenshot 2023-01-25 at 16 59 59"
src="https://user-images.githubusercontent.com/91763/214629688-80148487-73de-40a8-b9d6-2dbd6bcc67ea.png ">
2023-01-26 13:51:43 +00:00
Kevin Delemme
dd56e9b06d
chore(slo): refactor sli client ( #149259 )
2023-01-26 08:49:22 -05:00
Jonathan Buttner
82afa05699
[Cases] Adding new external services field for get connectors API ( #149535 )
...
This PR adds a new `externalServices` field for the get connector API.
This is needed to show the "View <incident>" link in the case's action's
menu. I moved all push related fields under a new `push` field as well.
I also ran into some circular references since the API response now
needs the external services type from the cases.ts file and the cases.ts
file imports the connector index.ts so I refactored them.
Example response
```
{
"4175c370-9cd4-11ed-975e-43fe3caaded6": {
"name": "Jira",
"type": ".jira",
"fields": {
"issueType": "10001",
"parent": null,
"priority": null
},
"id": "4175c370-9cd4-11ed-975e-43fe3caaded6",
"push": {
"needsToBePushed": false,
"hasBeenPushed": true,
"externalService": {
"pushed_at": "2023-01-25T17:18:47.770Z",
"pushed_by": {
"username": "elastic",
"full_name": null,
"email": null,
"profile_uid": "u_mGBROF_q5bmFCATbLXAcCwKa0k8JvONAwSruelyKA5E_0"
},
"connector_name": "Jira",
"external_id": "10026",
"external_title": "TPN-27",
"external_url": "<url>",
"connector_id": "4175c370-9cd4-11ed-975e-43fe3caaded6"
},
"latestUserActionPushDate": "2023-01-25T17:18:47.819Z",
"oldestUserActionPushDate": "2023-01-25T17:18:47.819Z"
}
}
}
```
2023-01-26 08:46:20 -05:00
Paul Tavares
063850817b
[Security Solution][Endpoint] Replace localhost with 127.0.0.1 in all endpoint CLI scripts ( #149551 )
...
## Summary
- Replaces `localhost` with `127.0.0.1` in all endpoint CLI scripts.
This is needed as a result of the stack's upgrade to NodeJS, as it now
seems to default `localhost` to the IPv6 loopback IP if that interface
is available on the local machine. Problem is that Kibana does not
listen on IPv6.
2023-01-26 08:43:33 -05:00
Carlos Crespo
7facd3be50
[Infrastructure UI] Lens charts reload problem fix ( #149517 )
...
## Summary
closes #149514
This PR fixes the problem with lens charts not always reloading when a
search is submitted.
### How to test
Go to Infrastructure > Hosts
- Select a relative date range of 15m from now and click on submit -
should always make all lens charts reload
- Select any absolute date and click on submit- should always make all
lens charts reload
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
2023-01-26 14:18:45 +01:00
|
