Performance problems are mostly hard to locate and to fix. Unlike other ongoing errors such as logical and algorithmic errors and bugs, which developers solve during coding provided the information pointing to the error cause, performance problems normally come without many hints. That's when our brains start to pick every piece of context available in order to deduct the root cause. This information may include multiple log files, database state, system and application metrics, also the time when the problem occurred is important in order to exclude possible known external causes.
With that in mind, Nodetime tries to provide as much information as possible to the developer to make performance problem tracing faster, which is critical in every aspect. With powerful core tools, such as transaction tracing, CPU profiling and heap profiling already available, Nodetime is adding monitoring to its arsenal. In addition to real-time metrics, it features historical metrics and a possibility to set up alerts for all available metrics.
Here is how historical metrics look in the web console:
And the alerts setup page: