New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Trace API [CORE1734] #2158
Comments
Commented by: Sean Leyne (seanleyne) The TraceAPI, which was originally created by Nikolay Samofatov while he was at BroadView, will be added in a future release (it is being discussed for inclusion in v2.5). |
Commented by: @WarmBooter Thanks Sean. I guessed that, but I could not find any issue in the tracker about this, so I decided to post one so it will not be forgotten, and interested people can vote in the issue to raise its priority ;-) Anyway, a previous talk with Vlad a few days ago surprised me when he told me that he wasn't sure if this feature would be implemented in 2.5 or even was being discussed at all. |
Commented by: @dyemanov Possibility for having this feature in v2.5 will be discussed by TTG starting from the next week. |
Commented by: Van den Wouwer Danny (dannyvdw) test |
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 Beta 2 [ 10300 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Submitted by: @WarmBooter
Votes: 2
It would be nice to have a Trace capability in the server, to be able to track everthing that happened in the databases of a server. Example of usage would be for web hosting companies who are offering Firebird databases hosting, and wants to know what customers were doing that could be causing server slowdowns, freezing, crashes, etc. This is a real problem, specially if SuperServer is being used.
Maybe this can be based on the actual TraceAPI of RedDB by RedSoft, if appropriate.
The text was updated successfully, but these errors were encountered: