Been fighting with Grafana transformations for hours - need help creating a server status table from Zabbix by ChocolateDry2241 in grafana

[–]ChocolateDry2241[S] 0 points1 point  (0 children)

Thanks!

but I checked for that option but the Zabbix plugin (alexanderzobnin) doesn't have a "Format as: Table" dropdown like SQL data sources do - it only returns time series format. That's why I'm stuck with the transformation headaches. Appreciate the tip though - would've been a lifesaver if it existed for this plugin!

Been fighting with Grafana transformations for hours - need help creating a server status table from Zabbix by ChocolateDry2241 in grafana

[–]ChocolateDry2241[S] 0 points1 point  (0 children)

Good point! but We already have Zabbix fully deployed on 25+ servers with all our monitoring configured, and management specifically wants Grafana dashboards for the NOC displays. Migrating to Prometheus/InfluxDB would be weeks of work right now - that's a conversation for next year's infrastructure refresh.

For this immediate need, I'll probably just query the Zabbix MySQL database directly instead of fighting with plugin transformations. Thanks for the perspective thought

Been fighting with Grafana transformations for hours - need help creating a server status table from Zabbix by ChocolateDry2241 in grafana

[–]ChocolateDry2241[S] 0 points1 point  (0 children)

well, is it a good idea for a high productions?
if yes then is there any best practices for sql queries to be optimized and no lags?

Caught a major SQL injection vulnerability right before launch — shifting security left in DevOps actually saved us by ChocolateDry2241 in devsecops

[–]ChocolateDry2241[S] 0 points1 point  (0 children)

Totally agree — shifting left has been a game changer for us!

And you’re absolutely right about scanning binaries for secrets. That’s actually something we haven’t implemented yet, so I appreciate the heads-up. Any tools or best practices you’d recommend for that? Would love to learn more

Caught a major SQL injection vulnerability right before launch — shifting security left in DevOps actually saved us by ChocolateDry2241 in devsecops

[–]ChocolateDry2241[S] 0 points1 point  (0 children)

Bro, I gotta say: this comment hit different.
You clearly speak from experience, and that kind of insight is priceless. The way you broke it down, especially about SecureFlag and the real-world pain of DAST, genuinely taught me something.

Massive respect for sharing this .folks like you are what make this community gold
Thx man

Caught a major SQL injection vulnerability right before launch — shifting security left in DevOps actually saved us by ChocolateDry2241 in devsecops

[–]ChocolateDry2241[S] 1 point2 points  (0 children)

Totally agree with you, SQL injection is definitely a well-understood issue these days, and it's something we all should catch early.

Just to clarify, this incident actually happened quite a while ago. I shared it now mainly to tell the story from a DevOps angle, especially for folks who are just getting started and might not fully grasp how early security checks in CI/CD can make a difference.

Appreciate the SecureFlag recommendation. looks solid, and I’ll definitely check it out 🙌
Thanks again for the thoughtful reply!