c0m4r

Oh rrdtool is still relevant today. Multiple (if not most of) monioring tools like Cacti, Observium, Munin still use it.

Yeah, that's a pain. Every time I boot up new hardware, I wonder how many readings I'll be able to get this time, and if it's even possible. On one computer, I have practically all the temperatures, voltages, and fan speeds, while on another, I can barely read the CPU temperature alone. Not to mention the need to sometimes compile sketchy drivers from github...

That's true, which is why I assume I'll have to gradually implement this feature. It probably won't be perfect, but it's worth trying :)

Thank you for opening the issue!

I'm not currently collecting metrics for containers. Though I might add this feature later on.

If you have a moment, I would be grateful if you could create an issue on github. I will then be able to let you know when it's ready and ask you to try it out. Please also let me know which temperatures you'd like to primarily monitor. I assume I'll have to gradually introduce the supported ones, as not all of them can be detected at once.

I've uploaded these prompts to the repo's wiki if anyone else would like to read my broken English.

A lawyer's opinion will be directly proportional to their fee and will have little to do with reality, because the law hasn't kept up with what's happening right now. If you don't code with AI, you'll be left behind. Everyone is coding with AI, even in places where it's not immediately obvious, there's AI. You open the refrigerator and AI comes out. I don't know how this will be regulated, I'm not an expert in this field, but for now, it is what it is. The most important thing for me is that I don't derive any financial benefit from this and I give attribution where it is due.

I think netdata or Grafana with a chosen backend is right for you then. My goal was different, but I'll consider implementing such functionality in the long run. Thank you for your feedback.

At some point, writing these files became a hassle and I felt it was too chaotic, so I gave up on it. Regarding licenses, given that LLMs are using other people's work without their consent anyway, and most of the code produced rn is AI, these licenses are to me really just suggestions. I would treat them as an expression of intent, not a strictly legal document.

Temperatures monitoring will be added. Initially, I implemented too many metrics, so during development I limited them to a reasonable level to make them manageable, but I'll be adding more as the project matures. Thanks for the feedback!

I respect your opinion, but I disagree with it. It's purely a matter of perspective. I find such restrictions acceptable in free licenses. Besides, as you pointed out, these licenses don't matter anyway, since anyone can use AI and write their own tool :) This choice of license is just my suggestion, or if you prefer, a manifesto that I don't want open source projects to become closed source, that's all.

Initially, yes. However since then I edit it manually, but I agree it still has the AI vibe. I'll work on that!

To be honest, I didn't think about it for too long. I choose licenses based on intuition. I put a lot of work into this tool, I knew it would require a lot of effort, and besides, I created it precisely because someone else turned a similar project into a money-making machine, completely abandoning the original ideals. Therefore, I felt that AGPL, which requires code disclosure and non-profit use, is the way to go.

I think that once I get most of the core functions stable, I will also want to add options for exporting metrics.

It is from LLM and some of the security features are overkill - I'm aware of that. These will be optional. I will also try to improve the readability of the README and move more detailed documentation to the wiki. Thanks for your opinions!

I got your point. The project structure remains from the initial phase of building the tool. I think I'll eventually remove it or put it on the wiki or somewhere else. My excessive attachment to copyright probably stems from the fact that years ago, when I wrote my own websites and articles, people often simply copied them and signed them as their own. The Linux Foundation website has attribution instructions that ask for the use of the ® symbol; I simply followed this instruction, but I agree that it's probably an exaggeration on my part. Considering what this tool does, I personally think it's lightweight in terms of both binary size, execution times, and dashboard performance. But I agree that's debatable.

Nice little panel. Although a bit too kawaii for my taste!

exactly this

That's fair. I can't resist putting easter eggs in my software, sorry :)

Yes, netdata was an inspiration, as I'd been using it for several years. Unfortunately, it stopped being what it initially was, and recently I was so disappointed that I decided to write my own tool. It's also true that I use AI models for coding, but I wouldn't exactly call it vibe coding, as I actively analyze what the models are doing and don't just blindly accept everything. I also try to thoroughly test my code, implement as many security-enhancing features as possible, and have multiple models review my code to catch as many bugs as possible.

Well, it was easy since my native language is Polish and I often use "kula szpiegula" term, which translates to something like a "spying crystal ball" in relation to things that allow monitoring or collecting information. In Polish, "kula" can refer to many things, e.g. a sphere or a globe.

Netdata was actually THE reason I wanted to create my own real-time monitoring system. When I first came across Netdata, it was everything I needed, and its dashboard was fast, clean, and easy to use. But ever since they created the v3 dashboard and started aggressively advertising their cloud services, it became off-putting to me. Thank you for your suggestions, noted!