You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Often there is necessary to compare trace log files for different values of time_threshold.
Currently we have to change values of this parameter in trace.conf or create another .conf - this is inconveniently.
I think it will be very useful if we can specify some parameters just in command line, without updating trace.conf
For example, if:
Submitted by: @pavel-zotov
Votes: 1
Often there is necessary to compare trace log files for different values of time_threshold.
Currently we have to change values of this parameter in trace.conf or create another .conf - this is inconveniently.
I think it will be very useful if we can specify some parameters just in command line, without updating trace.conf
For example, if:
$ grep "time" my_trace.conf
time_threshold 0
and we issue:
fbtracemgr -se service_mgr -sta -c my_trace.conf -time_threshold 25
-- than only statements that last more than 25 ms will be logged.
Or if we have:
$ grep "<database" my_trcace.conf
<database (%[\\/](ttt%|zzz%|foo%).fdb)|(dbg%|boo%)>
and:
fbtracemgr -se service_mgr -sta -c my_trace.conf -fdb some_new_base.fdb
fbtracemgr -se service_mgr -sta -c my_trace.conf -alias some_new_alias
-- and we can (temply) trace activity for new database or alias that is NOT specified in my_trcace.conf
The text was updated successfully, but these errors were encountered: