## Summary
Fix https://github.com/elastic/kibana/issues/165166
- remove `getAllIndices` from the SO service's setup contract
- adapt `getAllIndices` from the start contract to only return indices
that are effectively present in the current environment
Closes#164657
## Summary
- Improve kbn/es docs to include prerequisites for using serverless
- Better guidance to use `--ssl` flag to enable security
- Alert the user how to authenticate with Elastic registry if it fails
- Guidance for using `--ssl` and authentication
## Summary
If a user is running serverless ES in the cloud and serverless KBN
locally, passing the token can trigger an invalid configuration error:
`serviceAccountToken cannot be specified when "username" is also
defined`
Additionally, the token is likely invalid anyways because the SES
instance was not seeded with it. This PR checks the
`elasticsearch.hosts` configuration for non-localhost values before
passing along the token.
## Testing
Add something like the following to `config/kibana.dev.yml` and run
`yarn serverless`. Should not get a configuration error.
```yml
elasticsearch.hosts: https://xxxxxxxxxx.es.us-west2.gcp.elastic-cloud.com:443
elasticsearch.username: kibana_system_user
elasticsearch.password: xxxxxxxxxxxxxx
```
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
The config does not propagate to downstream workflow jobs in all cases
so things break if we don't use the default. Therefore we will make dev
the exception.
Update the gpctl config we reference in the gitops repo. The default
config needs to be the promotion workflow and dev needs to be separate
otherwise other promotion infrastructure breaks since it does not know
to look for the overridden config.
https://github.com/elastic/serverless-gitops/pull/688
Slack: https://elastic.slack.com/archives/C9PPG4EJH/p1693480365606699
Resolves#162518
This PR updates the logic that detects whether Kibana has booted
correctly during interactive setup.
The issue described in #162518 was a false positive and only effected
Kibana when run in development mode.
We already have end-to-end tests which go through the entire enrollment
flow and ensure that Kibana correctly redirects to the login page once
interactive setup completes:
https://github.com/elastic/kibana/blob/main/test/interactive_setup_functional/tests/enrollment_token.ts#L78-L81
These tests passed with both the previous and the updated logic.
However, the end-to-end tests do not check development mode which is why
the build never failed and we started seeing this issue.
Closes https://github.com/elastic/kibana/issues/160253.
### Changes
- Schema was added to observabilityOnboarding SO
- `x-elastic-internal-origin` was added to requests from installation
script
This is a follow up of https://github.com/elastic/kibana/pull/165311
Instead of duplicating the key we are only importing from
`@kbn/dev-utils` if the package is available. The serve file is also
load under dist mode where the devOnly dependencies are not availble and
as such we can't reliable load from them.
## Summary
This PR made updates to section titles and wordings in expandable flyout
according to [docs
suggestions](https://github.com/elastic/kibana/issues/164786).
## Right panel
**Response**
- Updated empty response message
**Visualizations -> Session viewer preview**
- Added upsell message when user does not have enterprise license
- Added empty message when session viewer preview is not available
**Visualizations -> Analyzer preview**
- Added empty message
**Investigation -> Investigation guide**
- Updated empty message when investigation guide is not available
**Insights -> Prevalence**
- Updated empty message when no filed/value pair meets prevalence
threashold
**Insights -> Entities**
- Updated empty message when neither host name or user name are present
## Left panel
**Insights -> Entities**
- Updated empty state message
- "User info" -> "User information"
- Tooltip and empty table message in related hosts table
- "Host info" -> "Host information"
- Tooltip and empty table message in related users table
**Insights -> Threat Intelligence**
- Updated title to lower case
- Updated empty message for threat match detected and enriched with
threat intelligence sections
- Updated tooltips
**Investigation**
- Updated empty state message to stay consistent with right section
**Insights -> Correlations**
- Updated table message when no item is found
**Insights -> Prevalence**
- Added tooltips to each column other than `Field` and `Value`
**Response**
- Updated empty state message to match response section on right section
### Checklist
Delete any items that are not applicable to this PR.
- [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
Fixes https://github.com/elastic/kibana/issues/165183
### Test instructions
1) install any sample data set
2) open new dashboard
3) Use "Add panel" buttons to add by-value map with only base map layer
4) Ensure map tiles fill entire map panel in dashboard
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Fix#165216
Fixed for any dimension panel:
<img width="269" alt="Screenshot 2023-08-31 at 14 22 24"
src="2a8eb2c0-747f-4918-997b-1b059339a242">
<img width="275" alt="Screenshot 2023-08-31 at 14 37 46"
src="0ef218b3-1400-4eb9-8f4b-65eee814e0ac">
This has been addressed also in the annotation panel:
<img width="262" alt="Screenshot 2023-08-31 at 14 37 00"
src="22967182-b9bb-49c4-bfb8-48f25babd128">
## Summary
When we run tests on MKI, we cannot override Elasticsearch security
realm definitions. This means that any of our tests relying on a custom
Elasticsearch security realm (SAML and JWT) won't work on MKI.
## How to test
See `Kibana serverless cheat sheet` on how to run tests against MKI.
Until https://github.com/elastic/qaf-tests/pull/30 is merged, you'd need
to also add `--exclude-tag=skipMKI` to the test runner command.
/cc @dmlemeshko
https://github.com/elastic/elasticsearch/pull/97865 expands
index-pattern expressions to include a cluster alias for purposes of
excluding an entire cluster from a cross-cluster search. This allows
users to put the minus sign in front of the cluster name
(`-cluster_one:*`). The advantage to this change is that it avoids
sending any network calls to that cluster. Compare this to the existing
syntax for excluding clusters, where the minus sign is in front of the
index name (`cluster_one:-*`). The older syntax has to send the request
to the remote cluster, which if it is down (and skip_unavailable=false),
will cause the search to fail.
This PR updates the docs to reflect the new syntax.
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
Due to an existing (but already resolved) bug in elastic-chart, the Lens Heatmap introduced a workaround to avoid a reduction in the size of the heatmap chart in the suggestions panel due to the length of the axis labels.
After the fix was resolved in elastic-charts, the workaround was not removed and left a bug in the interface.
This commit removes the workaround introduced.
Attempt at fixing https://github.com/elastic/kibana/issues/149611
I updated the test code as follows:
* Removed the RxJS logic and simply factorised the reads to read only
once.
* Got rid of the "retry" service. There's already a mechanism in place
to make sure the logs are up-to-date.
* Updated the `setCommonlyUsedTime` method to make sure it awaits for
the popup to be ready before clicking.
* Skipped 4 tests that seem outdated, the logs don't have the related
entries even after waiting for more than one minute and flushing (in
fact, they all seem to systematically fail on `main` too):
* lnsLegacyMetric
* [Flights] Delays & Cancellations
* [Flights] Destination Weather
* [Flights] Delay Buckets
Attached is the generated
[kibana.log](12260144/kibana.log)
(focussing only the `browser.ts` tests).
So for the skipped tests, this does not look like flakiness anymore, but
rather outdated / incorrect checks. I propose we review and update them
on a separate issue / PR.
50 runs results
[here](https://buildkite.com/elastic/kibana-flaky-test-suite-runner/builds/3026).
## Summary
Adds a pipeline that will trigger the promotion and QG for kibana
through qa -> staging -> production whenever the tag which [matches the
regex](https://regex101.com/r/tY52jo/1) is created.
Sibling PR [here](https://github.com/elastic/serverless-gitops/pull/661)
that defines `main/gen/gpctl/kibana/tagged-release.yaml`
The meat of the PR is the regex.
---------
Co-authored-by: Thomas Watson <w@tson.dk>
Co-authored-by: Alex Szabo <delanni.alex@gmail.com>
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
