* chore: add message about missing index in data view
* fix: typo
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 9f6c78139e)
Co-authored-by: Jan Monschke <jan.monschke@elastic.co>
This PR fixes the jobs_summary API tests for the `7.latest ES 8.1 forward compatibility` scenario by making it only check expected fields in the response body and ignore additional fields that are coming from the newer ES version.
(cherry picked from commit 13e7c8a1e2)
* extract message from error objects
* only warn for 400 and up status codes
* Simplify for loop per dokmic's suggestion
Co-authored-by: Michael Dokolin <dokmic@gmail.com>
* formatting
Co-authored-by: Michael Dokolin <dokmic@gmail.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 0ee514b1fe)
* [Security Solutions] Fixes the telemetry to use the new rule types (#123781)
## Summary
Telemetry was not updated to use the newer rule types so it was not querying the elastic package rules.
The query before was:
```json
# Original query which will not get the new elastic pre-packaged rule types
GET .kibana*/_search
{
"query": {
"bool": {
"filter": [
{
"term": {
"alert.alertTypeId": "siem.signals"
}
},
{
"term": {
"alert.params.immutable": true
}
}
]
}
}
}
```
The query after this change uses the new rule types and I tested it by manually executing this query to ensure everything works as expected:
```json
# Modified query which filters against two arrays of terms. One for the set of rules
# and the second terms which filters against the rule being immutable
GET .kibana*/_search
{
"query": {
"bool": {
"must": [
{
"bool": {
"filter": {
"terms": {
"alert.alertTypeId": [
"siem.signals",
"siem.eqlRule",
"siem.mlRule",
"siem.queryRule",
"siem.savedQueryRule",
"siem.indicatorRule",
"siem.thresholdRule"
]
}
}
}
},
{
"bool": {
"filter": {
"terms": {
"alert.params.immutable": [true]
}
}
}
}
]
}
}
}
```
### 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
There doesn't look to be integration tests started for these or how to test them at this moment.
(cherry picked from commit ba6f77ca37)
* Updated to pass build since the types did not like boolean. Tested in ES directly, should still work as a string of a boolean.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* Change error to warning toast
* Add test for addWarning
Co-authored-by: Kristof-Pierre Cummings <kristofpierre.cummings@elastic.co>
(cherry picked from commit 11537eacfd)
Co-authored-by: Kristof C <kpac.ja@gmail.com>
This PR stabilizes the date nanos job and categorization job tests for cloud execution by reducing the job run time.
(cherry picked from commit 4f1d97a908)
Co-authored-by: Robert Oskamp <robert.oskamp@elastic.co>
* change test to match current message when decryption fails
* fix lint error
* update message for newest message
* lint
(cherry picked from commit f209677286)
Co-authored-by: Lee Drengenberg <lee.drengenberg@elastic.co>
Updates the Kibana link service for changes related to https://github.com/elastic/elasticsearch/pull/82826.
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Luke Elmers <lukeelmers@gmail.com>
(cherry picked from commit f77355b665)
* [Uptime] Update functional test directory to use a pinned version of package registry via docker (#117736)
* update functional test directory to use a pinned version of package registry via docker
* remove console log
* adjust config
* skip synthetics tests if no docker image
* remove extra configs
* move synthetics tests to a different directory
* update tests
* update tests
* remove duplicate tests
* update helpers
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
# Conflicts:
# x-pack/test/functional_synthetics/apps/uptime/synthetics_integration.ts
* Update x-pack/test/functional_synthetics/apps/uptime/synthetics_integration.ts
* tooltip added to OS column
* change os info message
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 16642e0028)
Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
* Log deprecations originating from Kibana on debug level
* Surface debug level deprecation logs on CI
* Review feedback
(cherry picked from commit c64c766444)
Addresses #121758 and #121759.
Updates exceptions table export icon to be "download" icon and updates exceptions table header to use native EUI page headers.
(cherry picked from commit 8c0fbdf502)
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
* search responses without a specific namespace to show pending actions
fixes elastic/kibana/issues/123707
* search over all endpoint response indices irrespective of namespace suffix
fixes elastic/kibana/issues/123707
* match namespace suffixes for endpoint action and response indices
fixes elastic/kibana/issues/123707
(cherry picked from commit dfd8bfbd90)
Co-authored-by: Ashokaditya <1849116+ashokaditya@users.noreply.github.com>
With https://github.com/elastic/elasticsearch/pull/81870, the Azure, GCS, and AWS snapshot repository types have built-in support in Elasticsearch and no longer require plugins in 8.0+. This PR updates step one of the **Register Repository** wizard to:
- Include Azure, GCS, and AWS as default repository types
- Tweak UI copy and links referring to repository plugins.
Co-authored-by: Yulia Čech <6585477+yuliacech@users.noreply.github.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
(cherry picked from commit 1e576042df)
# Conflicts:
# x-pack/plugins/snapshot_restore/server/routes/api/repositories.test.ts
## Summary
See this PR from here:
https://github.com/elastic/kibana/pull/123094
Where `"rule": { "id": null, "name": null },` can be null. This just adds guards around it to prevent possible errors. Note, I tested it first and there aren't errors with this even if we don't merge but that is not a guarantee that later NodeJS wouldn't cause errors if the implementation details of [Map](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map) change.
Note, I don't try to do any additional lookups if these are `null` as the release is coming very quickly and I do not want to overcomplicate telemetry and we don't have dashboards around the cases feature. Over time I would expect the telemetry to become more accurate again even if cases are `nulled` out.
**Manual testing**
Either create a true upgrade where all the id's changed by going to 7.16 and making a new space, then within that space outside of default creating cases and alerts and then do an upgrade to 8.0.0 ... or ...
Downgrade a `case-comments` like so manually in dev tools:
```ts
# Get all case-comments to choose an id
GET .kibana/_search
{
"query": {
"term": {
"type": "cases-comments"
}
}
}
```
```ts
# Downgrades a case comment of id "25554290-7a36-11ec-8d37-0d0e30a77b60"
POST .kibana/_update/cases-comments:25554290-7a36-11ec-8d37-0d0e30a77b60
{
"script" : {
"source": """
ctx._source.migrationVersion['cases-comments'] = "7.16.3";
""",
"lang": "painless"
}
}
```
Restart Kibana and you should query the same `case-comments` and see that the `"rule": { "id": null, "name": null },` are all null.
Either way once you have a null rule go to `Advanced Settings -> cluster data` and ensure that you still get metrics flowing and that one is no longer counted but if you create a new one everything still works as expected:
<img width="647" alt="Screen Shot 2022-01-24 at 11 48 39 AM" src="https://user-images.githubusercontent.com/1151048/150846789-d94ac212-6c45-44cc-a663-cd304bfda22e.png">
### 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
We still don't have this for the existing telemetry and are running out of time for 8.0.0 to add them. We might re-write this part of telemetry as well so I am not adding tests just yet.
(cherry picked from commit 607feecb20)
Co-authored-by: Frank Hassanabad <frank.hassanabad@elastic.co>
Exports the uuid regexp used in to validate configuration for use in validating the data/uuid file. Also includes a `trim()` to allow newlines that could have been edited automatically via file editing or configuration management.
(cherry picked from commit f021f75aea)
Co-authored-by: Mat Schaffer <mat@elastic.co>
* Allow empty strings for required text fields in package policies
* make empty yaml check more explicit
(cherry picked from commit bf2626f101)
Co-authored-by: Mark Hopkin <mark.hopkin@elastic.co>
