-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release 0.2.0 #15
Comments
Circling back now. From what I can see, the only thing outstanding/desired is #17 ( |
It looks like this has been open for awhile. Is there any update on this? Notification for services recovering would be huge. |
Hello! Thanks for your feedback, I'll try to make this possible during next
week
…On Fri, 28 Jul 2017 at 23:17, Josh Reichardt ***@***.***> wrote:
It looks like this has been open for awhile. Is there any update on this?
Notification for services recovering would be huge.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7ZWqjbbNAV62GwP_01nCd45Lo-VufEks5sSkHZgaJpZM4JkBHK>
.
|
@ndelitski Awesome, thanks for the update. |
@jmreicha Hello just pushed new version with a recover state notification, please check if it works as expected and then we release it. Docker image version is |
btw recover notifications feature is enabled by default, do we even need it to be an optional? |
@ndelitski Awesome, I will try to test it out this week. I don't really have a use case for turning off the recovery feature. Thanks again! |
The recovery notification is working. The only other thing I'd like to see is red for degraded and green when recovered for Slack messages. I can do a separate PR or just work with the templates for that unless you want to make that default behavior. |
Woops. There is already an issue for the colors #24. |
Ok from what I've read we need to hardcode message color depending on
notification type, sounds easy to implement. I'll do it soon 😉
…On Wed, 16 Aug 2017 at 21:34, Josh Reichardt ***@***.***> wrote:
I see there is already an issue for the colors #24
<#24>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#15 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AC7ZWpJPohKyu1yztHPbKhi2bUyMx2dkks5sYzY7gaJpZM4JkBHK>
.
|
Todo
#{service.id}
Is there anything i have missed @flaccid?
The text was updated successfully, but these errors were encountered: