Skip to content

Commit 660e736

Browse files
Merge branch 'main' into adding-dbvisualizer
2 parents da5c907 + 4095822 commit 660e736

File tree

386 files changed

+4675
-10690
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

386 files changed

+4675
-10690
lines changed

.github/CODEOWNERS

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,19 +9,19 @@
99
# The docs
1010
/cloud-account/ @elastic/admin-docs
1111
/deploy-manage/ @elastic/admin-docs
12-
/explore-analyze/ @elastic/core-docs @elastic/experience-docs
12+
/explore-analyze/ @elastic/core-docs @elastic/experience-docs
1313
/extend/ @elastic/core-docs
1414
/get-started/ @elastic/core-docs @elastic/project-docs
1515

1616
/manage-data/ @elastic/admin-docs
17-
/manage-data/data-store/ @elastic/admin-docs @elastic/developer-docs
17+
/manage-data/data-store/ @elastic/admin-docs @elastic/developer-docs
1818
/manage-data/ingest/ @elastic/ingest-docs
1919

2020
/reference/ @elastic/docs
2121
/reference/apm-agents/ @elastic/ingest-docs
2222
/reference/data-analysis/ @elastic/docs
2323
/reference/data-analysis/observability/ @elastic/experience-docs
24-
/reference/data-analysis/kibana/ @elastic/experience-docs
24+
/reference/data-analysis/kibana/ @elastic/experience-docs
2525
/reference/data-analysis/machine-learning/ @elastic/developer-docs
2626
/reference/data-analysis/observability/ @elastic/experience-docs
2727
/reference/elasticsearch/clients/ @elastic/developer-docs
@@ -42,8 +42,12 @@
4242
/release-notes/fleet-elastic-agent/ @elastic/ingest-docs
4343
/release-notes/intro/ @elastic/docs
4444

45-
/solutions/ @elastic/experience-docs @elastic/developer-docs
45+
/solutions/ @elastic/experience-docs @elastic/developer-docs
4646
/solutions/observability/ @elastic/experience-docs
47+
/solutions/observability/apm/apm-agents/ @elastic/ingest-docs
48+
/solutions/observability/apm/apm-server/ @elastic/ingest-docs
49+
/solutions/observability/apm/ingest/ @elastic/ingest-docs
50+
/solutions/observability/apm/opentelemetry/ @elastic/ingest-docs
4751
/solutions/observability/get-started/ @elastic/ski-docs @elastic/project-docs
4852
/solutions/search/ @elastic/developer-docs
4953
/solutions/search/get-started/ @elastic/developer-docs @elastic/project-docs
@@ -54,7 +58,7 @@
5458
/troubleshoot/deployments/ @elastic/admin-docs
5559
/troubleshoot/elasticsearch/ @elastic/admin-docs
5660
/troubleshoot/ingest/ @elastic/ingest-docs
57-
/troubleshoot/kibana/ @elastic/admin-docs @elastic/experience-docs
61+
/troubleshoot/kibana/ @elastic/admin-docs @elastic/experience-docs
5862
/troubleshoot/monitoring/ @elastic/admin-docs @elastic/experience-docs
5963
/troubleshoot/observability/ @elastic/ski-docs
6064
/troubleshoot/security/ @elastic/ski-docs

.github/workflows/co-docs-builder.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -21,7 +21,7 @@ on:
2121
jobs:
2222
publish:
2323
if: contains(github.event.pull_request.labels.*.name, 'ci:doc-build')
24-
uses: elastic/workflows/.github/workflows/docs-versioned-publish.yml@main
24+
uses: elastic/dev-docs-workflows/.github/workflows/docs-versioned-publish.yml@main
2525
with:
2626
# Refers to Vercel project
2727
project-name: elastic-dot-co-docs-preview-docs
Lines changed: 74 additions & 33 deletions
Original file line numberDiff line numberDiff line change
@@ -1,65 +1,106 @@
1-
name: Update Kube-Stack Version
1+
name: Update Kube Stack Version
22

33
on:
44
schedule:
55
# Run every Monday at 9:00 AM UTC
66
- cron: '0 9 * * 1'
7-
workflow_dispatch: # Allow manual triggering
7+
workflow_dispatch:
8+
inputs:
9+
dry_run:
10+
description: 'Dry run (check for updates without creating PR)'
11+
required: false
12+
default: false
13+
type: boolean
814

