ChatOps is all about conversation-driven ops. While in a chat channel, team members type commands that some bot is configured to execute through custom scripts. These can wildy vary in functionality as they are highly configurable.
Bringing ops tools into team conversations and using bots to work with key parts of infrastructure allows team to automate tasks and collaborate better, faster, and cheaper.
The next generation of our ChatOps implementation will allow users to have a dedicated interface to configure, invoke, and audit ChatOps actions, doing it in a secure way through RBAC.
We've identified two key aspects that must be included in our offering:
/chatops get cpu <hostname>. We have this today, but we do require you to write the parser and action script yourself.
Interested in joining the conversation for this category? Please join us in our public epic where we discuss this topic and can answer any questions you may have. Your contributions are more than welcome.
Currently, we don't have any plans around improving ChatOps support inside GitLab. We believe the next issue for the community to tackle would be to introduce a pipeline type for chat-ops generated pipelines.
It’s really hard to make “one-size-fits-most” ChatOps when the driving force behind ChatOps is “my business that works in
X way has a need to perform
Y function via chat”, where never between most companies will those variables be the same. No one company has emerged as the leader in this area.
VictorOps is an incident management platform. Through their slack integration they provide common commands to acknowledge and resolve incidents.
Cog provides the ability to build new bot commands in any language allowing users to leverage extensibility and security features.