(评论)
(comments)

原始链接: https://news.ycombinator.com/item?id=41240379

在过去的 5 个月里,我们一直在与 7 名开发人员和 3 名外部贡献者组成的团队一起开发 BlueWave 正常运行时间管理器 [1],直到今天,我们始终处于人们的关注之下。随着我们从基本的正常运行时间跟踪扩展到全面的正常运行时间管理器, 监控解决方案,我们有兴趣从社区获得见解。对于那些管理服务器基础设施的人来说,- 除了 CPU、RAM 和磁盘使用等基础设施之外,您还监控哪些关键资产?- 您是否还密切关注网络 performance, processes, services, or other metrics?Additionally, we're debating whether to build a custom monitoring agent or leverage existing solutions like OpenTelemetry or Fluentd.- What’s your take—would you trust a simple, bespoke agent, or would you feel more secure with a well-established solution?- Lastly, what’s your preference for data collection—do you prefer an agent that pulls data or one that pushes it to the monitoring system?[1] https://github.com/bluewave-实验室/bluewave-正常运行时间

相关文章

原文
We've been developing the BlueWave Uptime Manager [1] for the past 5 months with a team of 7 developers and 3 external contributors, and till today we always went under the radar.

As we move towards expanding from basic uptime tracking to a comprehensive monitoring solution, we're interested in getting insights from the community.

For those of you managing server infrastructure,

- What are the key assets you monitor beyond the basics like CPU, RAM, and disk usage?

- Do you also keep tabs on network performance, processes, services, or other metrics?

Additionally, we're debating whether to build a custom monitoring agent or leverage existing solutions like OpenTelemetry or Fluentd.

- What’s your take—would you trust a simple, bespoke agent, or would you feel more secure with a well-established solution?

- Lastly, what’s your preference for data collection—do you prefer an agent that pulls data or one that pushes it to the monitoring system?

[1] https://github.com/bluewave-labs/bluewave-uptime

联系我们 contact @ memedata.com