Kibana: Slack integration

[elasticmachine]

Original comment by @epixa:

This is a stub issue to track the request to have slack integration with Kibana through reporting. It should be edited with more details as they get fleshed out.

From @kimchy:

Thoughts on such integration:

/kibana 24h Dashboard-X
/kibana last week Viz-Y

Some other related links:

Custom unfurls from slack: https://medium.com/slack-developer-blog/all-will-be-revealed-ebcad7c531f0#.3nsciiipe
Grafana slack alerts: http://docs.grafana.org/alerting/notifications/

Rough mockup:

[elasticmachine]

Original comment by @epixa:

/cc @alexfrancoeur @kobelb @Stacey-Gammon @tbragin @jimgoodwin

[elasticmachine]

Original comment by @alexfrancoeur:

Working doc with some additional thoughts on this topic: LINK REDACTED

[elasticmachine]

Original comment by @pickypg:

I didn't read the brainstorm (saw the issue as an email), but I think it would also be very helpful to have a "send to Slack" feature which was simply a way to send the current URL to Slack once we integrate with Slack.

That way users seeing something weird could automatically send the properly constrained URL to Slack.

[alexfrancoeur]

Linking to:
[Reporting] - Export to PNG #18130
[Watcher] Add support for the PNG report generated image_urls in the Slack action https://github.com/elastic/elasticsearch/issues/30387

[pickypg]

https://github.com/elastic/kibana/pull/19236 provides the ability to do this.

[stacey-gammon]

@pickypg - this is actually a bit different. Rather than a "send to slack" feature, this is more about a command a user would issue within slack, like /giffy but instead something like /kibana dashboard-title which would show a png and link to a dashboard.

[pickypg]

@Stacey-Gammon Ah, good point! I was thinking in the reverse direction that we'd have to send the file to Slack, but it's probably an API response.

[alexfrancoeur]

Both are great and valid use cases needed in Kibana. As Stacy mentioned, this issue is meant more to address the ChatOps use case. We can probably update this description to provide a more generic implementation, I'd imagine we'd want this service to be more than just Slack.

[tsullivan]

If this is a ChatOps / alerting / actions issue, then I'm taking off the Reporting label.

Reporting might come into play in some way as a driver for generating the image, but that doesn't seem to be a main point of this issue

[elasticmachine]

Pinging @elastic/kibana-core-ui (Team:Core UI)

[timroes]

Chat Ops is part of core UI, so relabelleing.