## Summary
Moving ES|QL ownership to the new esql project team
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Added documentation explaining how SO migrations on serverless work
## Preview
<img width="741" alt="Screenshot 2024-03-22 at 16 15 13"
src="2217c01f-8447-4f22-a782-a07ff221aa42">
## Summary
Whenever a test is failing and the label `failed-test` is added or a
test is skipped, then a notification will be sent to the slack channel
of preference of the team. Currently this is enabled only for Security
Solution.
This PR depends on completion of the [PR in
kibana-operations](https://github.com/elastic/kibana-operations/pull/72)
## Summary
Fixes#178753. Adds blurb and doc link about scaling resources when
deploying Elastic Agent on Kubernetes.
Applies to both managed and standalone K8 manifest workflows:
<img width="699" alt="image"
src="2e9773c5-e4b5-4003-a0a9-de4445f56c6a">
<img width="766" alt="image"
src="62c1bf79-fbde-4096-ac56-6539e700c6b8">
### 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)
## Summary
This PR combines the chart type selection options into a single,
layer-based chart switch. This improves the user experience by
streamlining the process of switching between chart types in Lens
visualizations.
Fixes https://github.com/elastic/kibana/issues/163721
<img width="1365" alt="Screenshot 2024-03-25 at 10 46 24"
src="cc36220e-aea0-4e4d-9436-948265f185a1">
Functionality:
Multilayer Charts: Switching to a compatible option (e.g., vertical bar
to line) will only convert that specific layer.
Multilayer Charts: Switching to incompatible, multilayer option (e.g.,
horizontal to vertical) will convert all layers to the new type.
Multilayer to Single Layer: Switching to a single-layer chart type (line
-> pie) will create the new chart based on the layer where you clicked
the dropdown.
Benefits:
Simpler Interface: Reduces confusion by offering a single, unified way
to switch chart types.
Improved Workflow: Makes it easier to customize individual layers or
switch the entire visualization type.
Note: In Discover, due some architectural problems, we can only convert
to compatible types so the chart switch is limited:
<img width="483" alt="Screenshot 2024-03-25 at 11 19 02"
src="ffd60e19-18c9-443a-87ce-27e111f1bdf4">
<img width="493" alt="Screenshot 2024-03-25 at 11 19 07"
src="9b5d31ed-105a-4515-8d96-4fd291a3b427">
This PR brings in add new field component in index management page and
update mappings in Serverless and Stack. New mappings can be viewed in
Json and list view.
Features:
- Can add new mapping to an index
- Cancel adding a new fields when new unsaved fields are empty
- New fields can be viewed in Json and list view in a toggle button
- List view shows nested fields
- Able to search existing fields
- Shows error message when save mappings fail
7e860360-1ff7-4968-b56d-bbeba2284ef0
### 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
---------
Co-authored-by: Kibana Machine <42973632+kibanamachine@users.noreply.github.com>
## Summary
Closes https://github.com/elastic/kibana/issues/177925.
This gives a light refresh to the Dashboard UI, primarily around panel
styling.
#### View mode
| Before | After |
|--------|--------|
| <img width="1409" alt="Screenshot 2024-03-12 at 8 29 40 AM"
src="aeac42dd-9dd4-4885-ba6c-9d5fd407522d">
|<img width="1407" alt="Screenshot 2024-03-12 at 8 40 26 AM"
src="d96d5b0d-d79c-44cc-baa1-0d21a52ac01f">|
#### Edit Mode
| Before | After |
|--------|--------|
| <img width="1408" alt="Screenshot 2024-03-12 at 8 29 31 AM"
src="a7694c17-8cda-4392-b396-e2bce1bbdc16">|
<img width="1407" alt="Screenshot 2024-03-12 at 8 40 19 AM"
src="a3e3e316-c339-4c7b-bd1b-f24c997ac3c9">
|
### Changes:
- Replaces shadows surrounding panels with thin borders
| Before | After |
|--------|--------|
| <img width="703" alt="Screenshot 2024-03-12 at 6 57 50 PM"
src="9da34f91-6e76-41a9-9526-2d9a593241a1">
| <img width="703" alt="Screenshot 2024-03-12 at 1 08 04 PM"
src="b4f0c7d6-8d3f-4ac9-a80b-a813d4288db1">
|
- Increases space between panel title and panel description icon
| Before | After |
|--------|--------|
| <img width="326" alt="Screenshot 2024-03-12 at 1 08 53 PM"
src="a6568436-0936-4b57-b897-4bfb21425990">
| <img width="324" alt="Screenshot 2024-03-12 at 1 10 54 PM"
src="e9315987-8dd1-475a-8788-f7fecdec3dc8">
|
- Adds spacer after title/description form in panel settings
| Before | After |
|--------|--------|
| 
| 
|
- Reduces left padding with no title and has a badge
| Before | After |
|--------|--------|
| <img width="353" alt="Screenshot 2024-03-12 at 7 00 00 PM"
src="27061ce3-575d-4c66-96ac-0818fb438d42">
| <img width="352" alt="Screenshot 2024-03-12 at 7 00 56 PM"
src="e973cfbf-f1d7-45cd-9adb-a15882ffe3de">
|
- Removes dashed border in edit mode
| Before | After |
|--------|--------|
| <img width="353" alt="Screenshot 2024-03-12 at 7 03 28 PM"
src="ddb31b14-5ff7-4089-b4cf-3fc28733f360">
| <img width="354" alt="Screenshot 2024-03-12 at 7 03 11 PM"
src="da3a99c9-6aa5-49c1-ae96-2babebcc6c16">
|
- Adds title to tooltip when a panel has a description
| Before | After |
|--------|--------|
| <img width="338" alt="Screenshot 2024-03-12 at 7 04 15 PM"
src="23d7c0ef-9a58-41cc-a0e7-38b5f1adbe7d">
| <img width="339" alt="Screenshot 2024-03-12 at 1 10 59 PM"
src="4b92bd3e-db0a-49e7-bfaa-751a846a4545">
|
- Enables edits to panel description when title is disabled (because the
panel description icon/tooltip shows even when title is hidden)
| Before | After |
|--------|--------|
| <img width="389" alt="Screenshot 2024-03-12 at 7 15 16 PM"
src="e1ff2532-33f0-4bf8-980f-18d59dcf6b7c">
| <img width="398" alt="Screenshot 2024-03-12 at 7 13 51 PM"
src="72e6761e-f0dd-4c5d-8c61-2bdcabd65f1d">
|
### 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
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1) was
used on any tests changed
- [ ] 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)
fixes https://github.com/elastic/kibana/issues/179378
## Summary
This PR fixes a problem introduced by a refactoring in the charts config
catalog, which removed the `breakdown` config from the charts in the
Hosts View
<img width="691" alt="image"
src="0bfe6093-887b-4a46-8d53-2580fea9ee39">
### How to test
- Start a local Kibana instance
- Either point it to an oblt-cli cluster or run the
`infra_hosts_with_apm_hosts.ts` synthtrace scenario (we need more than 1
host in the page)
- Navigate to `Infrastructure > Hosts` and also validate the asset
details page
Towards: https://github.com/elastic/kibana/issues/169867
This PR onboards Latency Threshold rule type with FAAD.
### To verify
1. Run the following script to generate APM data:
```
node scripts/synthtrace simple_trace.ts --local --live
```
2. Create a latency threshold rule.
Example:
```
POST kbn:/api/alerting/rule
{
"params": {
"aggregationType": "avg",
"environment": "ENVIRONMENT_ALL",
"threshold": 400,
"windowSize": 5,
"windowUnit": "m"
},
"consumer": "alerts",
"schedule": {
"interval": "1m"
},
"tags": [],
"name": "testinggg",
"rule_type_id": "apm.transaction_duration",
"notify_when": "onActionGroupChange",
"actions": []
}
```
3. Your rule should create an alert and should saved it in
`.internal.alerts-observability.apm.alerts-default-000001`
Example:
```
GET .internal.alerts-*/_search
```
4. Set `threshold: 10000`
5. The alert should be recovered and the AAD in the above index should
be updated `kibana.alert.status: recovered`.
## Summary
Fixed install package script, it was missing version header. It turned
out the job was failing since last summer:
https://buildkite.com/elastic/kibana-fleet-packages
Added a notification section to send notification to
#fleet-notifications slack channel on failed builds.
Ran locally:
```
│ info ✅ juniper@1.2.0 took 31.24s
│ info ✅ dga@2.0.1 took 12.603s
│ info ✅ security_detection_engine@8.13.2 took 5.152s
│ info ✅ aws@2.13.1 took 5.115s
│ info ✅ jumpcloud@1.10.0 took 4.199s
│ info ✅ ti_threatconnect@0.3.0 took 4.126s
│ info ✅ cloudflare_logpush@1.18.0 took 4.101s
│ info ✅ beaconing@1.2.0 took 4.068s
│ info ✅ arista_ngfw@1.1.0 took 4.066s
│ info ✅ google_workspace@2.20.0 took 4.064s
│ info ✅ linux@0.6.9 took 3.443s
│ info ✅ influxdb@0.7.0 took 3.167s
│ info ✅ snort@1.15.0 took 3.157s
│ info ✅ ti_misp@1.32.0 took 3.139s
│ info ✅ endpoint@8.14.0-prerelease.0 took 3.127s
│ info ✅ ti_crowdstrike@0.5.3 took 3.124s
│ info ✅ lmd@2.1.2 took 3.118s
│ info ✅ ti_anomali@1.20.0 took 3.109s
│ info ✅ vectra_detect@1.7.2 took 3.097s
│ info ✅ hadoop@1.5.2 took 3.095s
│ info ✅ proofpoint@0.9.1 took 3.092s
│ info ✅ redis@1.14.0 took 3.092s
│ info ✅ citrix_waf@1.14.0 took 3.091s
│ info ✅ nagios_xi@1.2.1 took 3.09s
│ info ✅ microsoft_defender_cloud@1.1.1 took 3.089s
│ info ✅ sysmon_linux@1.6.2 took 3.088s
│ info ✅ thycotic_ss@1.7.0 took 3.085s
│ info ✅ cyberark_pta@1.9.0 took 3.082s
│ info ✅ salesforce@0.14.0 took 3.081s
│ info ✅ trendmicro@2.2.0 took 3.079s
│ info ✅ netscout@0.20.0 took 3.078s
│ info ✅ proofpoint_tap@1.17.0 took 3.078s
│ info ✅ ti_rapid7_threat_command@1.15.0 took 3.076s
│ info ✅ cloud_security_posture@1.9.0-preview01 took 3.075s
│ info ✅ nats@1.5.1 took 3.075s
│ info ✅ sonicwall@0.8.2 took 3.075s
│ info ✅ websphere_application_server@1.3.0 took 3.074s
│ info ✅ netskope@1.17.0 took 3.072s
│ info ✅ ti_mandiant_advantage@1.1.1 took 3.072s
│ info ✅ m365_defender@2.8.0 took 3.071s
│ info ✅ zscaler_zpa@1.17.0 took 3.071s
│ info ✅ modsecurity@1.18.0 took 3.068s
│ info ✅ redisenterprise@0.9.0 took 3.068s
│ info ✅ sentinel_one_cloud_funnel@0.13.0 took 3.066s
│ info ✅ apache_tomcat@1.4.0 took 3.065s
│ info ✅ apm@8.13.1-preview-1708411360 took 3.065s
│ info ✅ azure_metrics@1.4.2 took 3.065s
│ info ✅ cisco_meraki@1.21.2 took 3.064s
│ info ✅ azure@1.10.0 took 3.063s
│ info ✅ checkpoint@1.31.0 took 3.063s
│ info ✅ zeek@2.24.0 took 3.063s
│ info ✅ iptables@1.16.0 took 3.062s
│ info ✅ qualys_vmdr@2.1.0 took 3.061s
│ info ✅ microsoft_sqlserver@2.5.0 took 3.059s
│ info ✅ box_events@2.7.0 took 3.058s
│ info ✅ google_scc@1.1.1 took 3.058s
│ info ✅ hid_bravura_monitor@1.17.2 took 3.057s
│ info ✅ ibmmq@1.2.4 took 3.056s
│ info ✅ awsfirehose@0.5.0 took 3.055s
│ info ✅ memcached@1.3.0 took 3.054s
│ info ✅ microsoft_exchange_server@0.1.2 took 3.054s
│ info ✅ prisma_cloud@1.1.1 took 3.054s
│ info ✅ oracle_weblogic@1.5.0 took 3.053s
│ info ✅ pps@0.0.1 took 3.053s
│ info ✅ gcp@2.33.1 took 3.052s
│ info ✅ jamf_compliance_reporter@1.12.0 took 3.052s
│ info ✅ amazon_security_lake@1.1.0 took 3.051s
│ info ✅ bluecoat@0.17.2 took 3.051s
│ info ✅ activemq@1.2.0 took 3.05s
│ info ✅ barracuda@1.12.0 took 3.05s
│ info ✅ tanium@1.8.0 took 3.049s
│ info ✅ trellix_epo_cloud@1.10.0 took 3.049s
│ info ✅ imperva_cloud_waf@0.3.0 took 3.048s
│ info ✅ lyve_cloud@1.13.0 took 3.048s
│ info ✅ juniper_junos@0.10.1 took 3.047s
│ info ✅ ceph@1.4.0 took 3.046s
│ info ✅ nginx_ingress_controller@1.8.2 took 3.046s
│ info ✅ cassandra@1.12.0 took 3.045s
│ info ✅ cribl@0.3.0 took 3.045s
│ info ✅ istio@0.5.0 took 3.045s
│ info ✅ hashicorp_vault@1.24.0 took 3.044s
│ info ✅ kafka@1.13.0 took 3.043s
│ info ✅ azure_functions@0.4.0 took 3.042s
│ info ✅ auth0@1.15.0 took 3.04s
│ info ✅ imperva@1.1.0 took 3.039s
│ info ✅ infoblox_bloxone_ddi@1.16.0 took 3.038s
│ info ✅ bitdefender@1.12.0 took 3.037s
│ info ✅ cisco_secure_email_gateway@1.23.0 took 3.037s
│ info ✅ problemchild@2.1.2 took 3.036s
│ info ✅ juniper_netscreen@0.10.1 took 3.032s
│ info ✅ infoblox@0.8.1 took 3.023s
│ info ✅ 1password@1.27.0 took 2.728s
│ info ✅ kafka_log@1.6.0 took 2.118s
│ info ✅ keycloak@1.21.0 took 2.117s
│ info ✅ fortinet_fortiedr@1.15.0 took 2.108s
│ info ✅ network_traffic@1.30.0 took 2.098s
│ info ✅ prometheus_input@0.4.0 took 2.091s
│ info ✅ rabbitmq@1.13.0 took 2.091s
│ info ✅ ping_one@1.14.0 took 2.089s
│ info ✅ vsphere@1.11.1 took 2.087s
│ info ✅ snyk@1.20.1 took 2.086s
│ info ✅ okta@2.8.0 took 2.085s
│ info ✅ kibana@2.5.2 took 2.084s
│ info ✅ log@2.3.1 took 2.082s
│ info ✅ mongodb@1.13.2 took 2.082s
│ info ✅ microsoft_exchange_online_message_trace@1.19.0 took 2.08s
│ info ✅ panw@3.24.0 took 2.08s
│ info ✅ ti_abusech@1.25.0 took 2.078s
│ info ✅ php_fpm@1.2.1 took 2.077s
│ info ✅ qnap_nas@1.20.0 took 2.077s
│ info ✅ microsoft_dhcp@1.24.2 took 2.076s
│ info ✅ oracle@1.24.3 took 2.076s
│ info ✅ osquery@1.19.0 took 2.076s
│ info ✅ statsd_input@0.2.3 took 2.075s
│ info ✅ system_audit@1.10.1 took 2.075s
│ info ✅ zscaler_zia@2.19.0 took 2.075s
│ info ✅ logstash@2.4.3 took 2.074s
│ info ✅ lumos@0.1.0 took 2.074s
│ info ✅ udp@1.19.0 took 2.074s
│ info ✅ windows@1.44.4 took 2.074s
│ info ✅ kubernetes@1.58.0 took 2.073s
│ info ✅ netflow@2.18.0 took 2.073s
│ info ✅ zerofox@1.23.0 took 2.072s
│ info ✅ zookeeper@1.10.0 took 2.072s
│ info ✅ lastpass@1.15.0 took 2.07s
│ info ✅ ti_cif3@1.11.0 took 2.07s
│ info ✅ wiz@1.1.1 took 2.07s
│ info ✅ azure_billing@1.5.0 took 2.069s
│ info ✅ platform_observability@0.0.2 took 2.069s
│ info ✅ sql@0.4.0 took 2.068s
│ info ✅ tines@1.11.0 took 2.068s
│ info ✅ mysql@1.19.0 took 2.067s
│ info ✅ elastic_agent@1.18.0 took 2.066s
│ info ✅ panw_cortex_xdr@1.25.0 took 2.066s
│ info ✅ ti_util@1.5.0 took 2.066s
│ info ✅ tomcat@1.10.0 took 2.066s
│ info ✅ winlog@2.1.1 took 2.066s
│ info ✅ system@1.54.0 took 2.065s
│ info ✅ apache@1.17.0 took 2.064s
│ info ✅ darktrace@1.16.0 took 2.064s
│ info ✅ mysql_enterprise@1.14.2 took 2.064s
│ info ✅ pfsense@1.19.0 took 2.063s
│ info ✅ profiler_agent@8.12.0 took 2.063s
│ info ✅ ti_recordedfuture@1.22.0 took 2.062s
│ info ✅ squid@0.19.3 took 2.061s
│ info ✅ couchbase@1.5.0 took 2.06s
│ info ✅ cyberarkpas@2.20.0 took 2.06s
│ info ✅ ded@2.1.1 took 2.06s
│ info ✅ synthetics_dashboards@1.0.1 took 2.06s
│ info ✅ coredns@0.6.1 took 2.059s
│ info ✅ mimecast@1.23.0 took 2.059s
│ info ✅ nginx@1.20.0 took 2.059s
│ info ✅ ti_otx@1.24.1 took 2.059s
│ info ✅ cockroachdb@1.9.0 took 2.058s
│ info ✅ sophos@3.9.0 took 2.058s
│ info ✅ google_cloud_storage@1.1.0 took 2.056s
│ info ✅ journald@1.1.0 took 2.056s
│ info ✅ sophos_central@1.14.0 took 2.056s
│ info ✅ synthetics@1.2.1 took 2.056s
│ info ✅ microsoft_defender_endpoint@2.24.1 took 2.055s
│ info ✅ osquery_manager@1.11.0 took 2.055s
│ info ✅ symantec_edr_cloud@1.1.0 took 2.055s
│ info ✅ azure_frontdoor@1.7.0 took 2.054s
│ info ✅ forcepoint_web@1.8.0 took 2.054s
│ info ✅ stan@1.5.0 took 2.054s
│ info ✅ traefik@1.11.1 took 2.054s
│ info ✅ trend_micro_vision_one@1.16.0 took 2.054s
│ info ✅ cisa_kevs@0.1.0 took 2.053s
│ info ✅ fireeye@1.22.0 took 2.053s
│ info ✅ infoblox_nios@1.21.0 took 2.053s
│ info ✅ o365@2.3.0 took 2.053s
│ info ✅ suricata@2.21.0 took 2.053s
│ info ✅ tenable_io@2.9.0 took 2.053s
│ info ✅ ti_cybersixgill@1.27.0 took 2.053s
│ info ✅ containerd@0.3.0 took 2.052s
│ info ✅ jolokia@0.3.0 took 2.052s
│ info ✅ sonicwall_firewall@1.16.0 took 2.052s
│ info ✅ spring_boot@1.4.0 took 2.052s
│ info ✅ tcp@1.19.0 took 2.052s
│ info ✅ ti_maltiverse@1.1.0 took 2.052s
│ info ✅ cisco_ise@1.22.0 took 2.051s
│ info ✅ fortinet_fortigate@1.25.1 took 2.051s
│ info ✅ sentinel_one@1.20.0 took 2.051s
│ info ✅ tenable_sc@1.21.0 took 2.051s
│ info ✅ fleet_server@1.5.0 took 2.05s
│ info ✅ azure_application_insights@1.4.0 took 2.049s
│ info ✅ cef@2.17.0 took 2.049s
│ info ✅ juniper_srx@1.21.0 took 2.049s
│ info ✅ zoom@1.19.0 took 2.049s
│ info ✅ awsfargate@1.0.0 took 2.048s
│ info ✅ crowdstrike@1.32.1 took 2.048s
│ info ✅ zeronetworks@1.12.0 took 2.048s
│ info ✅ akamai@2.23.0 took 2.047s
│ info ✅ barracuda_cloudgen_firewall@1.11.0 took 2.047s
│ info ✅ eset_protect@0.3.0 took 2.047s
│ info ✅ cisco_umbrella@1.22.0 took 2.046s
│ info ✅ httpjson@1.20.0 took 2.046s
│ info ✅ iis@1.17.4 took 2.046s
│ info ✅ bitwarden@1.11.0 took 2.045s
│ info ✅ cisco_duo@1.22.0 took 2.045s
│ info ✅ cisco_secure_endpoint@2.25.0 took 2.045s
│ info ✅ couchdb@1.1.0 took 2.045s
│ info ✅ golang@1.4.0 took 2.045s
│ info ✅ haproxy@1.11.1 took 2.045s
│ info ✅ slack@1.19.0 took 2.045s
│ info ✅ auditd@3.19.1 took 2.044s
│ info ✅ entityanalytics_okta@1.1.0 took 2.044s
│ info ✅ f5@0.17.2 took 2.044s
│ info ✅ gcp_metrics@0.1.0 took 2.044s
│ info ✅ postgresql@1.19.0 took 2.044s
│ info ✅ entityanalytics_entra_id@1.1.0 took 2.043s
│ info ✅ f5_bigip@1.14.0 took 2.043s
│ info ✅ fim@1.14.1 took 2.043s
│ info ✅ beat@1.0.0-beta1 took 2.042s
│ info ✅ cel@1.9.0 took 2.042s
│ info ✅ cylance@0.19.2 took 2.042s
│ info ✅ fortinet_fortimail@2.13.0 took 2.042s
│ info ✅ github@1.28.0 took 2.042s
│ info ✅ pulse_connect_secure@1.19.0 took 2.042s
│ info ✅ rapid7_insightvm@1.9.0 took 2.042s
│ info ✅ ti_threatq@1.25.0 took 2.042s
│ info ✅ auditd_manager@1.16.2 took 2.041s
│ info ✅ carbonblack_edr@1.17.0 took 2.041s
│ info ✅ cisco_ios@1.26.2 took 2.041s
│ info ✅ cloud_defend@1.2.4 took 2.041s
│ info ✅ gcp_pubsub@1.13.0 took 2.041s
│ info ✅ ti_opencti@2.1.0 took 2.041s
│ info ✅ airflow@0.6.0 took 2.039s
│ info ✅ atlassian_bitbucket@1.23.0 took 2.039s
│ info ✅ cisco_ftd@3.2.0 took 2.039s
│ info ✅ cloudflare@2.24.0 took 2.039s
│ info ✅ enterprisesearch@1.0.1 took 2.039s
│ info ✅ fortinet_forticlient@1.10.2 took 2.039s
│ info ✅ aws_logs@1.1.0 took 2.038s
│ info ✅ fortinet_fortimanager@2.11.0 took 2.038s
│ info ✅ atlassian_confluence@1.24.0 took 2.037s
│ info ✅ azure_app_service@0.3.0 took 2.037s
│ info ✅ etcd@1.0.0 took 2.037s
│ info ✅ fortinet@1.9.0 took 2.037s
│ info ✅ http_endpoint@1.15.0 took 2.037s
│ info ✅ trellix_edr_cloud@1.1.0 took 2.037s
│ info ✅ apache_spark@1.0.3 took 2.036s
│ info ✅ elastic_package_registry@0.2.0 took 2.036s
│ info ✅ prometheus@1.15.0 took 2.036s
│ info ✅ santa@3.17.0 took 2.036s
│ info ✅ cisco_aironet@1.13.0 took 2.035s
│ info ✅ docker@2.9.0 took 2.035s
│ info ✅ elasticsearch@1.14.0 took 2.035s
│ info ✅ carbon_black_cloud@1.21.3 took 2.034s
│ info ✅ cisco_asa@2.32.0 took 2.034s
│ info ✅ symantec_endpoint@2.15.0 took 2.033s
│ info ✅ ti_eclecticiq@0.3.0 took 2.033s
│ info ✅ cisco_nexus@1.1.0 took 2.032s
│ info ✅ citrix_adc@1.4.0 took 2.032s
│ info ✅ forgerock@1.15.0 took 2.031s
│ info ✅ atlassian_jira@1.24.0 took 2.03s
│ info ✅ radware@0.19.0 took 2.03s
│ info ✅ mattermost@1.18.0 took 2.028s
│ info ✅ azure_blob_storage@1.1.0 took 2.026s
└- ✓ pass (20.0m)
└-> "after all" hook: afterTestSuite.trigger for "should work and install all packages"
└-> "after all" hook: afterTestSuite.trigger in "Fleet packages test"
1 passing (20.0m)
```
Towards: https://github.com/elastic/kibana/issues/169867
This PR onboards "Custom Threshold" rule type with FAAD.
## To verify
Create a Custom Threshold rule by using a test index and DW. Set the
`Role visibility` `metrics`.
When the rule runs, it generates an alert and saves it under
`.internal.alerts-observability.threshold.alerts-default`.
The alert should be visible on `Observability > alerts` page as well.
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
This PR updates the ES|QL grammars (lexer and parser) to match the
latest version in Elasticsearch.
## Edit by @dej611
* Introduced new `META` command (with the only `FUNCTIONS` option) who
replaced the previous `SHOW FUNCTIONS`
* add new `meta` command into the commands definitions
* make it work with both validation and autocomplete
* updated ES|QL theme with new `meta` command
* Removed the `FUNCTIONS` function from the `SHOW` command
* tweaked the `show` command definition
* fix both validation and autocomplete
* removed some unused code after the grammar changes
---------
Co-authored-by: dej611 <dej611@gmail.com>
Co-authored-by: Marco Liberati <dej611@users.noreply.github.com>
## Summary
Closes#164952
Apparently part of the task was already done via #173770 but the issue
hasn't been updated.
I've now added one more example just to show a practical usage of
`time_range()` but the other 2 constant functions have already
meaningful examples in place.
### Checklist
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html)
was added for features that require explanation or tutorials
## Summary
Resolves https://github.com/elastic/kibana/issues/179362
Handles transaction name for APM alert visualizations on the alert
details page.
<img width="1092" alt="Screenshot 2024-03-25 at 12 25 04 PM"
src="576edc66-42a9-4e26-af9b-784d3b21b23c">
<img width="1441" alt="Screenshot 2024-03-25 at 12 17 01 PM"
src="aca84148-87f8-445e-a14e-57a6b87558f7">
### Testing
1. Create APM data. I used `node scripts/synthtrace many_transactions.ts
--live`
2. Create a latency threshold rule filtered with transaction name. I
used `UPDATE /payments-1997` from that data set and threshold as 1500 ms
3. Navigate to the service page and click on the transaction name to
observe the visualizations
4. Navigate to the alert, then the alert details page. Observe that the
visualizations match the visualizations on the transaction page.
### Release note
APM alert details page visualizations are now filtered by transaction
name when transaction name is defined on the APM latency rule type.
Towards: https://github.com/elastic/kibana/issues/169867
This PR onboards "SLO burn rate" rule type with FAAD.
## To verify
Create an SLO by using a test index (create a dataview for it), use very
low `budget consumed %`
The rule bound to the SLO should create an alert and save it under
`.internal.alerts-observability.slo.alerts-default-000001`
## Summary
Fixes the `Was this helpful?` text when the conversation list is open
and the viewport is smaller by wrapping the text
**Before**
**Now**
<img width="915" alt="image"
src="05015f7f-bcf0-4e8e-9bc6-9516839e11a5">
## Summary
Display Header sub heading as children of page template !!
### After
<img width="1728" alt="image"
src="d6198df4-40b7-488f-a7df-0fcbc514a371">
## Summary
We're spending ~200ms (on benchmark machine) in the `start` lifecycle of
the `home` plugin.
After some investigations, this time is spent evaluating the tutorial
providers, here:
c713b91e66/src/plugins/home/server/services/tutorials/tutorials_registry.ts (L140-L143)
A significant amount of time and GC cycles are spent generating the
various instructions for all those tutorials.
I feel like the proper solution would be to have those instructions
(`TutorialSchema.onPrem`, `TutorialSchema.elasticCloud` and
`TutorialSchema.onPremElasticCloud`) living on the browser-side only
(given the server don't really need to know about them), however doing
it would imply some serious refactoring (especially to handle
externally-registered tutorials..), so for now this PR just adds some
cache, reducing those `200ms` to around `110ms`, so almost in half
## Summary
Fix for the flaky infra_hosts_view journey:
```
...
[01:01:17] │ debg waitForRender: 7 out of 5 are loaded...
[01:01:17] │ debg waitForRender: 7 out of 5 are loaded...
[01:01:18] │ debg waitForRender: 7 out of 5 are loaded...
[01:01:18] │ debg waitForRender: 7 out of 5 are loaded...
[01:01:19] │ debg waitForRender: 7 out of 5 are loaded...
...
[01:01:20] └- ✖ fail: Journey[infra_hosts_view] Navigate to Hosts view and load 500 hosts
[01:01:20] │ Error: timed out waiting for rendering of 5 elements with selector .echChartStatus is completed
[01:01:20] │ at onFailure (retry_for_truthy.ts:39:13)
[01:01:20] │ at retryForSuccess (retry_for_success.ts:84:7)
[01:01:20] │ at retryForTruthy (retry_for_truthy.ts:27:3)
[01:01:20] │ at RetryService.waitForWithTimeout (retry.ts:73:5)
[01:01:20] │ at KibanaPage.waitForRender (kibana_page.ts:54:5)
[01:01:20] │ at KibanaPage.waitForCharts (kibana_page.ts:103:5)
[01:01:20] │ at Object.fn (infra_hosts_view.ts:32:5)
[01:01:20] │ at journey_ftr_harness.ts:499:15
[01:01:20] │ at JourneyFtrHarness.withSpan (journey_ftr_harness.ts:350:22)
[01:01:20] │ at Context.<anonymous> (journey_ftr_harness.ts:497:11)
[01:01:20] │ at Object.apply (wrap_function.js:73:16)
```
The failure is due to playwright was able to find 7 charts instead of 5
(expected)
It turned out the Infra page has 5 metric charts + 2 Control inputs + 12
Lens embeddables: seems like some of rendering is async and depends on
screen viewport size.
PR is adding `parentLocator` to `waitForRender` function as opt-in
argument that helps to locate charts inside the specified parent
element.
How to test:
perf run: `node scripts/run_performance.js --journey-path
x-pack/performance/journeys_e2e/infra_hosts_view.ts`
test run: `node scripts/functional_tests.js --config
x-pack/performance/journeys_e2e/infra_hosts_view.ts`
