Retrace combines several tools every development team needs, but we are always open to fresh new ideas. Please submit your feature request/idea for Retrace below.
Clients would like the option to download / export their logs.
I would like to add that we should be able to have automatic exports through integrations to something like Azure Blob and File storage, not only manual exports.
This seems like a huge egress security risk. I think if this were to be added, it would need audit logging.
Exporting of data has become a hot topic here at Stackify. Previous incarnations of export proved to be costly and less scalable than desired so we are rethinking how to accommodate this request.
To help ensure the solution fills the needs, I'd like to request more details on the ask.
I would like to use the export to forward to a security vendor like AlertLogic or Century Link. Would need every 15 minutes or so in batch, but prefer a syslog stream.
For our part, we would simply like to be able to select and export an extract of the logs, like a copy/paste of some lines in Stackify. This would help to share them with other workers.No need for a backup. And it does not have to be the raw logs.
It'd be very helpful to be able to copy & paste lines of logs from Stackify so that logs can be pasted into error / support tickets. As it is now, every time I copy & paste log lines, I have to spend upwards of 10 minutes trying to reformat the lines to some sensible format in Notepad++. I don't need backup capabilities but I'd need significantly better control over selecting lines (and jumping to a particular part of the log after doing a search to see context. (The "View related" feature is nearly unusable.)
This would make my life dramatically easier.
This would be very helpful in both log retention when investigating specific issues as well as performance tracking.
Our primary need is that we must retain logs for a period of time to meet regulatory compliance requirements. Being able to simply have them dumped to an S3 bucket would be ideal. Some configuration over what is archived, via some kind of filtering/routing mechanism, and specifying the target per config would allow control over what is archived, and where it goes.For S3, json format text files that are then gzipped would allow for querying via Athena. Allowing for path formats that automatically upload by date/hour would facilitate this:
You won't be notified about changes to this idea.