philbob
/
grafana_af2c
1
0
Fork 0
Code Issues 5 Pull Requests Packages Projects 1 Releases Wiki Activity

more sensible README 

explaining how this shit works

something more than just "it just works"
This commit is contained in:
philbob 2024-12-28 00:15:56 +00:00
parent 5e38812115
commit 418fe2b5a0
1 changed files with 18 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -27,4 +27,21 @@ dependencies (for debian): what I've installed:
1.4 everything is ready? then we start up container 1.4 everything is ready? then we start up container
sudo docker-compose up sudo docker-compose up
and connect with localhost (by default it should be localhost:3000) and connect with localhost (by default it should be localhost:3000)
2. because we start with monitoring what's going on our own server, we will deploy prometheus and node_exporter now.
let's start with node_exporter becasue this is the source of data about our server
2.1 add docker config for node exporter
2.2 add docker config for prometheus
HUGE DISCLAIMER ABOUT NETWORKING:
technically, every application has own container which mean it also has its own networking rules. for tests, I connected it together that:
1. turn on containers: docker-compose up -d
2. list working containers: docker ps
3. inspect them: docker inspect <container name>
4. look for "NetworkSettings" and sub-category Networks
5. look for value in "IPAddress" because this is our "localhost" for particular container
6. take this value and get access to container with this pattern http://<IPAddress>:assigned_port