[Push monitor] Fix: Prometheus update with incorrect value#6436
Merged
[Push monitor] Fix: Prometheus update with incorrect value#6436
Conversation
…catch to avoid break the monitor in the future.
louislam
commented
Nov 28, 2025
|
|
||
| this.prometheus = new Prometheus(this, await this.getTags()); | ||
| try { | ||
| this.prometheus = new Prometheus(this, await this.getTags()); |
Owner
Author
There was a problem hiding this comment.
It is safe to not initialized.
I have checked all calls, they have syntax like this: this.prometheus?.update(null, tlsInfo);
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
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
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.
Close: #6430
I think it is not the first time, monitors are broken by Prometheus. Let's try-catch to avoid it in the future.