Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Answered
Q2 → Slack integration?

Hi all,

I'm looking for a slack integration where Q2 sends notification to a slack channel, instead to my email. I'm seeking to expand team receptivity on my end. a Is there a such thing yet? If not, are there any restrictions on creating one?

Posted 4 years ago
Votes Newest

Answers


What do you mean exactly? Do you mean through the Caliper SDK? If so there is no helpers, but sure you can build something. If you are talking about through the developer portal or community page, that is currently not something that is supported. You would have to make something that takes in your emails and posts it to Slack. While the software we use theoretically could make that possible in the future it is currently not on the roadmap.

Posted 4 years ago
Trey Teter
124 × 2 Administrator
0

Basically, I seek a way to direct notifications to slack, like notifications that goes to our emails currently, like the ones where we would get notifications when someone reply to our tickets for example. I would like slack to have the ability to notify us when our tickets has a new comment, when dev-server status has degraded/offline issue, gitlab CI/CD build failures (when test fails for example.) I think those are good use cases here.

To your suggestion, taking in email and posting it to slack, that seems like a good start here! Thanks for the response!

— Rocky Smith   4 years ago
0

Okay, so the tickets on the Developer Portal, yeah only email is supported at this time. Gitlab seems to be the same. The shared dev server status is a bit different. There is an api that you could potentially hit to get that information, but it doesn't send any notifications externally at this time. Also, that api is currently internal Q2 use only. The main reason that it is internal use only is because we haven't decided on a way to share the documentation on the api, and whether it will stay the same shape it currently is.

— Trey Teter   4 years ago
0

The api is now not an officially supported one, and we reserve the right to change the schema, but we likely won't change the schema in the future. The end point is public now though here: https://q2developer.com/api/v1/admin/status/services

— Trey Teter   4 years ago
0

Excellent, thanks for that api!

— Rocky Smith   4 years ago
78 Views
1 Answer
4 years ago
4 years ago
Tags