Skip to content

Consolidate Azure Container Apps instrumentation hub#37778

Open
rohanagarwaldd wants to merge 1 commit into
masterfrom
rohanagarwal/aca-instrumentation
Open

Consolidate Azure Container Apps instrumentation hub#37778
rohanagarwaldd wants to merge 1 commit into
masterfrom
rohanagarwal/aca-instrumentation

Conversation

@rohanagarwaldd

Copy link
Copy Markdown

What does this PR do? What is the motivation?

Consolidates the flow to reach setup guide for Azure Container Apps instrumentation into a single landing page with an interactive method/language picker, updates the overview copy, and adds a "Best for" row to the comparison table. The goal of this change is to remove redundant unnecessary/redundant info and provide users with a faster time-to-instrumentation.

@rohanagarwaldd rohanagarwaldd requested review from a team as code owners June 25, 2026 20:34
@github-actions github-actions Bot added the Architecture Everything related to the Doc backend label Jun 25, 2026
@janine-c janine-c assigned janine-c and unassigned janine-c Jun 25, 2026

@janine-c janine-c left a comment

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.

Hey Rohan, thanks for submitting this! I tested this on the staging links, and it looks like the setup pages all broke. I provided some ideas on next steps below; let me know if you'd like to chat further 🙂

@@ -1,14 +1,6 @@
---
title: In-Container Instrumentation
type: multi-code-lang
external_redirect: /serverless/azure_container_apps/

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.

I noticed that when I click the new "Go to [method] setup for [language]" button, none of the pages render, and this seems to be why. Without the multi-code-lang param and the container-languages shortcode in this and the sidecar index file, the setup docs have nowhere to actually live, and thus don't render. (I also noticed that the links to the in-container and sidecar pages are still in the left nav, which we should remove if we're going to make these pages redirect, but I'm not sure that's what we want to do!)

For next steps, I think we need to figure out where to make this content live, so we can link to it nicely. This could also be a good candidate for Cdocs, which gives us better filtering abilities for situations like this that have multiple options, and the benefit there would be that it wouldn't require designing any new components.

Give it a think, and let us know how we can help. If you have any questions, reach out anytime in #documentation!

@janine-c janine-c removed their assignment Jun 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Architecture Everything related to the Doc backend

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants