Remove logging during temporary downtime - #181
Merged
Merged
Conversation
During the GKE upgrade of last night we had a short auth credential unavailibity (2.3 seconds, while a gateway pod was being replaced). This was logged by the client as WARN and ERROR, which is completely over the top. This PR changes the logic of the failure logging. It will log on the first connection attempt of the JVM lifetime. It's very unlikely that it's booting right into unavailibility of the Platform side. If it loses connection afterwards, it will log every 10 attempts. So, this is 4 minutes after losing connection, and then every 10 minutes afterwrds. As the Axoniq Platform client is not essential to the application, any remaining log message has been demoted to info, as to not trigger customer's monitoring during outages
CodeDrivenMitch
force-pushed
the
fix/quieter-auth-failure-logging
branch
from
September 22, 2026 12:29
5cd77c0 to
f65b93f
Compare
|
CodeDrivenMitch
requested review from
a team,
Andrew-deVillier and
stefanmirkovic
and removed request for
a team
September 22, 2026 12:34
Collaborator
Author
|
Ported to the AF5 line in #183. |
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
2 participants
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.
During the GKE upgrade of last night we had a short auth credential unavailibity (2.3 seconds, while a gateway pod was being replaced). This was logged by the client as WARN and ERROR, which is completely over the top.
This PR changes the logic of the failure logging. It will log on the first connection attempt of the JVM lifetime. It's very unlikely that it's booting right into unavailibility of the Platform side. If it loses connection afterwards, it will log every 10 attempts. So, this is 4 minutes after losing connection, and then every 10 minutes afterwrds.
As the Axoniq Platform client is not essential to the application, any remaining log message has been demoted to info, as to not trigger customer's monitoring during outages