Skip to content

Diagnostics privacy disclaimer#6229

Merged
stefnestor merged 5 commits intoelastic:mainfrom
stefnestor:stef_diagPrivacy
May 7, 2026
Merged

Diagnostics privacy disclaimer#6229
stefnestor merged 5 commits intoelastic:mainfrom
stefnestor:stef_diagPrivacy

Conversation

@stefnestor
Copy link
Copy Markdown
Member

Summary

👋 howdy, team! Mini PR to cross-pollinate our diagnostic sensitive data & privacy statement disclaimers across the different diagnostic pages. Also took the moment to standardize the diagnostic intro paragraphs a bit (and remove AutoOps disclaimers from platform-level which it does not monitor, only ES).

Generative AI disclosure

  1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?
  • Yes
  • No

@stefnestor stefnestor requested review from a team as code owners May 2, 2026 17:43
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented May 2, 2026

Vale Linting Results

Summary: 1 warning, 6 suggestions found

⚠️ Warnings (1)
File Line Rule Message
troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md 60 Elastic.MenuArrows Use '→' to separate menu items, not '' or '='. Example: Select Manage index → Add lifecycle policy.
💡 Suggestions (6)
File Line Rule Message
troubleshoot/deployments/cloud-enterprise/run-ece-diagnostics-tool.md 60 Elastic.WordChoice Consider using 'can, might' instead of 'may', unless the term is in the UI.
troubleshoot/elasticsearch/diagnostic.md 31 Elastic.Versions Use 'or later' instead of 'or higher' when referring to versions.
troubleshoot/index.md 73 Elastic.FirstPerson Use caution when using first-person pronouns such as 'my.'
troubleshoot/ingest/logstash/diagnostic.md 26 Elastic.Versions Use 'or later' instead of 'or higher' when referring to versions.
troubleshoot/kibana/capturing-diagnostics.md 23 Elastic.Repetition "this" is repeated.
troubleshoot/kibana/capturing-diagnostics.md 32 Elastic.Versions Use 'or later' instead of 'or higher' when referring to versions.

The Vale linter checks documentation changes against the Elastic Docs style guide.

To use Vale locally or report issues, refer to Elastic style guide for Vale.

@stefnestor stefnestor enabled auto-merge (squash) May 2, 2026 17:50
Copy link
Copy Markdown
Contributor

@github-actions github-actions Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Docs review summary

Focus areas

  • Style and clarity: Good. The standardized privacy note is consistently worded across all seven files. The updated warning in troubleshoot/index.md is clearer than the original.
  • Jargon: One issue — ECK is used without expansion on first use in the new run-eck-diagnostics.md intro paragraph. See inline comment.
  • Frontmatter and applies_to: troubleshoot/index.md is missing an applies_to block entirely (pre-existing gap, but this PR edits the file). All other changed files have applies_to present.
  • Content type fit: Changes are appropriate for troubleshooting pages. The heading demotion of Working with support from ## to ### (making it a sub-section of Contact us) is structurally sound.
  • Parent issue satisfaction: Not applicable — this is a cross-pollination/cleanup PR with no linked parent issue.

Nits

  • troubleshoot/index.md:107 — Double space before Any uploads (see inline comment).

Notes

  • Vale is not installed in this environment; style review was performed manually using the Elastic style guide rules.
  • troubleshoot/index.md frontmatter lacks applies_to entirely. Since the PR touches this file, consider adding applies_to (for example stack: ga / serverless: ga, or the relevant deployment keys) to bring it into compliance with the mandatory frontmatter requirement.

Generated by Docs review agent for issue #6229 · ● 455.7K

Comment thread troubleshoot/index.md Outdated

:::{warning}
Diagnostics and logs mainly emit product metadata and settings, but they may expose sensitive data which needs to be redacted before being shared outside of your organization. Refer to each product's diagnostics page for information on sanitizing output.
Diagnostics and logs mainly emit product metadata and settings. They are privacy-redacted as much as possible, but may still contain sensitive data which needs to be redacted before being shared outside of your organization. We therefore recommend against uploading these outputs to public forums. Any uploads to the [Elastic Support Portal](https://support.elastic.co) are treated according to the [Elastic Privacy Statement](https://www.elastic.co/legal/privacy-statement). Refer to each product's diagnostics page for information on sanitizing output.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Double space introduced in this edit. There are two spaces between public forums. and Any uploads — remove the extra space.

:::

`eck-diagnostics` is a stand-alone command line tool to create a diagnostic archive to help troubleshoot issues with ECK.
ECK diagnostics is a stand-alone command line tool that you can run on hosts where the ECK operator is installed. It collects logs and metrics, and stores everything into an archive file that can be provided to [Elastic support](/troubleshoot/index.md#troubleshoot-work-with-support) for troubleshooting and investigation purposes.
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Jargon: ECK not expanded on first use.

The new intro paragraph uses "ECK" twice as a bare abbreviation without spelling it out. Per the jargon guide, spell out on first use in the page body.

Suggested rewrite:

Elastic Cloud on Kubernetes (ECK) diagnostics is a stand-alone command line tool that you can run on hosts where the ECK operator is installed. It collects logs and metrics, and stores everything into an archive file that can be provided to Elastic support for troubleshooting and investigation purposes.

Comment thread troubleshoot/ingest/logstash/diagnostic.md Outdated
Comment thread troubleshoot/deployments/cloud-on-k8s/run-eck-diagnostics.md
Copy link
Copy Markdown
Member

@shainaraskas shainaraskas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

approved after edits

@stefnestor
Copy link
Copy Markdown
Member Author

Cheers, both! 🙇‍♀️

@stefnestor stefnestor merged commit bf8e2cd into elastic:main May 7, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants