Run the Agents Locally
Instructions on how to run the WarpStream Agent locally for testing / development purposes.
Last updated
Was this helpful?
.svg?alt=media&token=de534435-d87b-4f47-a762-54ed6aae1b02)
.svg?alt=media&token=5df48930-f99f-4779-b05f-359312e79636)
Instructions on how to run the WarpStream Agent locally for testing / development purposes.
Last updated
Was this helpful?
First, for your platform.
Once you've installed the WarpStream Agent, you can run the playground command to create an account for local development as well as an ephemeral Kafka cluster and Schema Registry cluster.
The playground stores data in memory only by default, so any data written will no longer be accessible once the process exits.
Once the docker container is running, there will be a Kafka TCP server listening on port 9092 and a Schema Registry HTTP server listening on port 9094.
This means you're ready to run any application locally that expects to connect to Kafka, and it'll connect to WarpStream instead if you set the bootstrap URL to localhost:9092.
You can also replace the URL of your schema registry clients to localhost:9094 and it'll connect to WarpStream's Schema Registry instead.
If you encounter any problems connecting an application running outside of Docker to the WarpStream agent running inside of Docker, follow .
Alternatively, if you installed the standalone WarpStream Agent binary and it is in your PATH, you can just run:
The playground stores data in memory only by default, so any data written will no longer be accessible once the process exits.
Once that completes, run the following command to test the Kafka connection:
If that succeeds, then you're ready to run any application locally that expects to connect to Apache Kafka, and it'll connect to WarpStream instead if you set the bootstrap URL to localhost:9092.
If the diagnostic command returns an error, follow the provided instructions to diagnose and fix it.
To test the Schema Registry connection, you can send a request to the server with curl as follows:
If you receive a valid response, such as {"id":1}, then you're ready to run any application locally that expects to connect to a schema registry by replacing schema registry URL with localhost:9094.
Once the binary is installed, run the following command to test the connection:
If that succeeds, then you're ready to run any application locally that expects to connect to Apache Kafka, and it'll connect to WarpStream instead if you set the bootstrap URL to localhost:9092.
If the diagnostic command returns an error, follow the provided instructions to diagnose and fix.
The WarpStream Agent binary ships with a utility for diagnosing connection issues. However, diagnosing connection issues cannot be done in a general purpose manner from within a Docker container. Therefore even if you're running the Agent in a Docker container locally, you'll need to follow our to install the raw WarpStream Agent binary locally before proceeding.