| layout | title | description | permalink |
|---|---|---|---|
docs |
Migrating From RisingStack Trace To Keymetrics |
Migrating From RisingStack Trace To Keymetrics |
/docs/usage/from-trace-to-keymetrics/ |
As you might have seen, Trace and Keymetrics had partnered up. Trace was the tool built by the engineers of RisingStack, a monitoring SaaS which use an agent to provide insights into Node.js services.
The partnership of RisingStack & Keymetrics includes merging Trace and its userbase into Keymetrics, and providing technical help to build a superior Node.js monitoring tool.
This piece of documentation is for former Trace users and will help them understand how do properly migrate from Trace to Keymetrics
It requires a very short amount of time to use Keymetrics and PM2 in production. Basically you will just need to use pm2 as a process manager / node.js runtime and use one to command to link it to Keymetrics.
Keymetrics is built on top of PM2, a well known, Open Source process manager that improves performance and reliability of your Node.js applications.
Getting started with PM2 is as easy as:
# Install PM2 globally
$ npm install pm2 -g
# Start your Node.js application
$ pm2 start app.jsYour app is now daemonized, monitored and kept alive forever.
Some of the key features are:
- Automatic clustering and Zero Downtime Reload
- Process Configuration file
- Docker integration
- Auto Source Map resolving, Log management and much ore
Discover all PM2 features via our official documentation.
Now let's get this Node.js application monitored by Keymetrics. Make sure you've created an account and just copy the pm2 link <secret> <public> displayed in the popup and paste it into your terminal.
Instantly, you will see the Keymetrics Dashboard revealed and you can monitor some of the Key Metrics of your application.
As Trace, Keymetrics provides a Transaction Tracing system that allows you to identify which HTTP calls are slow and why they are slow. Unlike Trace, we retrieve all the traces generated by your application, not only the one with issues (so you can inspect even how healthy routes behave)
Learn more about Transaction Tracing
The Trace tracing feature is similar to what can be found under the "Profiling" tab of Keymetrics App:
For CPU profiling, it can be started directly from the Keymetrics interface and stopped any time you want. You will then get a visualisation of the stack and you will still have the ability to download the CPU profiling file.
About Memory Profiling, you have the exact same ability to heapdump memory any time you want.
Learn more about Memory & CPU Profiling
You can find and filter errors in your code and see their stack traces and occurrence data. We also display line code number and logs before exceptions
Learn more about Exceptions Tracking
With Keymetrics you can also monitor criticals metrics and also have data retention of 14 days. This will be extended to 60 days in the next month.
Learn more about Metrics Monitoring
The Trace Uptime Webchecks and Topology overview will be developped in the following months in partnership with RisingStack team.
- Custom metrics allows you to track variable value over time
- Remote Functions Trigger allows you to trigger code function straight fronm the dashboard
Also, the teams of Keymetrics & RisingStack created a webinar which will help you in the migration & the unanswered questions you have. Here is the link of the upcoming webinar.