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
This concerns notifications around rollout lifecycle.
These messages are very noisy and dont feel like errors. they should be info (maybe warning?)
example message: time="2024-03-21T18:29:30Z" level=error msg="Failed to run trigger, trigger: on-scaling-replica-set, destination: {slack argo-rollouts-notifications}, namespace config: : trigger 'on-scaling-replica-set' is not configured"
even better would be fire once the first time and never again.
i want to do this work but first wanted to check if there is reason these are error level messages.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered:
meeech
changed the title
Downgrade log messages for "...trigger '<EVENT>' is not configured"
Downgrade log level for messages around notifs for rollout lifecycle "...trigger '<EVENT>' is not configured"
Mar 21, 2024
Summary
This concerns notifications around rollout lifecycle.
These messages are very noisy and dont feel like errors. they should be info (maybe warning?)
example message:
time="2024-03-21T18:29:30Z" level=error msg="Failed to run trigger, trigger: on-scaling-replica-set, destination: {slack argo-rollouts-notifications}, namespace config: : trigger 'on-scaling-replica-set' is not configured"
even better would be fire once the first time and never again.
i want to do this work but first wanted to check if there is reason these are error level messages.
Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritize the issues with the most 👍.
The text was updated successfully, but these errors were encountered: