Retrace: Ideas Portal

Since APIs are supposed to be fast e.g. under 1 second it means you are constantly looking at fractional time. Default the views to display milliseconds to avoid having to do mental math and multiplying all values by 1000. Easy at a glance to not ...

Consider the attached screenshot which displays several POST api calls going to Customer controller (attribute-base routing is in use). From the Url column you cannot read which call when to which endpoint. One can hover ober the links to see the ...

The Retrace grid will truncate the environment name around 11 characters and we use a suffix at the end of the environment name that tells us if it is for dev, prod, staging etc. I have no way of viewing the full environment name in the grid, I h...

Once there is a performance issue or error noticed it can be difficult to catch a traced request. Trace all requests for a given URL would likely need to shut itself off after a period of time to not impose performance issues with the app (I woul...

I've been looking at ways we can improve our logging/error reporting and one of the issues we're having now, is that some of our exception stack traces are effectively useless. With async methods, LINQ queries and the like, it's quite common to se...

It would be useful to have plugins available where we could track metrics over time of our 3rd party apps. For Elasticsearch, this would mean graphing document growth, query latency, index time, etc.

Once client-side monitoring is available, it will be important to have support for source maps in JS to help with debugging minified code.

Instead having a specific support for each database type, there is a generic JDBC api which can be used to query a database through the driver.

MariaDB is a fork for MySQL so the driver and connection string are the same.

This seems like it would be a quick item to develop. This would make the selection of your Saved Search much faster.