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

[Monitoring] Fixing fatal exception where BOT_NAME env var was not set in k8s #4273

Merged
merged 1 commit into from
Sep 25, 2024

Conversation

vitorguidi
Copy link
Collaborator

@vitorguidi vitorguidi commented Sep 25, 2024

This PR fixes this error:

image

BOT_NAME is not set for k8s jobs

Part of #4271

@vitorguidi vitorguidi merged commit 3a9caf8 into master Sep 25, 2024
6 of 7 checks passed
@vitorguidi vitorguidi deleted the fix/bot-name-exception branch September 25, 2024 18:54
Copy link
Collaborator

@jonathanmetzman jonathanmetzman left a comment

Choose a reason for hiding this comment

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

LGTM

@vitorguidi vitorguidi changed the title Fixing fatal exception where BOT_NAME env var was not set in k8s [Monitoring] Instrumenting cronjob exit codesFixing fatal exception where BOT_NAME env var was not set in k8s Nov 8, 2024
@vitorguidi vitorguidi changed the title [Monitoring] Instrumenting cronjob exit codesFixing fatal exception where BOT_NAME env var was not set in k8s [Monitoring] Fixing fatal exception where BOT_NAME env var was not set in k8s Nov 8, 2024
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.

2 participants