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 #4517) [apm] Update Applications nav subsection from "Services" to "Service inventory" #4520

Merged
merged 2 commits into from
Nov 8, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 8, 2024

Description

Update the Applications nav subsection from Services to Service Inventory. Note: The page title appears to still be Services so I only updated references to the nav.

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 #4447

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 #4517 done by [Mergify](https://mergify.com).

…inventory" (#4517)

* update references to services item in serverless side bar

* update references to services item in stateful side bar

* scale back serverless updates

(cherry picked from commit a24b240)

# Conflicts:
#	docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc
#	docs/en/serverless/apm/apm-get-started.asciidoc
#	docs/en/serverless/apm/apm-ui-services.asciidoc
@mergify mergify bot added backport conflicts There is a conflict in the backported pull request labels Nov 8, 2024
@mergify mergify bot requested a review from a team as a code owner November 8, 2024 21:11
Copy link
Contributor Author

mergify bot commented Nov 8, 2024

Cherry-pick of a24b240 has failed:

On branch mergify/bp/8.16/pr-4517
Your branch is up to date with 'origin/8.16'.

You are currently cherry-picking commit a24b240a.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   docs/en/observability/apm/view-and-analyze/ui-overview/services.asciidoc
	modified:   docs/en/observability/monitor-k8s/monitor-k8s-application-performance.asciidoc

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   docs/en/serverless/apm/apm-find-transaction-latency-and-failure-correlations.asciidoc
	deleted by us:   docs/en/serverless/apm/apm-get-started.asciidoc
	deleted by us:   docs/en/serverless/apm/apm-ui-services.asciidoc

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

Copy link
Contributor

github-actions bot commented Nov 8, 2024

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 merged commit 466a4f4 into 8.16 Nov 8, 2024
3 checks passed
@colleenmcginnis colleenmcginnis deleted the mergify/bp/8.16/pr-4517 branch November 8, 2024 21:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport conflicts There is a conflict in the backported pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant