Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.16](backport #4670) [apm] Clarify how to create/use API keys #4740

Merged
merged 1 commit into from
Jan 3, 2025

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Jan 3, 2025

Description

Fixes inconsistencies in how we talk about API keys for APM Server usage.

Documentation sets edited in this PR

Check all that apply.

  • Stateful (docs/en/observability/*)
  • Serverless (docs/en/serverless/*)
  • Integrations Developer Guide (docs/en/integrations/*)
  • None of the above

Related issue

Closes #4312

Checklist

  • Product/Engineering Review
  • Writer Review

Follow-up tasks

Select one.

  • This PR does not need to be ported to another doc set because:
    • The concepts in this PR only apply to one doc set (serverless or stateful)
    • The PR contains edits to both doc sets (serverless and stateful)
  • This PR needs to be ported to another doc set:
    • Port to stateful docs: <link to PR or tracking issue>
    • Port to serverless docs: <link to PR or tracking issue>

This is an automatic backport of pull request #4670 done by [Mergify](https://mergify.com).

* add information on beats api key

* add section to common problems section of the apm config page

* apply suggestions from code review

Co-authored-by: Edu González de la Herrán <[email protected]>

* fix typp

---------

Co-authored-by: Edu González de la Herrán <[email protected]>
(cherry picked from commit 0fee5c3)
@mergify mergify bot requested a review from a team as a code owner January 3, 2025 16:29
@mergify mergify bot added the backport label Jan 3, 2025
Copy link
Contributor

github-actions bot commented Jan 3, 2025

A documentation preview will be available soon.

Request a new doc build by commenting
  • Rebuild this PR: run docs-build
  • Rebuild this PR and all Elastic docs: run docs-build rebuild

run docs-build is much faster than run docs-build rebuild. A rebuild should only be needed in rare situations.

If your PR continues to fail for an unknown reason, the doc build pipeline may be broken. Elastic employees can check the pipeline status here.

@colleenmcginnis colleenmcginnis enabled auto-merge (squash) January 3, 2025 16:33
@colleenmcginnis colleenmcginnis merged commit 829181c into 8.16 Jan 3, 2025
8 checks passed
@colleenmcginnis colleenmcginnis deleted the mergify/bp/8.16/pr-4670 branch January 3, 2025 16:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant