Include numeric values from falco payloads in alertmanager alerts #177
Conversation
This file contains 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
|
Welcome @alsm! It looks like this is your first PR to falcosecurity/falcosidekick 🎉 |
Use the json UseNumber() option to not decode numbers as float64 then when creating the am payload can just call .String on the json.Number this means that ints don't get unnecessary precision and floats aren't cut off short. resolves falcosecurity#176 Signed-off-by: Al Stockdill-Mander <asm@uk.ibm.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: Issif The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
LGTM label has been added. Git tree hash: 5e4a895d25db4a1b18be628e3b6b2e6bc4139b65
|
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.
Use the json UseNumber() option to not decode numbers as float64 then
when creating the am payload can just call .String on the json.Number
this means that ints don't get unnecessary precision and floats
aren't cut off short.
resolves #176
/kind feature
/area outputs