Comment on page
Four extension kits exist through which Steadybit's capabilities can be extended. Unless you are thinking about authoring a custom extension, you probably do not need to know about these kits.
ActionKit logo depicting the text action kit and a crosshair icon
The Steadybit ActionKit enables the extension of Steadybit with new action capabilities that you can use within experiments. For example, ActionKit can be used to author open/closed source:
- attacks to attack AWS, Azure, and Google Cloud services that Steadybit cannot natively attack,
- integrate load testing tools,
- health and state checks and
- every other runnable action!
DiscoveryKit logo depicting the text discovery kit and a radar dish icon
The Steadybit DiscoveryKit enables the extension of Steadybit with new discovery capabilities. For example, DiscoveryKit can be used to author open/closed source discoveries for:
- proprietary technology,
- non-natively supported open-source tech,
- hardware components and
- every other "thing" you would want to see and attack with Steadybit.
EventKit logo depicting the text event kit and a bell icon
EventKit allows extensions to consume events from the Steadybit platform to integrate with third-party systems. Extensions leveraging EventKit are similar to webhooks but do not face the typical web routing issues as Steadybit agents handle this aspect. You can use EventKit to:
- Forward audit logs to an external system.
- Add markers to monitoring systems' charts during experiment executions.
- Capture experiment execution statistics.
- Report information about experiment executions to Slack, Discord etc.
ExtensionKit logo depicting the text extension kit and a wrench icon
Through kits like ActionKit and DiscoveryKit, Steadybit can be extended with new capabilities. ExtensionKit on the other hand contains helpful utilities and best practices for extension authors leveraging the Go programming language.