Watchtower: Customizable Verbosity for Slack Notifications

Created on 26 Jul 2018  路  7Comments  路  Source: containrrr/watchtower

It would be great to do a less noisy version of the Slack notifications.

Instead of this:

for container in containers:
   print [stopping|creating]  container ....

It would be great to to summarize this to:

All containers redeployed with latest image

Low Available Enhancement

Most helpful comment

I feel you, but I only have so many hours to put into open source each month.

It鈥檚 up for grabs though so if anyone want to take a stab at it; feel absolutely free. For now, however, I believe my time is better used elsewhere on the project.

馃檹馃徎

All 7 comments

Alternatively, simply bundle the "found new image - stopping - creating - removing" messages into a single message. That would already reduce the "spam" quite significantly, especially when using Mattermost which does not seem to bundle the messages automatially:

screenshot

Ideally allow us to provide a template file (using go template syntax, similar to Alert Manager for Prometheus), to be able to define our own format. That would be extremely useful!

{{ if gt (len .Notifications.Updated) 0 }}
  {{ range .Notifications.Updated }}
    Container {{ .Annotations.container }} was updated with ({{ .Annotations.imageName }}) {{ .Annotations.imageHash }}.
    {{ .Annotations.deletedHash }} has been deleted.
  {{ end }}
{{ end }}
{{ if gt (len .Notifications.Failed) 0 }}
  {{ range .Notifications.Failed }}
    There was a failure: {{ .Annotations.Error }}
  {{ end }}
{{ end }}

And I would totally try to implement it and start a new PR, but my golang knowledge is not sufficient.

Bump up!?
Not a low priority for some of us! 馃槃

Not bugging though :)

I feel you, but I only have so many hours to put into open source each month.

It鈥檚 up for grabs though so if anyone want to take a stab at it; feel absolutely free. For now, however, I believe my time is better used elsewhere on the project.

馃檹馃徎

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Up

Closing this issue in favor of #255 which is aimed towards a more generic (ie. not only for slack) solution.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

7imbrook picture 7imbrook  路  7Comments

MakerTim picture MakerTim  路  6Comments

simskij picture simskij  路  5Comments

meandthedevil picture meandthedevil  路  6Comments

ghost picture ghost  路  4Comments