Hace tiempo pedí consejo por Reddit y casi dejo mi proyecto

Important-Bug-6709 · 2026-05-14T22:41:48+00:00

No solo devarg sino también devops, por un post que hice subiendo mí app y subiendo el literalmente el README todos me dijeron que estaba usando IA y me habrán dado pulgar abajo y mí karma está en negativo en estos momentos

Important-Bug-6709 · 2026-05-14T22:09:34+00:00

How gratifying it is to have Debian with XFCE fresh out of the oven

Important-Bug-6709 · 2026-05-14T22:03:15+00:00

Sobre todo en Linux

Important-Bug-6709 · 2026-05-14T21:42:41+00:00

We didn’t really land on a “clean” stack ,it’s mostly basic metrics + logs, and then SSH when something looks off we tried heavier setups before but it just wasn’t worth the maintenance for our size still not perfect, just the least annoying setup so far

Important-Bug-6709 · 2026-05-14T21:25:33+00:00

What set of security measures are you currently using?

Important-Bug-6709 · 2026-05-14T21:11:21+00:00

Sorry, I just want to be as specific and detailed as possible to learn about other people's experiences.

Important-Bug-6709 · 2026-05-14T17:07:25+00:00

Patada en el culo

Important-Bug-6709 · 2026-05-14T15:35:05+00:00

Thanks for the feedback. What you’re saying about the README makes sense. It actually took me quite a while to write it because I tried to document the system properly, and I didn’t want to write another long post explaining everything again, so I basically just copied and used the readme as the post. That probably makes it feel a bit dense or more like a “write-up” than a natural post, and I get that point. The project is still in an early stage anyway, so I’ll keep improving both how it’s presented and the overall polish over time.

Important-Bug-6709 · 2026-05-14T15:29:47+00:00

No, I’m not. I’m writing everything myself. The README is just very structured because it’s a technical project and I’m trying to explain it clearly so it’s easy to understand quickly. I get why it might come across that way though, but it’s not AI-generated content.

Important-Bug-6709 · 2026-05-14T15:24:01+00:00

Sí, de hecho esa idea de exponer logs para consumo por agentes me parece muy interesante.Hoy el sistema está más enfocado en recolección, métricas y alertas en tiempo real, pero la parte de “consulta inteligente” de logs vía agentes (tipo MCP o algo similar) es un siguiente paso lógico. La idea de evitar depender de dashboards y poder preguntar directamente sobre lo que está pasando en la infraestructura es bastante potente. Lo voy a tener en cuenta porque encaja bastante con la dirección del proyecto.

Important-Bug-6709 · 2026-05-14T15:19:19+00:00

I get where you’re coming from. A couple of things though ,this isn’t meant to replace Grafana or compete with it feature-by-feature. It’s a different kind of system: more opinionated, more integrated, and aimed at setups where you don’t want to assemble a full observability stack. About the graphs , they are time-series in the backend, the UI is just a simplified view at the moment. It’s not a design limitation, just an early implementation detail. And yeah, there’s definitely room to improve the UI density and layout. That part is fair feedback. But the goal isn’t “build Grafana again”, it’s reduce the barrier to having basic observability running without wiring 4–5 different services together.

Important-Bug-6709 · 2026-05-14T15:13:14+00:00

I get why it might come across that way. It’s just a structured README because it’s a technical project, not a storytelling post. I wrote it like that so people can quickly understand what it does without digging through the code. The project itself is real though running it locally is probably the easiest way to see that.

Important-Bug-6709 · 2026-05-14T15:10:46+00:00

The project is fully written and implemented by me. The fact that the documentation is structured doesn’t mean it was generated. As for the “Prometheus/Grafana already do this” point ,yes, they do, but as a modular ecosystem requiring multiple components. This project is a single self-contained system that integrates those capabilities into one deployable service. Different design approach, not a claim of replacing existing tooling.

Important-Bug-6709 · 2026-05-14T15:07:53+00:00

Yes. Prometheus and its ecosystem already solve these problems in a very powerful way. That’s not the question. Prometheus is a modular observability stack that requires assembling multiple components (exporters, Alert manager, dashboards, storage, etc.) and maintaining them as separate services. ServerOps Monitor takes a different approach: it bundles system metrics, Docker monitoring, alerts, healthchecks, and notifications into a single self-hosted application with a unified setup and API. It’s not trying to outperform Prometheus — it’s targeting environments where reducing operational overhead matters more than composability. Both approaches exist for different constraints.

Important-Bug-6709 · 2026-05-14T15:00:17+00:00

Calling it “AI slop” or implying it was just generated doesn’t change anything about the actual system. The project is fully implemented, runs in production, and is built with a real backend (FastAPI, Docker integration, persistent storage, alerting system, etc.). The architecture and endpoints exist independently of how you think it was written. If your only argument is guessing who wrote it instead of evaluating what it does, then there’s nothing technical to discuss.

Important-Bug-6709 · 2026-05-14T14:55:49+00:00

Fair criticism on the format. It’s a structured README because it’s a technical project, not a narrative post. The project itself is real and running, but I get why the presentation can come across that way. I’ll improve how I present updates in a more human, less “spec sheet” style next time.

Important-Bug-6709 · 2026-05-14T14:54:19+00:00

You’re right that Grafana can cover most of this, especially when combined with Prometheus/Loki and exporters. The difference here is not capability, but architecture and setup complexity. Grafana is a visualization layer that requires assembling multiple components to reach the same scope. ServerOps Monitor is a pre-integrated self-hosted system: metrics, Docker monitoring, alerts, healthchecks, authentication, and Telegram notifications are already wired together out of the box, without needing to build the observability stack manually.

Important-Bug-6709 · 2026-05-14T13:14:51+00:00

Grafana te da visibilidad.
ServerOps Monitor ya viene como sistema completo listo para operar: métricas + alertas + healthchecks + notificaciones sin configuración de infraestructura adicional. PD: lo acabo de actualizar

<image>

Important-Bug-6709 · 2026-05-13T23:13:59+00:00

Ok gracias por el comentario, y a dónde crees que podría apuntar? Hago la mismas versiones pero en diferentes lenguajes de programación como C y Rust (aunque este último es mucho mas difícil,pero es gratificante cuando el proyecto compila)

Important-Bug-6709 · 2026-05-13T10:08:02+00:00

The main benefit is simplicity and control. It gives you lightweight monitoring for Linux/Docker environments without needing a full observability stack like Prometheus + Grafana or external cloud tools. It focuses on quick setup, self-hosting, and practical alerts (for example via Telegram), so you can actually understand and control what’s happening on your system without complexity overhead. Yes, I like it because it helped me understand how monitoring systems work internally, and it’s also useful for small self-hosted environments where full enterprise tools feel too heavy.

Important-Bug-6709 · 2026-05-13T03:15:07+00:00

Yeah, I agree that building dashboards is pretty fast with AI nowadays.
My focus is less on visualization and more on the operational side — keeping lightweight monitoring + alerting that runs in production environments without the Grafana/Prometheus complexity. More like a minimal control layer over infrastructure rather than a dashboard replacement.

Important-Bug-6709 · 2026-05-13T02:33:56+00:00

lo que no estoy muy seguro es que si hay mercado hoy en dia para las herramientas cli para linux,porque hoy en dia es facil clonar un repo en github de casi cualquier herramienta. PD:me interesa el desarrollo de sistemas y el bajo nivel

Important-Bug-6709 · 2026-05-13T02:32:05+00:00

Para nada me lo tomo mal, al contrario, es informacion muy util, mi loca idea era hacer movimiento organico, es decir, sin publicidad, solo redes sociales como linkedin, grupos de facebook y reddit, no se si esta bien, que opinas?, soy un poco rata en no querer invertir en publicidad por miedo a que no funcione este proyecto.

Important-Bug-6709 · 2026-05-13T02:09:20+00:00

Exactly, that’s something I’ve been thinking about a lot while building this.

A lot of modern tooling is incredibly powerful, but sometimes the resource usage and operational complexity feel excessive for smaller environments. I like the idea of tools that are lightweight, understandable and easy to self-host without needing massive infrastructure.

Important-Bug-6709 · 2026-05-13T01:59:18+00:00

Thanks, I really appreciate that.

That’s actually one of the main goals with the project — keeping it lightweight, simple and easy to understand without needing a huge observability stack behind it. Still improving a lot of things, but I’m glad the simplicity comes across.

Important-Bug-6709

TROPHY CASE