StatHat can send alert notifications to any Keybase team chat channels.
Since team chat on Keybase is end-to-end encrypted, we can't just post a message to some API endpoint like we do for Slack and PagerDuty. You need to add our bot user to your team.
We created a Keybase user named
stathatbot. You should check it out
to make sure it is legit by doing:
keybase id stathatbot
It should have valid proofs for
@stathat on twitter, DNS for
and DNS for
numerotron.com. Given those proofs, you can be confident that
stathatbot belongs to us here at StatHat. You can follow
to keep track of its proofs.
Now you need to add
stathatbot to one of your teams. Please note that
once on the team,
stathatbot will be able to read (and write) messages
to all the channels on the team.
The best way to protect your data is
to use a subteam that is just for alerts or bots. If
just a member of a subteam, it can only access chat channels in that subteam,
and not the root team or any other subteams.
So, let's say your team on keybase is
treehouse, you would do:
keybase team create treehouse.alerts
to create the subteam. And then
keybase team add-member treehouse.alerts --user=stathatbot --role=reader
The reader role is a little confusing, but it means that it will only
have read access to any files you happen to put in
It can still read and write to any chat channel in
(For the record, the
stathatbot doesn't even have file system access turned
on, but you should still give bots as little access as necessary.)
Now, you're all set. In StatHat alert destinations settings, there's a new
section for Keybase. You would enter
treehouse.alerts for the team name
and you can leave the channel blank to use the default
Then enable this Keybase destination for manual and automatic alerts on the Settings page, and now all alert notifications will be sent to your Keybase team's chat channel.