I know that there is a practice to write data by Influx protocol into InfluxDB. Also I know that InfluxDB have an issues with high RAM consumption on running device. Is this system compatible with VictoriaMetrics ? Because it can be run as simple binary file and as I know it requires less memory and cpu.

Hey, This is really cool - thanks for all the hard work :smile:

Just thought I'd raise this, as it was a small issue I hit.

my hardware:

1 x raspberry pi 4 (8gb) 2 x raspberry pi 3b+ 's (1gb) 7 x raspberry pi compute module 3+'s (1gb) All running ubuntu server 20.04 LTS 64-bit

On trying to install using your Ansible, i got this error across all nodes:

fatal: [node2]: FAILED! => {"changed": true, "cmd": ["dpkg", "-i", "libseccomp2_2.5.1-1_armhf.deb"], "delta": "0:00:00.237499", "end": "2021-06-18 14:07:28.893279", "msg": "non-zero return code", "rc": 1, "start": "2021-06-18 14:07:28.655780", "stderr": "dpkg: error processing archive libseccomp2_2.5.1-1_armhf.deb (--install):\n package architecture (armhf) does not match system (arm64)\nErrors were encountered while processing:\n libseccomp2_2.5.1-1_armhf.deb", "stderr_lines": ["dpkg: error processing archive libseccomp2_2.5.1-1_armhf.deb (--install):", " package architecture (armhf) does not match system (arm64)", "Errors were encountered while processing:", " libseccomp2_2.5.1-1_armhf.deb"], "stdout": "", "stdout_lines": []}

I just switched the URL to point to an arm64 binary instead and all was fine. I was going to make the change and open a pull request, but i appreciate you may want to keep the current armhf deb in place for a number of reasons! If not, let me know and I'll get a pull request opened!

For anyone who may come across this issue in future, my fix was updating the ansible-playbook-libs.yaml file to the following:

  - name: Download libseccomp2.deb
    command: "wget http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_arm64.deb"
    become: yes

  - name: Install libseccomp2.deb
    command: "dpkg -i libseccomp2_2.5.1-1_arm64.deb"
    become: yes`

Thanks again!

Hello, first of all thank you so much. This repo is so great for a small start on monitoring Raspberry Pi's.

I couldn't find the InfluxDB Dashboard you have attached in the README anywhere in the repo. Am I missing something or did you simply not added the dashboard to the project?

Hi,

I really like the light-weight nature of Omni. It was simple to install as well. I was like you, I tried to run Prometheus on my 3 pi k3s cluster, and while it would run for a day or so, it would soon crash no mater how many resources I gave to it.

Would it be possible to add pod-specific statistics to Omni? I'd like to be able to make sure that individual pods don't run out of disk space, and also see how much CPU they consume over time. I do have the Kubernetes dashboard installed, but I'd like the flexibility of setting up alerts etc.

Thanks!

P.S. it was awesome hooking up Omni to the influx free cloud service. I had no idea that existed, and its great for my small use-case!

The library url http://ftp.us.debian.org/debian/pool/main/libs/libseccomp/libseccomp2_2.5.1-1_armhf.deb for the wget shown in both the readme and the ansible playbook returns 404 now.

I am figuring out the update and will do a PR but if anyone else gets this error I am poking around on the packages webpage here to find the updated url.

For now I I have 64 bit Ubuntu 21.10 on my rpi4 cluster so the latest version was installed anyways and all worked great. Thanks again for thsi project

this is great - I did EXACTLY what you did and setup Prometheus and Grafana and nearly killed my 4-node Rpi cluster. When I set everything up, I ended up seeing in the omni pod logs this error:

                omni
                return self.request("POST", url,
                omni
                File "/usr/local/lib/python3.8/site-packages/influxdb_client/rest.py", line 250, in request
                omni
                raise ApiException(http_resp=r)
                omni
                influxdb_client.rest.ApiException: (401)
                omni
                Reason: Unauthorized

There is a corresponding error in influxdb:

              influxdb
              ts=2021-10-13T17:10:18.772914Z lvl=info msg=Unauthorized log_id=0XAaFye0000 error="token required"

I've triple-checked, and tried a couple of different kinds of tokens. Have you seen any common reasons for this? Thanks in advance for any help, if I can end up helping here I'll do so but I'm pretty rusty.