TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ask HN: Need advice on Node.js and express metrics monitoring

2 点作者 fpd4444超过 6 年前
Hello everyone,<p>I’m the CEO of a team of developers, we mostly develop web-based applications using ES + node.js + express + React.<p>For every application we implement for our customers we have to be confident about maintaining our SLA-related metrics (we’ll simply lose customers if we aren’t able to meet our SLA terms) - which requires a proper metrics monitoring such as response time, error rates, etc.<p>We had to invent a new small infrastructure each time we implement a new project, most often it was ES + Grafana&#x2F;Kibana + modifications inside the app to collect metrics and ship them into the ES instance.<p>So we got tired of doing the same thing over and over and created a cloud-hosted tool for our internal usage, which monitors all our node.js + express applications, we called it SLAO.<p>It monitors all the methods calls with response codes, durations, headers, and other metrics, and we made its integration as simple as it could be - by adding a single row of code: app.use(slao()).<p>Now we only use SLAO internally, but we’re considering publishing it as a cloud service because we think that we’re not the only team that had such node.js + express app monitoring issues.<p>What do you think about this whole idea, should we go for it?<p>P.S.<p>If anyone wants to test it - just text me and I’ll give you a test access.

暂无评论

暂无评论