Raya Fratkina
fc332241fe
Update advanced-settings.md to clarify space-specific vs global ( #224951 )
...
## Summary
The description of space-specific vs global settings was unclear. This
PR cleans up the language around space-specific vs global settings
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] 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/src/platform/packages/shared/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
- [ ] 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 was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
### Identify risks
Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.
- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx )
- [ ] ...
---------
Co-authored-by: Kaarina Tungseth <kaarina.tungseth@elastic.co>
2025-06-25 10:28:20 -04:00
Shubha Anjur Tupil
8d34975d30
Update elastic-managed-llm.md ( #225108 )
...
Remove the early access form since we started rolling out.
## Summary
Summarize your PR. If it involves visual changes include a screenshot or
gif.
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] 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/src/platform/packages/shared/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
- [ ] 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 was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
### Identify risks
Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.
- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx )
- [ ] ...
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
2025-06-24 18:46:34 +00:00
Arianna Laudazzi
26d064520d
Configure Microsoft Teams - update the config steps to post messages in a private group ( #224799 )
...
This PR updates the
https://www.elastic.co/docs/reference/kibana/connectors-kibana/teams-action-type#configuring-teams
page by adding a note on how to post messages in a private group.
Closes https://github.com/elastic/obs-docs-projects/issues/283
2025-06-24 11:28:45 +02:00
Brijesh Khunt
de031df3f6
[Connector][TheHive] Show rule severity toggle and body jsoneditor in UI ( #224669 )
...
## Summary
- This PR unhides rule severity toggle and body jsoneditor in UI. (kept
hidden in PR : #207255 )
- Add functional test related to `createAlert` subaction.
- Remove unused variables from `translations.ts`.
- Remove the custom template description from documentation.
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [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/src/platform/packages/shared/kbn-i18n/README.md )
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html )
were updated or added to match the most common scenarios
- [x] 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 )
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-06-24 11:53:46 +03:00
Walter M. Rafelsberger
b0f2c611f2
Remove legacy time axis advanced setting ( #221419 )
...
## Summary
Follow up to #210579 . Close #193683 .
This PR removes the deprecated `visualization:useLegacyTimeAxis`
advanced setting and all related code. This setting was previously used
to enable legacy time axis behavior for charts in Lens, Discover,
Visualize and TSVB, but has been deprecated and is no longer needed. All
usage of the setting was already removed in #210579 , this PR just cleans
up the advanced setting itself.
## Changes
- Removed the `visualization:useLegacyTimeAxis` UI setting registration
from the charts plugin
- Removed `LEGACY_TIME_AXIS` constant export from charts common module
- Cleaned up related TypeScript configuration dependencies
- Removed telemetry schema entries for the deprecated setting
- Removed translation strings for the deprecated setting
- Adds a saved object migration to remove the setting (see [advanced
settings
migrations](https://docs.elastic.dev/kibana-dev-docs/tutorials/advanced-settings#registering-migrations ))
### Identify risks
- Identified that a saved object migration needs to be added for the
removal of the setting. See this
[PR](https://github.com/elastic/kibana/pull/157699 ) for reference.
- Advanced settings [can be
overridden](https://www.elastic.co/docs/extend/kibana/ui-settings-service#uisettings-overrides )
in `kibana.yml`. If the setting is present in `kibana.yml` and we remove
support for it, if verification of the file was too strict, it would
fail to start Kibana. I verified that Kibana still starts when support
for the advanced setting was removed but it's still present in
`kibana.yml`.
## Release note
Removal of the deprecated `visualization:useLegacyTimeAxis` advanced
setting.
2025-06-23 11:30:29 +02:00
Julian Gernun
411ab215a5
[Response Ops][Connectors] New xpack.actions.email.services.enabled Kibana setting ( #223363 )
...
## Summary
Closes #220288
## Release note
New kibana setting `xpack.actions.email.services.enabled` to
enable/disable email services for email connector.
2025-06-20 16:10:43 +02:00
Brijesh Khunt
3fcdc062fa
XSOAR Connector ( #212049 )
...
## Summary
XSOAR action connector, enabling users to send alerts generated by the
rule detection engine to Palo Alto XSOAR for automation and remediation.
### **create connector**
### **test connector**
1. **test page**
2. **select playbook**
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [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/src/platform/packages/shared/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
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html )
were updated or added to match the most common scenarios
- [x] 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 )
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
### 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: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Sergi Massaneda <sergi.massaneda@elastic.co>
Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-06-20 14:50:07 +02:00
Marta Bondyra
65bdf1ff8e
Optimize existing image assets with lossless compression ( #223998 )
...
## Summary
This PR applies **lossless compression** to all SVG and JPG/PNG assets
across Kibana using:
- [`svgo`](https://github.com/svg/svgo ) — for optimizing SVGs
- [`image-optimize`](https://www.npmjs.com/package/image-optimize ) — for
JPG/PNG compression
‼️ **Please scroll to ''Unknown metric groups" accordion to see what's
the gain for your code.**
<img width="542" alt="Screenshot 2025-06-18 at 13 24 20"
src="https://github.com/user-attachments/assets/191afb28-44fc-4551-9026-756a8385c66a "
/>
The goal is to reduce asset size and improve load performance without
compromising visual quality.
This PR achieves a **23 MB** reduction in asset size across all images
bundled in Kibana’s running code—meaning these compressed images
directly impact what ships in Kibana.
Some assets get bundled into chunks due to our bundling strategy but
might not actually be requested at runtime.
Additionally, I ran the same optimization script on the docs assets as a
harmless extra step, but those savings aren’t included in the 23 MB
total.
---
## Why
While working on Emotion rewrites, I noticed some SVGs seemed
unnecessarily heavy. That led to a broader investigation into our image
assets, and it turns out we’re not consistently optimizing them during
development or build.
---
## Notes
- Visual fidelity of optimized assets has been manually verified — no
visible differences
- The optimization is **lossless**, meaning no quality degradation
- Some assets (like large background images) could benefit further from
**lossy compression**
---
## Follow-ups / Ideas
1. **Automate compression in the dev/build pipeline**
- e.g. add `svgo` as a pre-commit or CI step for SVGs
2. **Improve CI reporting**
- Currently, bundle size diffs for images are hidden under "Unknown
metric groups" in the GitHub CI comment. We may want to make these more
visible.
-
3. **Audit large assets manually** — apply lossy compression where
appropriate
4. **Avoid redundant image loading**
- e.g. background images on the login page are loaded again on the space
selector page since they’re bundled twice. I’m working on a separate PR
to address that.
## Snippets I used to apply the compression
```
# Find SVG files
find . -type f -iname "*.svg" \
-not -path "*/node_modules/*" \
-not -path "*/functional/*" > svg-files.txt
# Compress SVGs
while IFS= read -r file; do
svgo "$file"
done < svg-files.txt
```
This snippet has been used for png and jpg, but the example below is for
png:
```
# Find PNG files
find . -type f -iname "*.png \
-not -path "*/node_modules/*" \
-not -path "*/functional/*" > png-files.txt
# Compress PNGs
while IFS= read -r file; do
image-optimize -f jpg "$file"
done < png-files.txt
```
2025-06-19 16:44:13 +02:00
Brijesh Khunt
884e51ae49
Implement functionality to add observables, procedures and custom fields to alerts for TheHive ( #207255 )
...
## Summary
- Added a toggle to retain the severity from the rule. When enabled,
alerts generated from the rule will inherit its severity; otherwise,
users must manually select a severity level from the dropdown.
- Added a template selection menu with predefined basic templates. These
templates come with preset configurations, including observables and
procedures, which automatically populate the Body field upon selection.
Users also have the option to modify an existing template or create a
custom one using the `Custom Template` option.
## Screenshots
### 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/src/platform/packages/shared/kbn-i18n/README.md )
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html )
were updated or added to match the most common scenarios
- [x] 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 )
- [x] This was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [x] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
Co-authored-by: Elastic Machine <elasticmachine@users.noreply.github.com>
2025-06-19 16:12:59 +02:00
Shubha Anjur Tupil
1a26254fb6
Update elastic-managed-llm.md ( #224337 )
...
Added a detail to make it clear we are not hosting the LLM but proxying
to AWS Bedrock in us-east-1
## Summary
Summarize your PR. If it involves visual changes include a screenshot or
gif.
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] 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/src/platform/packages/shared/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
- [ ] 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 was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
### Identify risks
Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.
- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx )
- [ ] ...
Co-authored-by: István Zoltán Szabó <szabosteve@gmail.com>
2025-06-18 10:05:55 +02:00
Julian Gernun
25b4f507e2
[Response Ops][Connectors] New xpack.actions.webhook.ssl.pfx.enabled config ( #222507 )
...
## Summary
Closes https://github.com/elastic/kibana/issues/220416
## Release note
New `xpack.actions.webhook.ssl.pfx.enabled` Kibana setting to disable
Webhook connector PFX file support for SSL client authentication
---------
Co-authored-by: Nastasha Solomon <79124755+nastasha-solomon@users.noreply.github.com>
2025-06-17 09:31:17 +02:00
Julian Gernun
f5b6aa241f
[Response Ops][Connectors][Email] xpack.actions.email.services.ses.host/port kibana config ( #221389 )
...
## Summary
Closes https://github.com/elastic/kibana/issues/220286
## Release note
New AWS SES Email configuration options
`xpack.actions.email.services.ses.host` and
`xpack.actions.email.services.ses.port`.
---------
Co-authored-by: Lisa Cawley <lcawley@elastic.co>
2025-06-12 08:38:08 -07:00
Antonio Piazza
8fae18a9b2
OpenAI (Other) Connector PKI implementation ( #219984 )
2025-06-06 20:43:57 +00:00
Shubha Anjur Tupil
e4b3ecb8e9
Update elastic-managed-llm.md ( #222714 )
...
Changing optimized to vetted
## Summary
Summarize your PR. If it involves visual changes include a screenshot or
gif.
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [ ] 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/src/platform/packages/shared/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
- [ ] 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 was checked for breaking HTTP API changes, and any breaking
changes have been approved by the breaking-change committee. The
`release_note:breaking` label should be applied in these situations.
- [ ] [Flaky Test
Runner](https://ci-stats.kibana.dev/trigger_flaky_test_runner/1 ) was
used on any tests changed
- [ ] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
### Identify risks
Does this PR introduce any risks? For example, consider risks like hard
to test bugs, performance regression, potential of data loss.
Describe the risk, its severity, and mitigation for each identified
risk. Invite stakeholders and evaluate how to proceed before merging.
- [ ] [See some risk
examples](https://github.com/elastic/kibana/blob/main/RISK_MATRIX.mdx )
- [ ] ...
2025-06-05 09:34:56 +02:00
István Zoltán Szabó
12ef92b462
[DOCS] Updates model card for Elastic Managed LLM ( #222314 )
...
## Summary
Related to https://github.com/elastic/search-team/issues/10095
This PR updates the Elastic Managed LLM model card to state that the
used model is Claude Sonnet 3.7 and changes the links accordingly.
<img width="935" alt="Screenshot 2025-06-03 at 11 32 06"
src="https://github.com/user-attachments/assets/6e9db480-e802-4068-849d-916f600c45d6 "
/>
### Checklist
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
2025-06-04 10:04:41 +02:00
Sergi Romeu
8ccc4859b3
[APM] Remove labs ( #222177 )
2025-06-04 10:03:40 +02:00
Sergi Romeu
5824c557f6
[ObsUX][APM][Infra] Use profiling plugin configuration instead of feature flags ( #219904 )
...
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-06-02 12:56:43 +02:00
Maryam Saeidi
3d86a175d7
Extend default log pattern on server-side to include error information ( #219940 )
...
## Release Notes
Kibana logging's pattern layout, used by default for the console
appender, will now use a new default pattern layout
`[%date][%level][%logger] %message %error`. This will include the error
name and stack trace if these were included in the log entry. To opt out
of this behavior users can omit the `%error` placeholder from their log
pattern config in kibana.yml e.g.:
```
logging:
appenders:
console:
type: console
layout:
type: pattern
pattern: "[%date][%level][%logger] %message"
```
## Summary
Previously, when we pass the error in meta, the information related to
stacktrace and error message was not available in console. This PR
changed the default pattern to also include error information if it is
provided in meta (similar to the way that the logging happens when error
is directly passed to logger.error).
New pattern: (added `%error` at the end)
```
[%date][%level][%logger] %message %error
```
Here you can see the difference:
Logger:
```
server.logger.error(
`Unable to create Synthetics monitor ${monitorWithNamespace[ConfigKey.NAME]}`,
{ error: e }
);
```
#### Before
#### After
### Alternative
We could also change the MetaConversion and include this information,
but we might have additional meta information which I am not sure if it
is OK to be logged by default. Let me know if you prefer changing
MetaConversion instead of adding a new error conversion.
<details>
<summary>Code changes for MetaConversion</summary>
```
function isError(x: any): x is Error {
return x instanceof Error;
}
export const MetaConversion: Conversion = {
pattern: /%meta/g,
convert(record: LogRecord) {
if (!record.meta) {
return '';
}
const { error, ...rest } = record.meta;
const metaString = Object.keys(rest).length !== 0 ? JSON.stringify(rest) : '';
let errorString = '';
if (isError(record.meta?.error)) {
errorString = record.meta?.error.stack || '';
}
return [metaString, errorString].filter(Boolean).join(' ');
},
};
```
</details>
Here is how adjusting meta will look like in this case:
2025-05-22 16:57:42 +02:00
Colleen McGinnis
fbda17de2d
[docs] Fix various syntax and rendering errors ( #218883 )
...
Fixes various syntax and rendering errors that might include:
* Fixing broken images
* Hardcoding book-level substitution values
* Fixing incorrectly closed blocks (admonitions, tab sets, code blocks,
dropdowns etc.)
* Fixing poorly migrated complex tables
* Fixing poorly migrated lists
* Fixing poorly migrated tab sets
* Removing inline text formatting from directive titles where they won't
be rendered (for example, inline `code` formatting in dropdown titles)
* Specifying if a version is trying to communicate if a feature was
added, deprecated, or coming (for example, during migration
`deprecated:[8.15.0]` became `[8.15.0]`, which doesn't give any
information about _what_ happened in 8.15.0)
* Note: I used an `{admonition}` for this, but you can change it to
prose or some other kind of admonition if you want.
* Fixing nested dropdowns / definition lists
* Fixing poorly migrated footnotes
* Updating references to prerelease `9.0.0` versions (using a repo-level
substitution until there is a solution to
https://github.com/elastic/docs-builder/issues/737 )
Links to pages that were updated:
| Before | After |
|---|---|
| https://www.elastic.co/docs/extend/kibana/development-documentation |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/development-documentation
|
| https://www.elastic.co/docs/extend/kibana/development-security |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/development-security
|
| https://www.elastic.co/docs/extend/kibana/development-tests |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/development-tests
|
|
https://www.elastic.co/docs/extend/kibana/external-plugin-functional-tests
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/external-plugin-functional-tests
|
| https://www.elastic.co/docs/extend/kibana/external-plugin-localization
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/external-plugin-localization
|
| https://www.elastic.co/docs/extend/kibana/interpreting-ci-failures |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/interpreting-ci-failures
|
| https://www.elastic.co/docs/extend/kibana/plugin-list |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/plugin-list
|
| https://www.elastic.co/docs/extend/kibana/sample-data |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/sample-data
|
| https://www.elastic.co/docs/extend/kibana/saved-objects-service |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/saved-objects-service
|
| https://www.elastic.co/docs/extend/kibana/sharing-saved-objects |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/sharing-saved-objects
|
| https://www.elastic.co/docs/extend/kibana/stability |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/extend/stability
|
| https://www.elastic.co/docs/reference/kibana/advanced-settings |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/advanced-settings
|
|
https://www.elastic.co/docs/reference/kibana/configuration-reference/ai-assistant-settings
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/configuration-reference/ai-assistant-settings
|
|
https://www.elastic.co/docs/reference/kibana/configuration-reference/fleet-settings
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/configuration-reference/fleet-settings
|
|
https://www.elastic.co/docs/reference/kibana/configuration-reference/general-settings
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/configuration-reference/general-settings
|
|
https://www.elastic.co/docs/reference/kibana/configuration-reference/monitoring-settings
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/configuration-reference/monitoring-settings
|
|
https://www.elastic.co/docs/reference/kibana/configuration-reference/reporting-settings
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/configuration-reference/reporting-settings
|
|
https://www.elastic.co/docs/reference/kibana/configuration-reference/task-manager-settings
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/configuration-reference/task-manager-settings
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/cases-webhook-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/cases-webhook-action-type
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/email-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/email-action-type
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/pre-configured-connectors
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/pre-configured-connectors
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/servicenow-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/servicenow-action-type
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/servicenow-itom-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/servicenow-itom-action-type
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/servicenow-sir-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/servicenow-sir-action-type
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/thehive-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/thehive-action-type
|
|
https://www.elastic.co/docs/reference/kibana/connectors-kibana/webhook-action-type
|
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/connectors-kibana/webhook-action-type
|
| https://www.elastic.co/docs/reference/kibana/kibana-audit-events |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/kibana-audit-events
|
| https://www.elastic.co/docs/reference/kibana/kibana-plugins |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/reference/kibana-plugins
|
| https://www.elastic.co/docs/release-kibana/notes/index |
https://docs-v3-preview.elastic.dev/elastic/kibana/pull/218883/release-notes/index
|
---------
Co-authored-by: wajihaparvez <wajiha.parvez@elastic.co>
2025-05-22 10:10:07 +02:00
florent-leborgne
0ce0f65f49
[Docs] Add Kibana Accessibility statement page ( #220997 )
...
This PR re-makes the Kibana accessibility statement page its own page to
ease sharing.
2025-05-20 14:11:48 +00:00
István Zoltán Szabó
e499dd4e6d
[DOCS] Adds Elastic Managed LLM to Kibana connectors ( #220247 )
...
## Summary
Related to https://github.com/elastic/search-team/issues/9890
### Checklist
Check the PR satisfies following conditions.
Reviewers should verify this PR satisfies this list as well.
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
2025-05-14 11:27:35 -07:00
Lisa Cawley
f3115c6746
[DOCS] Update CrowdStrike and SentinelOne connectors ( #219887 )
2025-05-08 11:34:40 -07:00
Lisa Cawley
154ed1ef6f
[DOCS] Microsoft Defender for Endpoint connector ( #219999 )
2025-05-08 11:34:12 -07:00
Sergi Romeu
fad881d918
[APM] Remove technical preview from apmProgressiveLoading ( #220343 )
2025-05-08 09:42:54 +02:00
Steph Milovic
0de633e01d
[GenAI Connectors] Update Default Model IDs for Bedrock and OpenAI Connectors ( #220146 )
2025-05-07 17:34:06 -06:00
Sergi Romeu
eb6a159317
[Infra] Remove enableInfrastructureAssetCustomDashboards setting ( #220210 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:enableInfrastructureAssetCustomDashboards` but keeps the
saved object, to be removed in a [follow-up
issue](https://github.com/elastic/kibana/issues/220340 ).
---------
Co-authored-by: kibanamachine <42973632+kibanamachine@users.noreply.github.com>
2025-05-07 14:21:08 +02:00
Sergi Romeu
89c91350cc
[APM] Remove apmTraceExplorerTab setting and feature ( #219063 )
...
## Summary
Part of #218501
This PR removes the advanced setting `observability:apmTraceExplorerTab`
and the feature.
2025-05-07 10:46:56 +02:00
Sergi Romeu
c47556ac08
Revert "[APM] Set apmProgressiveLoading low by default and remove technical preview" ( #220234 )
...
Reverts elastic/kibana#219067
2025-05-06 17:43:45 +02:00
Sergi Romeu
74408094ba
[APM] Remove enableContinuousRollups setting and enable it by default ( #219054 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:enableContinuousRollups` and enables the feature by
default
2025-05-06 15:03:39 +02:00
Sergi Romeu
b4b3824509
[APM] Remove enableAwsLambdaMetrics setting and enable it by default ( #219057 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:enableAwsLambdaMetrics` and enables the feature by
default
2025-05-06 12:49:08 +02:00
Sergi Romeu
a5fa9a2af6
[APM] Remove apmEnableServiceMetrics setting and enable it by default ( #219052 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:apmEnableServiceMetrics` and enables the feature by
default
2025-05-05 18:29:50 +02:00
Lisa Cawley
3dd3975f7b
[DOCS] Fix images and frontmatter in connector docs ( #219892 )
2025-05-05 07:45:27 -07:00
Sergi Romeu
1070ceeea2
[APM] Remove apmAgentExplorerView setting and enable it by default ( #219061 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:apmAgentExplorerView` and enables the feature by default
2025-05-05 16:26:21 +02:00
Sergi Romeu
321436ebfe
[APM] Remove apmServiceInventoryOptimizedSorting setting and enable it by default ( #219058 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:apmServiceInventoryOptimizedSorting` and enables the
feature by default
2025-05-05 16:25:34 +02:00
Sergi Romeu
4bf6522d78
[APM] Remove apmEnableCriticalPath setting and enable it by default ( #219055 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:apmEnableCriticalPath` and enables the feature by default
2025-05-05 16:17:18 +02:00
florent-leborgne
8a05701cc4
[Docs] Replace remaining occurrences of ESS ( #220045 )
...
This PR updates some remaining obsolete variables and mentions of
ESS/Elasticsearch Service that should now refer to Elastic Cloud Hosted.
Note: There are still a few valid references to the Elasticsearch
service, not to be mixed with the cloud offering bearing the same name.
2025-05-05 10:29:30 +00:00
Arianna Laudazzi
0fbb150907
[Reference] Revisit the kibana landing page ( #220025 )
...
This PR updates the Kibana landing page.
Relates to https://github.com/elastic/docs-content/issues/1303
---------
Co-authored-by: Florent Le Borgne <florent.leborgne@elastic.co>
2025-05-05 09:56:31 +00:00
Sergi Romeu
4748d4f1a8
[APM] Set apmProgressiveLoading low by default and remove technical preview ( #219067 )
...
## Summary
Part of #218501
This PR sets the advanced setting `observability:apmProgressiveLoading`
as low by default and removes the technical preview
2025-04-30 13:07:34 +02:00
Sergi Romeu
0e15ae0e55
[Profiling] Remove profilingFetchTopNFunctionsFromStacktraces setting ( #219050 )
...
## Summary
Part of #218501
This PR removes the advanced setting
`observability:profilingFetchTopNFunctionsFromStacktraces`
2025-04-30 11:20:02 +02:00
Michael Wolf
3a8bd29b2e
Osquery: Update exported fields reference for osquery 5.15.0 ( #215619 )
...
Update exported fields reference for osquery 5.15.0.
2025-04-24 19:21:38 +00:00
florent-leborgne
2210960152
[Docs] Fix column offset from migration to md in Audit events page ( #218938 )
...
Some values are not in the right column on this page
https://www.elastic.co/docs/reference/kibana/kibana-audit-events
(basically for all "failure" rows). This PR fixes this
2025-04-23 10:49:28 +00:00
Colleen McGinnis
907cd5904b
[docs] Fix image paths for docs-assembler ( #218344 )
...
Fixes image paths to work with docs-assembler.
Notes for the reviewer:
* I was not able to get images in reference, extend, or release-notes to
work using the `:::{image}` syntax because it seems to resolve
differently than the Markdown `![]()` syntax. We should address this in
docs-builder, but in order to get images working as soon as possible,
I've used Markdown syntax and left us a `TO DO` in a code comment to add
back the `screenshot` class where applicable.
* Can you please add the appropriate labels needed for backporting?
2025-04-15 16:59:57 -05:00
Dima Arnautov
6722f142a4
Support local file path for xpack.productDocBase.artifactRepositoryUrl ( #217046 )
...
## Summary
Closes https://github.com/elastic/kibana/issues/216583
Adds support for a local file path in
`xpack.productDocBase.artifactRepositoryUrl` setting.
If local path with `file://` protocol is provided, it has to contain a
path to a directory with the artifacts and the `index.xml` file.
#### How to test
1. Download the XML and zip files from
https://kibana-knowledge-base-artifacts.elastic.co
2. Create a folder, e.g. `mkdir /Users/<my_user>/test_artifacts` and
place all the files there. The XML file has to be called `index.xml`
3. Add `xpack.productDocBase.artifactRepositoryUrl:
'file:///Users/<my_user>/test_artifacts'` to your `kibana.dev.yml`
4. Go to `/app/management/kibana/observabilityAiAssistantManagement` in
Kibana and install Elastic documentation
5. Kibana dev server should report `[2025-04-07T14:05:10.640+02:00][INFO
][plugins.productDocBase.package-installer] Documentation installation
successful for product [security] and version [8.17]`
6. Check `data/ai-kb-artifacts` folder in your Kibana repo, it should
contain zip files with docs
### 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/src/platform/packages/shared/kbn-i18n/README.md )
- [x]
[Documentation](https://www.elastic.co/guide/en/kibana/master/development-documentation.html )
was added for features that require explanation or tutorials
- [x] [Unit or functional
tests](https://www.elastic.co/guide/en/kibana/master/development-tests.html )
were updated or added to match the most common scenarios
- [x] The PR description includes the appropriate Release Notes section,
and the correct `release_note:*` label is applied per the
[guidelines](https://www.elastic.co/guide/en/kibana/master/contributing.html#kibana-release-notes-process )
2025-04-14 15:27:41 +02:00
Lisa Cawley
388a6fcfbd
[DOCS] Fix path to images in connector docs ( #217920 )
2025-04-10 17:16:06 -07:00
Colleen McGinnis
e60b91a076
[docs] Remove reliance on temporary redirects part 2 ( #216362 )
...
Related to https://github.com/elastic/docs-content/pull/914
Related to https://github.com/elastic/elasticsearch/pull/125663
Removes reliance on temporary redirects in the elasticsearch and
docs-content repos.
2025-03-31 07:43:40 +00:00
Colleen McGinnis
369a43b2c2
[docs] Remove reliance on temporary redirects ( #216315 )
...
Related to https://github.com/elastic/docs-content/pull/914
Removes reliance on temporary redirects in the docs-content repo.
@florent-leborgne can you help me with backport labels? I always get
mixed up across repos.
2025-03-28 10:54:32 -05:00
wajihaparvez
37528a6cb4
[Docs] Remove mention of visualization:colorMapping setting ( #215962 )
...
## Summary
This PR removes the `visualization:colorMapping` setting from the
Advanced settings page.
Rel: https://github.com/elastic/kibana/pull/197802 ,
[#616 ](https://github.com/elastic/platform-docs-team/issues/616 )
---------
Co-authored-by: Nick Partridge <nicholas.partridge@elastic.co>
2025-03-27 18:50:27 +02:00
florent-leborgne
56acc69d59
[Docs] Settings - Specify that search sessions are disabled by default in 9.0 ( #216091 )
...
Updating search session settings docs to indicate that `.enable` is now
set to false by default.
Rel: https://github.com/elastic/kibana/issues/205814
2025-03-27 09:44:06 +01:00
Paulina Shakirova
637c61aedd
Custom link colour option for top banner ( #214241 )
...
This PR resolves [Link color in banner shown in blue and not the defined
color](https://github.com/elastic/kibana/issues/206266 ) issue.
Now there is a new option added that applies custom color specifically
for links, and can be fully customized.
- Updated documentation
- in Cloud
- advanced-settings
- configuration
- Added to plugins
- kibana_usage
- telemetry
- Implemented new 'linkColor' property for the banners
- Updated functional tests
2025-03-25 20:26:35 +01:00
Colleen McGinnis
5e5aff3b5b
[docs] Miscellaneous docs clean up ( #215260 )
...
Miscellaneous docs clean up including:
* [x] Removing unused substitutions
* [x] Moving images per https://github.com/elastic/docs-builder/pull/774
* [x] ~~Clean up redirecting links~~
* [x] ~~Clean up asciidoc-style links~~
2025-03-25 12:57:00 +00:00
