We’ve improved the process for using Synthetics’ private minions by enabling them to be run them in a container, instead of using an appliance on a virtual machine. This enables greater ease of use and flexibility when monitoring from any location, and behind their firewall. External blogpost here
What we did:
We improved on our private minions (which ran in a heavier appliance) by now inputting our Synthetics application inside of a container. You wanted an easier-to-use interface when monitoring from any location, and behind the firewall.
By using a container to run private minions we’re giving you:
- Greater ease of use (set up, configure, deploy)
- More control (host provisioning under compliance)
- More cloud friendly (containers are supported by cloud providers & easier to run in the cloud vs. our previous version of private minions → an appliance using VMs)
- Ability to use Kubernetes or other orchestration tooling
- More secure (less patches to fix because we’re shipping less packages)
What are we solving?:
We’re improving on our previous feature (private minions) which utilized an appliance and a virtual machine to run minions that monitored from any location, and behind the firewall. Because our legacy private minions were so heavy (shipping an appliance) they were time-intensive to install / configure / upgrade, provided challenges with teams in enterprise orgs (teams who monitor aren’t always teams who control VMs), often had to be massaged to run in cloud environments, and offered a host of other challenges and dependencies.
With containerized private minions we’re giving more control to you, the customer, with all the benefits that come from containers.
How easy is it to use?:
Super easy! To upgrade to CPM you need a pre-existing private location (or you’ll need to create a new one), and a docker capable host. Then, simply copy the private location key, and run the docker command.
Who else does this?:
Nobody else (that we know of) utilizes containers to run their synthetic applications.
Why should you care?
We’re making synthetic monitoring easier, and giving you much more control. You’ll be able to run synthetics monitors from any location / behind their firewall significantly easier. You’ll benefit by: greater ease of use in set up / configure / deploy, increased security, more cloud friendly, and will be able to utilize your orchestration tooling, like Kubernetes.
Other helpful links:
Walkthrough of the set up:
(in “Private locations” located within the Synthetics UI, click “Add New”)
(add the name of the private location, and a description, then hit “Generate key”)
(Your key will be generated, with the code ready to be copied and pasted into your docker container)
(add the code to into your terminal and hit “enter”, then the minion will run a health check, when you see the rocket ship you’re ready to go!)
(Go into your pre-existing monitors, or create a new one, add the private location, and hit “save”)
(from there, you can begin to see the results of your dockerized private minion in the test)