915
jobs:
1016
update-kube-stack-version:
1117
runs-on: ubuntu-latest
1218

1319
steps:
1420
- name: Checkout repository
15-
uses: actions/checkout@v4
21+
uses: actions/checkout@v5
1622
with:
1723
token: ${{ secrets.GITHUB_TOKEN }}
18-
24+
fetch-depth: 0
25+
1926
- name: Set up Python
20-
uses: actions/setup-python@v4
27+
uses: actions/setup-python@v5
2128
with:
22-
python-version: '3.9'
23-
24-
- name: Run kube-stack version update script
29+
python-version: '3.13'
30+
31+
- name: Install dependencies
2532
run: |
26-
cd scripts
27-
python update_kube_stack_version.py
28-
33+
python -m pip install --upgrade pip
34+
pip install requests
35+
36+
- name: Run update script
37+
id: update-script
38+
run: |
39+
echo "Running kube-stack-version update script..."
40+
python scripts/update_kube_stack_version.py
41+
echo "Script completed successfully"
42+
2943
- name: Check for changes
30-
id: verify-changed-files
44+
id: check-changes
3145
run: |
32-
if [ -n "$(git status --porcelain)" ]; then
33-
echo "changed=true" >> $GITHUB_OUTPUT
46+
if git diff --quiet HEAD -- docset.yml; then
47+
echo "No changes detected in docset.yml"
48+
echo "has_changes=false" >> $GITHUB_OUTPUT
3449
else
35-
echo "changed=false" >> $GITHUB_OUTPUT
50+
echo "Changes detected in docset.yml"
51+
echo "has_changes=true" >> $GITHUB_OUTPUT
52+
53+
# Show the diff for logging
54+
echo "Changes:"
55+
git diff HEAD -- docset.yml
3656
fi
37-
38-
- name: Commit and push changes
39-
if: steps.verify-changed-files.outputs.changed == 'true'
40-
run: |
41-
git config --local user.email "[email protected]"
42-
git config --local user.name "GitHub Action"
43-
git add docs/docset.yml
44-
git commit -m "chore: update kube-stack version [skip ci]"
45-
git push
46-
57+
4758
- name: Create Pull Request
48-
if: steps.verify-changed-files.outputs.changed == 'true'
49-
uses: peter-evans/create-pull-request@v5
59+
if: steps.check-changes.outputs.has_changes == 'true' && github.event.inputs.dry_run != 'true'
60+
uses: peter-evans/create-pull-request@v7
5061
with:
5162
token: ${{ secrets.GITHUB_TOKEN }}
52-
commit-message: "chore: update kube-stack version"
53-
title: "chore: update kube-stack version"
63+
commit-message: 'chore: update kube-stack-version'
64+
title: 'chore: update kube-stack-version'
5465
body: |
55-
This PR automatically updates the kube-stack version in `docs/docset.yml` based on the latest version from the elastic-agent repository.
66+
This PR automatically updates the `kube-stack-version` in `docset.yml` based on the latest version from the elastic-agent repository.
5667
5768
**Changes:**
58-
- Updated kube-stack version in docset.yml
69+
- Updated `kube-stack-version` to the latest value from elastic-agent repository
70+
71+
**Generated by:** [Update Kube Stack Version workflow](https://github.com/${{ github.repository }}/actions/workflows/update-kube-stack-version.yml)
5972
60-
This PR was created automatically by the weekly kube-stack version update workflow.
73+
This is an automated update. Please review the changes before merging.
6174
branch: update-kube-stack-version
6275
delete-branch: true
6376
labels: |
6477
automated
65-
documentation
78+
chore
79+
kube-stack-version
80+
81+
- name: Dry run summary
82+
if: github.event.inputs.dry_run == 'true'
83+
run: |
84+
echo "## Dry Run Summary" >> $GITHUB_STEP_SUMMARY
85+
echo "" >> $GITHUB_STEP_SUMMARY
86+
if [ "${{ steps.check-changes.outputs.has_changes }}" == "true" ]; then
87+
echo "✅ **Changes detected** - A PR would be created in a real run" >> $GITHUB_STEP_SUMMARY
88+
echo "" >> $GITHUB_STEP_SUMMARY
89+
echo "**Changes that would be made:**" >> $GITHUB_STEP_SUMMARY
90+
echo '```diff' >> $GITHUB_STEP_SUMMARY
91+
git diff HEAD -- docset.yml >> $GITHUB_STEP_SUMMARY
92+
echo '```' >> $GITHUB_STEP_SUMMARY
93+
else
94+
echo "ℹ️ **No changes needed** - kube-stack-version is already up to date" >> $GITHUB_STEP_SUMMARY
95+
fi
96+
97+
- name: Summary
98+
if: github.event.inputs.dry_run != 'true'
99+
run: |
100+
echo "## Update Summary" >> $GITHUB_STEP_SUMMARY
101+
echo "" >> $GITHUB_STEP_SUMMARY
102+
if [ "${{ steps.check-changes.outputs.has_changes }}" == "true" ]; then
103+
echo "✅ **PR Created** - Changes detected and pull request created" >> $GITHUB_STEP_SUMMARY
104+
else
105+
echo "ℹ️ **No changes needed** - kube-stack-version is already up to date" >> $GITHUB_STEP_SUMMARY
106+
fi
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,3 @@
11
This path is not supported. Currently, we only support using Cloud Connect to connect ECE, ECK, and self-managed clusters to AutoOps.
22

3-
For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md) from the deployment overview page.
3+
For {{ech}} clusters, AutoOps is set up and enabled automatically in all supported [regions](/deploy-manage/monitor/autoops/ec-autoops-regions.md), and can be [accessed](/deploy-manage/monitor/autoops/ec-autoops-how-to-access.md#ec-autoops-how-to-access) from the deployment overview page.
Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1 @@
1-
Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions).
1+
Using [AutoOps for ECE, ECK, and self-managed clusters](/deploy-manage/monitor/autoops/cc-autoops-as-cloud-connected.md) through Cloud Connect is included with your [self-managed Enterprise license](https://www.elastic.co/subscriptions) and self-managed free trials.

deploy-manage/cloud-connect.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -23,11 +23,11 @@ Learn how to set up and use [](/deploy-manage/monitor/autoops/cc-autoops-as-clou
2323

2424
Find answers to your questions about Cloud Connect.
2525

26-
* [Does using Cloud Connect require additional payment?](#cc-additional-payment)
26+
* [Does Cloud Connect require additional payment?](#cc-additional-payment)
2727
* [Can I use Cloud Connect to connect my Elastic Cloud Hosted clusters to AutoOps?](#cc-ech)
2828
* [Are more services going to be available with Cloud Connect?](#cc-more-services)
2929

30-
$$$cc-additional-payment$$$ **Does using Cloud Connect require additional payment?**
30+
$$$cc-additional-payment$$$ **Does Cloud Connect require additional payment?**
3131
: Each cloud connected service has its own licensing and payment requirements.
3232
:::{include} /deploy-manage/_snippets/autoops-cc-payment-faq.md
3333
:::

deploy-manage/cloud-organization/billing/billing-faq.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,6 +3,9 @@ mapped_pages:
33
- https://www.elastic.co/guide/en/cloud/current/ec-faq-billing.html
44
applies_to:
55
deployment:
6+
self:
7+
ece:
8+
eck:
69
ess: all
710
serverless: all
811
products:
@@ -29,6 +32,7 @@ This frequently-asked-questions list answers some of your more common questions
2932
* [How can I delete my {{ecloud}} account?](#faq-deleteaccount)
3033
* [Can I get a refund?](#faq-refund)
3134
* [What is included in my paid {{ecloud}} deployment?](#faq-included)
35+
* [Does Cloud Connect require additional payment?](#billing-cc-additional-payment)
3236
* [What are the data transfer and storage charges and how can I control them?](#faq-dts)
3337
* [What taxes will be applied on my invoice?](#faq-taxes)
3438

@@ -94,6 +98,9 @@ $$$faq-deleteaccount$$$How can I delete my {{ecloud}} account?
9498
$$$faq-refund$$$Can I get a refund?
9599
: Charges are non-refundable, but once you delete a deployment we’ll stop charging you for that deployment immediately. You only pay for what you use and you can stop using the service at any time. For any special considerations warranting a potential refund, use the {{ecloud}} Console [Support form](https://cloud.elastic.co/support?page=docs&placement=docs-body) to open a support case and select *Billing issue* as the category. To ensure quick processing, be sure to provide detail about the reasons for the refund request as well as other matters pertaining to the issue. For other ways to open a Support case, check [Contact us](../../../troubleshoot/index.md).
96100

101+
$$$billing-cc-additional-payment$$$ **Does Cloud Connect require additional payment?**
102+
: Each cloud connected service has its own licensing and payment requirements. For more information, refer to the [Elastic self-managed subscriptions](https://www.elastic.co/subscriptions) page.
103+
97104
$$$faq-included$$$What is included in my paid {{ech}} deployment?
98105
: All subscription tiers for {{ech}} include the following free allowance:
99106

deploy-manage/cloud-organization/billing/cloud-hosted-deployment-billing-dimensions.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -78,7 +78,7 @@ As is common with Cloud providers, we meter and bill snapshot storage using two
7878

7979
This is calculated by metering the storage space (GBs) occupied by all snapshots of all deployments tied to an account. The same unit price applies to all regions. To calculate the due charges, we meter the amount of storage on an hourly basis and produce an average size (in GB) for a given month. The average amount is then used to bill the account for the GB/month used within a billing cycle (a calendar month).
8080

81-
For example, if the storage used in April 2019 was 100GB for 10 days, and then 130GB for the remaining 20 days of the month, the average storage would be 120 GB/month, calculated as (100*10 + 130*20)/30.
81+
For example, if the storage used in April 2019 was 100GB for 10 days, and then 130GB for the remaining 20 days of the month, the average storage would be 120 GB/month, calculated as `(100*10 + 130*20)/30`.
8282

8383
We provide a free allowance of 100 GB/month to all accounts across all the account deployments. Any metered storage usage below that amount will not be billed. Whenever the 100 GB/month threshold is crossed, we bill for the storage used in excess of the 100GB/month free allowance.
8484

deploy-manage/cloud-organization/billing/elastic-observability-billing-dimensions.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -26,8 +26,8 @@ Refer to [Serverless billing dimensions](serverless-project-billing-dimensions.m
2626

2727
## Synthetics [synthetics-billing]
2828

29-
[Synthetic monitoring](/solutions/observability/synthetics/index.md) is an optional add-on to Observability Serverless projects that allows you to periodically check the status of your services and applications as a part of your "Complete" tier subscription. In addition to the core ingest and retention dimensions, there is a charge to execute synthetic monitors on our testing infrastructure. Browser (journey) based tests are charged per-test-run, and ping (lightweight) tests have an all-you-can-use model per location used.
29+
[Synthetic monitoring](/solutions/observability/synthetics/index.md) is an optional add-on to Observability Serverless projects that allows you to periodically check the status of your services and applications as a part of the "Observability Complete" feature tier. In addition to the core ingest and retention dimensions, there is a charge to execute synthetic monitors on our testing infrastructure. Browser (journey) based tests are charged per-test-run, and ping (lightweight) tests have an all-you-can-use model per location used.
3030

3131
## Elastic Managed LLM
3232

33-
The default [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) enables you to leverage AI-powered search as a service without deploying a model in your serverless project. It's configured by default to use with the Security AI Assistant, Attack Discovery, and other applicable AI features as a part of your "Complete" tier subscription. Using the default LLM will use tokens and incur related token-based add-on billing for your serverless project.
33+
The default [Elastic Managed LLM](kibana://reference/connectors-kibana/elastic-managed-llm.md) enables you to leverage AI-powered search as a service without deploying a model in your serverless project. It's configured by default to use with the Security AI Assistant, Attack Discovery, and other applicable AI features as a part of the "Observability Complete" feature tier. Using the default LLM will use tokens and incur related token-based add-on billing for your serverless project.

deploy-manage/cloud-organization/billing/manage-subscription.md

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -72,6 +72,9 @@ You can [change your subscription level](/deploy-manage/cloud-organization/billi
7272
`Field-level or document-level security`
7373
: Remove any user role configurations based on field or document access [through the API](/deploy-manage/users-roles/cluster-or-deployment-auth/controlling-access-at-document-field-level.md) or the {{kib}} [Roles](/deploy-manage/users-roles/cluster-or-deployment-auth/defining-roles.md) page.
7474

75+
`ES|QL cross-cluster search`
76+
: Discontinue all [ES|QL CCS queries](elasticsearch://reference/query-languages/esql/esql-cross-clusters.md) or upgrade license tier to Enterprise.
77+
7578
::::{note}
7679
After you have made your changes to the deployment, it can take up to one hour to clear the notification banner.
7780
::::

0 commit comments

Comments
 (0)