11/2/2021»»Tuesday

Sensu Go Docker

Cd sensu-docker sudo./setupsensudocker.sh generate sudo docker-compose -f base.yml build sudo docker-compose -f base.yml up it's normal to see a rc or console errors and they can safely be ignored. Once the download and build process is done you can run sudo docker-compose -f base.yml up to start the cluster. Generate certificates for your Sensu installation. This guide explains how to generate the certificates you need to secure a Sensu cluster and its agents. When deploying Sensu for use outside of a local development environment, you should secure it using transport layer security (TLS). While I was there primarily working the Sensu booth, it occurred to me that Docker presents an ideal way to demo what Sensu does, and I can quickly get an environment up without having to go through the rigmarole that I previously did using Vagrant.

This past week, I had the pleaseure of attending Dockercon. While I was there primarily working the Sensu booth, it occurred to me that Docker presents an ideal way to demo what Sensu does, and I can quickly get an environment up without having to go through the rigmarole that I previously did using Vagrant. Now, that’s not saying that I think one tool is better than the other, but for the purposes of quick demos, Docker is more useful to me.

So let’s go over the setup.

Docker details

I’m primarily using Docker for Mac right now, since I’ve switched over from my Linux laptop. But now that I’ve covered that, let’s take a look at this little repo I’m using.

And a look at the docker-compose file:

Sensu go docker 2

What we end up with here is a backend, an agent, and a local asset server (SUPER useful if you’re on 💩 wifi/internet). This means that I can quickly spin up an agent and a backend, and then drop any asset that I need to use in the assets directory and have the agent download it quickly.

This makes demos super quick to spin up, and I can scale a bunch of agents if I want to show a large number of agent containers connecting to the backend.

Cheers!

Share!

This past week, I had the pleaseure of attending Dockercon. While I was there primarily working the Sensu booth, it occurred to me that Docker presents an ideal way to demo what Sensu does, and I can quickly get an environment up without having to go through the rigmarole that I previously did using Vagrant. Now, that’s not saying that I think one tool is better than the other, but for the purposes of quick demos, Docker is more useful to me.

So let’s go over the setup.

Sensu Go Docker Compose

Docker details

I’m primarily using Docker for Mac right now, since I’ve switched over from my Linux laptop. But now that I’ve covered that, let’s take a look at this little repo I’m using.

Sensu Go Docker Download

And a look at the docker-compose file:

What we end up with here is a backend, an agent, and a local asset server (SUPER useful if you’re on 💩 wifi/internet). This means that I can quickly spin up an agent and a backend, and then drop any asset that I need to use in the assets directory and have the agent download it quickly.

This makes demos super quick to spin up, and I can scale a bunch of agents if I want to show a large number of agent containers connecting to the backend.

Cheers!

Sensu Go Docker Pro

Share!

Most Viewed Posts