servicesgogl.blogg.se

1. #Synology rt2600ac minimserver how to#
2. #Synology rt2600ac minimserver install#
3. #Synology rt2600ac minimserver update#
4. #Synology rt2600ac minimserver download#

Every deploy is unique, so with the information above you'll have everything to connect Grafana objects to your collections.įeel free to ask any questions I'll do my best to answer.ĬREDITS: Monitor-Internet.py and Monitor-Pihole.py were not built by me. I won't be posting my grafana Dashboard because I believe it won't suite your environment.

#Synology rt2600ac minimserver install#

Install the Libraries used by those scripts using pip3Ĭonfigure crontab to run Internet and Pihole scriptsĬonfigure your container to run the other 2 scripts upon restartĬonfigure your influx datasources on grafana ROUTER - Default Collection time is every 30+- secs.Ĭonfigure your database on the provided nf file and copy it to your telegraf container.Ĭopy scripts to your linux container and edit them with your info as explained above NARS - Default Collection time is every 30+- secs. Summary.LastDay - Collected every 1 hour. ROUTER - Default collection time is every 30+- secs, with a few exceptions. NAS - Everything is collected every 30+- secs. Everything else is collected locally by Telegraf using the exposed docker.sock. Keep in mind that every serie that has REMOTE in the name is collected remotely by SNMP or restful API. Half of the APIS used by me are not documented by Synology and they were extracted by a process of observation and experimentation.īoth Monitor-NAS and Monitor-Router use the default Telegraf database called telegraf to store data. Not my fault! I'm just emulating the act of browsing your nas interface and extracting this information.

#Synology rt2600ac minimserver update#

Monitor-ROUTER.py - Update lines 20-25 to reflect your NAS IP/Username/Password - IMPORTANT: This user must be a ROUTER admin(Follow this guide to create a second admin user on your Synology router), otherwise the API calls performed by the python script will fail.

Half of the APIS used by me are not documented by Synology and they were extracted by a process of observation and experimentation. Monitor-NAS.py - Update lines 14-20 to reflect your NAS IP/Username/Password - IMPORTANT: This user must be a NAS admin, otherwise the API calls performed by the python script will fail.

Monitor-Pihole.py - Update the included config_pihole.ini file to reflect your Pihole IP/Username/API Location Monitor-Internet.py - Update the included config_internet.ini file to reflect your InfluxDB IP/Username/Database Name After that clone this repository and store and configure those scripts to run using crontab on your container. So when I get to home I do this stuff to relax, so I don't take it too seriously.įor the Python part I recommend pulling the CentOS docker base image and installing python3 on it. I already work with complex systems on a daily basis. That being said I believe anyone with a little bit more than basic knowledge will be able to follow along and deploy your version of this stack.Īlso keep in mind, this is an early build, so expect some bugs and improvements. I won't go step by step since text is not the best form to explain complex procedures.

#Synology rt2600ac minimserver download#

The idea here is to provide what you need to download and provide the configuration files for it.

#Synology rt2600ac minimserver how to#

Some people demonstrated interest and asked me to provide instructions on how to achieve the same. A few days ago I posted a screenshot from my iPhone that included my Synology Infra monitoring dashboard.