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

Init container log not shown in console log stream #1336

Open
1 of 3 tasks
seraph-george opened this issue Nov 1, 2024 · 4 comments
Open
1 of 3 tasks

Init container log not shown in console log stream #1336

seraph-george opened this issue Nov 1, 2024 · 4 comments
Labels
Backlog Issue has been validated and logged in our backlog for future work bug Something isn't working

Comments

@seraph-george
Copy link

Please provide us with the following information:

This issue is a: (mark with an x)

  • bug report -> please search issues before submitting
  • documentation issue or request
  • regression (a behavior that used to work and stopped in a new release)

Issue description

Init container logs not shown on console log stream

Steps to reproduce

Deploy a container app with an init container. Try to view the logs on the console log stream when the init container is running.

Expected behavior [What you expected to happen.]
When the init container is running, the console log stream displays the logs from the init container.

Actual behavior [What actually happened.]
The console log stream displays a Kubernetes error.

Screenshots
When the init container is running, the console log stream displays a Kubernetes error.
Image

Additional context

The init container logs are only visible in the log analytics workspace. We use Datadog for observability and the init container logs aren't being sent to Datadog either, only the main container logs are being sent to Datadog. We're having to enable log analytics workspace for the sole purpose of viewing init container logs.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: triage 🔍 Pending a first pass to read, tag, and assign label Nov 1, 2024
@v-vish
Copy link
Collaborator

v-vish commented Nov 5, 2024

@seraph-george Could you please let us know the region where you're encountering this issue?

@v-vish v-vish added Needs: Author Feedback and removed Needs: triage 🔍 Pending a first pass to read, tag, and assign labels Nov 5, 2024
@seraph-george
Copy link
Author

@seraph-george Could you please let us know the region where you're encountering this issue?

East US. I'm not sure the region matters. I'd created an Azure support ticket and they reproduced it and suggested to raise a Github issue.

@SpecialHias
Copy link

We have the same issue in West-EU. We do not see the logs of the init container in the log stream.

@simonjj simonjj added Backlog Issue has been validated and logged in our backlog for future work bug Something isn't working and removed Needs: Attention 👋 labels Nov 7, 2024
@simonjj
Copy link
Collaborator

simonjj commented Nov 7, 2024

Thank you guys for raising this, we've added this to the backlog of our public roadmap. If you find yourself in the same situation and need this issue fixed please upvote here for us to get prioritization signal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog Issue has been validated and logged in our backlog for future work bug Something isn't working
Projects
Development

No branches or pull requests

4 participants