-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
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
Add Librato integration #648
Add Librato integration #648
Conversation
Automated message from Dropbox CLA bot @VallHer, it looks like you've already signed the Dropbox CLA. Thanks! |
name <code>librato</code>.</p> | ||
|
||
<p>Next, on your <a href="/#settings" target="_blank">Zulip settings | ||
page</a>, create an Librato bot. Please note the bot name and API key. Then:</p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/an/a/ before Librato bot
@VallHer thanks for working on this! I posted a few comments. |
Also, you should squash the two commits together. |
It'd be great if we could get feedback from the Librato folks or someone who has used Librato on the message format -- I pinged the person who opened the original issue to see if he's willing to take a look. The format is relatively verbose compared to how most of our integrations read, but I'm not sure if that's the nature of the Librato service. |
8ed3d2c
to
e1a0aee
Compare
@timabbott I can change it to slack style, should I? |
I think that's mostly reasonable, except that Slack doesn't have topics/threading, and we should move some part of that content into the topic (is "runbook" the machine here? If so maybe "runbook ToHighTemperatureAlert" would be a good thread name?). It might be helpful to have a few more example Librato alerts in the fixtures that we can work with... |
@timabbott I've reviewed screenshot 006 and as far as I'm concerned it looks fine. The only improvement I can think of is adding some color to easily recognise wether an alert is new or resolved. |
Cool. We don't currently have a way to do that variable color thing in Zulip, but it might be a formatting capability worth adding; shouldn't be too hard to do. Certainly I don't think green for new and blue for resolved is the right approach :). @VallHer does this give you the info you need to do a revised version? Also I guess this needs to be rebased across the tests refactoring I merged yesterday. |
f52a8ec
to
5c0807e
Compare
@zack-ahdach
EDIT: |
71d6f15
to
8f296cd
Compare
|
||
@api_key_only_webhook_view | ||
@has_request_variables | ||
def api_librato_webhook(request, user_profile, stream=REQ(default='librato'), topic=REQ(default=None)): |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This line is too long; the topic
argument should be on a second line.
OK will wait for the charts stuff to show up! |
8f296cd
to
aed8095
Compare
Ok I added option to handle charts. We need to wait for guys from librato for better solution. |
f388baa
to
7a0732e
Compare
7a0732e
to
6452b33
Compare
6452b33
to
770f315
Compare
Ok i found how to write service for Librato, however i need also some more time beacuse it is in Ruby and i don't have experience at all. |
What do you mean by "write service for Librato"? Is the idea to do a non-webhook integration? |
Ahh, OK, that makes sense! |
|
||
<p><b>Congratulations! You're done!</b><br /> When a snapshot comes, you'll get a Zulip notification that looks like this:</p> | ||
|
||
<p><img class="screenshot" src="/static/images/integrations/librato/009.png" /></p> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you retake these screenshots showing the stream/topic recipient bar? That's how the screenshots work in our other integrations. While you're doing it, can you give the bot the name "Librato Bot" to match the bot naming style of the other integrations.
Also, you should line wrap the text in a lot of these paragraphs, like we do for the other integrations.
Thanks!
Posted a few comments on the details of the documentation for this. Thanks for building this @VallHer, it's looking really good. |
@VallHer how are you doing on this? If you're too busy to finish this, let me know and perhaps someone else can pick it up. |
@timabbott Or i just can finish integration without snapshot. However it will be better if someone can help me here. |
@VallHer if we just finished and merged the Librato integration without snapshot support, would the work done need to be thrown away to add snapshot support, or would it be a more incremental extension? If the extension would be incremental, I'd recommend we finish and merging without snapshot support, and adding snapshot support can be a future project. Otherwise, @TomaszKolek do you know Ruby / are you interested in learning it to help with this? |
@timabbott |
@timabbott
@VallHer please confirm my conclusions. Or not If I'm talking nonsense. |
@TomaszKolek I will be glad if you can do it instead of me. I actually lost 'connection' with project and forgot basic things. |
@TomaszKolek that's reasonable to me; I think we should go ahead and merge a webhook integration. Then if we find time to add a Librato service, we can have that service use a similar format to the existing webhook integration for sending data over, to reuse the existing code. |
Closing this since development is proceeding on #1749. |
Add Librato integration
#68