Retrace: Ideas Portal

When looking at the Log Query Monitors (https://s1.stackify.com/Monitoring/Resources/Logs), each monitor has a link that says "View Log Dashboard". For log queries based on saved searches, this link takes us to that search (https://s1.stackify.com...

We have a threshold % error monitors on our web app that alerts once in a while when the number of errors are reaching to the set % threshold, the problem is that when it alerts and i get it on the phone, i open the link and gives me a graph of th...

Java Logback framework has a way to group logs using markers, similar as how stackify does with hashtags. Would be nice if stackify could pick up these logback markers and use them in the same way hadhtags are used.

Ability to export website monitor data so that up time and other metrics can be exported and audited outside of Retrace

A way to efficiently add and remove sites in bulk. Enhancing the existing Add Site/Remove Site functions to allow multi-select would work well for this, and may be applicable to more customers than the naming convention idea?

I always wonder: how many hits have we had of xyz in the last week, month, etc.? There's a graph with numbers per timespan - but no total number is given. I think it would add value to display that.

The logging in Stackify has a limit on the max JSON parameters that are collected. It would be nice if there was a way to specify what parameters a user wants so that the fields, filters, and search can be optimized to the information most useful ...

The public dashboard urls are rather cryptic. To give our team easy access to them, one simple way of doing that would be to show the dashboard inside an iframe on our company's website.The same idea holds for making a dashboard available to our c...

We have an API that shares the same URL, but has a different parameter, but for support folks who's actually looking at it, it would be easier to tell if we can specify a title, so when we're looking at slack, there's title then the url. Example:M...

Currently when a trace is thrown away for hitting the 5000 limit there is not indication of where the failure occurred which leaves no indication of where to apply work to decrease the trace size so that profiling is possible. It would be helpful...