This is documentation for the next version of Grafana k6 documentation. For the latest stable release, go to the latest version.
Explore extensions
Extensions can be used to extend the core k6 features to fit your performance-testing use cases. There are two main categories of extensions: official and community.
Official extensions
These are extensions owned and maintained by Grafana Labs, with support for a wide range of versions.
| Extension | Description | Versions |
|---|
Community extensions
These are extensions developed by the community, with support for specific versions.
Note
We’re working on a process for community folks to submit their extensions.
| Extension | Description | Versions |
|---|
Use extensions
There are two ways to use extensions when running a k6 test script.
Automatic extension resolution
You can use these extensions without any additional configuration. k6 automatically resolves and loads them when you use them:
- JavaScript extensions are loaded when you import them in your test script.
- Subcommand extensions are loaded when you invoke them using
k6 x <subcommand>. Refer to subcommand extensions for details.
Custom k6 binary
If you have developed your own k6 extension or want to use an extension that’s not available through automatic extension resolution, you have to build a custom k6 binary. The process involves using the xk6 tool to compile k6 with your desired extensions included. Custom binaries give you the flexibility to incorporate any extension from the k6 ecosystem.
Refer to build a custom k6 binary guide to learn how to create your own k6 binary with custom extensions.
Caution
Many other extensions maintained by members of the k6 ecosystem are available in GitHub. These extensions aren’t maintained nor audited by Grafana Labs.
