feat(channels): Log CLI version on startup and dedupe scheduler log#481
Merged
feat(channels): Log CLI version on startup and dedupe scheduler log#481
Conversation
Add a startup log line in `infer channels-manager` that includes the CLI version, commit, and build date so operators can confirm which release is running (e.g. in Kubernetes pod logs). Also drop the duplicate "Scheduler started" log emitted from cmd/channels.go — the scheduler service already logs the same event with richer fields. Closes #470
Contributor
|
🎉 This PR is included in version 0.107.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Starting channels-managerlog line at the top ofinfer channels-managerthat includesversion,commit, andbuild_date(sourced from the existingcmd.version/cmd.commit/cmd.datevars populated via-ldflags -X), so operators can see which release is running in pod/container logs.Scheduler startedlog emitted fromcmd/channels.go— the scheduler service already logs the same event frominternal/services/scheduler/scheduler.gowith richerdir+jobsfields.Closes #470