From 5eb260b432074b01d32cd4d7e07035bb06157d88 Mon Sep 17 00:00:00 2001 From: Alexander Lukyanchikov Date: Sun, 11 Aug 2019 22:14:37 -0400 Subject: [PATCH] Update README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index df301cb..3801d0a 100644 --- a/README.md +++ b/README.md @@ -41,9 +41,9 @@ Using Sampler is basically a 3-step process: - Adjust components size and location on UI ## But there are so many monitoring systems already -Sampler is by no means an alternative to full-scale monitoring systems, but rather fast and easy to setup development tool. +Sampler is by no means an alternative to full-scale monitoring systems, but rather easy to setup development tool. -If spinning up and configuring [Prometheous with Grafana](https://prometheus.io) is complete overkill for you task, Sampler might be the right solution. No servers, no databases, no deploy - you specify shell commands, and it just works. +If spinning up and configuring [Prometheus with Grafana](https://prometheus.io) is complete overkill for you task, Sampler might be the right solution. No servers, no databases, no deploy - you specify shell commands, and it just works. ## Then it should be installed on every server I monitor? No, you can run Sampler on local, but still gather telemetry from multiple remote machines. Any visualization might have `init` command, where you can ssh to a remote server. See [SSH example](https://github.com/sqshq/sampler#ssh)