rayelliott
/
sampler-fork
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update README.md

This commit is contained in:
Alexander Lukyanchikov 2019-08-11 22:14:37 -04:00 committed by GitHub
parent c6f6e7c719
commit 5eb260b432
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@ -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)