Join us for three lightning talks around how to get the most out of the Slack Platform:
1) "JavaScript broke my heart, but TypeScript made me fall in love again" by Andrew @Halp
2) "How Slack uses Slack at Slack" by Dustin @SlackHQ
3) "Building devops tooling with Slack" by Dan @Transposit
34. 3 simple things
How Slack uses Slack
Channel naming
conventions
Help people find the
information they’re looking for
easily.
Emojis have meaning
Emojis are fun. They also can
communicate concrete
meaning instantly.
Open by default
Questions that get answered
in public are answered for all.
42. 3 simple things
How Slack uses Slack
Channel naming
conventions
Help people find the
information they’re looking for
easily.
Emojis have meaning
Emojis are fun. They also can
communicate concrete
meaning instantly.
Open by default
Questions that get answered
in public are answered for all.
43. Emojis with
meaning
We use emojis to kickoff
automated
processes/workflows as
well as to communicate
very specific meaning.
We also use them for fun
all the time.
Matt Russo
Where do we get water from?
11:02 PM
DiógenesBrito
I’ve got a plan for Q4 planning in
4:59 PM
2 replies Last reply just now
How Slack uses Slack
Peter Tielking
Can I get GitHub added to my Okta?
3:02 PM
2 replies Last reply just now
Liz Lally
Did we fix the backend timing issue?
10:02 AM
44. 3 simple things
How Slack uses Slack
Channel naming
conventions
Help people find the
information they’re looking for
easily.
Emojis have meaning
Emojis are fun. They also can
communicate concrete
meaning instantly.
Open by default
Questions that get answered
in public are answered for all.
Team Escal. Channels
Alerts
Staffed
Priority
SLA’s (screenshot of SLA escal.)
For every feature, pinned items, purpose
We make interactive runbooks which learn.
Save questions for after the talk, due to the “lightning” nature of it.
Not going to cover:
Building a slack app
Oauth
UX intricacies
What is devops? It’s tools designed to enable development and operations of your applications. CI/CD pipelines, alerting, monitoring, incident management.
What makes sense to “tie in” to slack?
Frequency of use
Accessible (make a command available for someone who might not be able to run it on their own)
Intricate
Human decision making needed
SOP vs incident
“People are already there”. Everybody is in chat (as opposed to jenkins or other tools)
Across the org
Helpful for future you
Can be included in
All about making you more efficient and effective.
So how can devops tools and chat work together
Easiest: just have adhoc meetings in slack.
Easier: bring all your relevant events (releases, incidents, service provider statuses) and discussions about those into slack. Aka the “firehose” pattern.
Don’t push too much to slack (nginx logfiles in their entiriety) because of the 1 post/second limit.
You can also build specific commands that integrate with devops tooling.
Trigger a jenkins build. Show me the last 10 deployments for service X. Add this ip to my firewall and drop all the packets.
You need to think about inputs. These include plain text, structured data from slack’s form controls (dates, select list) and emojis.
Then ad your business logic (authorization, any specific business rules).
Finally, connect to your other systems via webhook, API or SDK calls.
Example of a slack app I built which lists my ec2 instances.
Demo of list of ec2-instances and restart of ec2-instances in my test slack.
Read this
Or google for it.
How can you discover slack commands? Docs, welcome messages, bots that exist in your workspace.
Make sure to avoid escalation of privileges.
Think about when you should drop out of slack. Sometimes you should just go to the tool. How do you capture the actions someone did “out of band”. Firehose will save you.