You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we send alerts to the notification channel before they are inserted into the database this means the ID of the Alert and Decision are always 0 as they are INT this is the default value. So if you include the ID in the notification template you will always see 0 and not the actual incremented ID from the database insertion.
If we do it after the database call, we do loose speed with the notification, however, user can actually use the ID property correctly and can easily inspect or dig into the alert without having to run cscli alerts list and find the one that is the one sent by the notification.
The text was updated successfully, but these errors were encountered:
Check Releases to make sure your agent is on the latest version.
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
@LaurenceJJones: There are no 'kind' label on this issue. You need a 'kind' label to start the triage process.
/kind feature
/kind enhancement
/kind refactoring
/kind bug
/kind packaging
Details
I am a bot created to help the crowdsecurity developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the BirthdayResearch/oss-governance-bot repository.
Currently we send alerts to the notification channel before they are inserted into the database this means the ID of the Alert and Decision are always
0
as they are INT this is the default value. So if you include the ID in the notification template you will always see0
and not the actual incremented ID from the database insertion.If we do it after the database call, we do loose speed with the notification, however, user can actually use the ID property correctly and can easily inspect or dig into the alert without having to run
cscli alerts list
and find the one that is the one sent by the notification.The text was updated successfully, but these errors were encountered: