Thursday 24 January 2019

Need your advice on node.js + express metrics monitoring

Hello everyone,I’m the CEO of a team of developers, we mostly develop web-based applications using ES + node.js + express + React. 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.We had to invent a new small infrastructure each time we implement a new project, most often it was ES + Grafana/Kibana + modifications inside the app to collect metrics and ship them into the ES instance.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. 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()).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.What do you think about this whole idea, should we go for it? P.S. If anyone wants to test it - just text me and I’ll give you a test access.

Submitted January 24, 2019 at 11:55AM by fpd4444

No comments:

Post a Comment