Add metric for Probe ID #1491
Closed
Add metric for Probe ID #1491
Conversation
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
Signed-off-by: Tobias Guggenmos <guggenmos@dfn-cert.de>
slrtbtfs
force-pushed
the
log_id_metric
branch
from
25165bb to
8838380
Compare
Author
|
The initial idea for this does not appear to work out. |
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.
What this PR does / Which issue(s) does the PR fix:
When using the
/logsendpoint to retrieve logs associated with an Alert it is currently not possible completely ensure that the logs for the Probe that triggered the Alert are retrieved. This is address by publishing theidused by the/logsendpoint as a metric.Does this PR introduce a user-facing change?
Checklist
release-notessection of PR Desc.