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
For example there can be situations when you had to trace actions from particular USER, IP or Application with several seconds of session duration.
It is unreal to determine connection_id during these seconds and change config file, but it is necessary to trace all sessions by USER/IP for a long period.
The text was updated successfully, but these errors were encountered:
description: For example there can be situations when you had to trace actions
from particular USER, IP or Application with several seconds of
session duration. It is unreal to determine connection_id during these seconds
and change config file, but it is necessary to trace all sessions by USER/IP for a long period.
=>
For example there can be situations when you had to trace actions from particular USER, IP or Application with several seconds of session duration.
It is unreal to determine connection_id during these seconds and change config file, but it is necessary to trace all sessions by USER/IP for a long period.
summary: fbtracemgr: add filtration for fields USER, IP (by mask), ROLE, Application in addition to connection_id. => fbtracemgr: add options to filter based USER, IP (by mask), ROLE and Application fields in addition to connection_id.
summary: fbtracemgr: add options to filter based USER, IP (by mask), ROLE and Application fields in addition to connection_id. => fbtracemgr: add options to filter on USER, IP (by mask), ROLE and Application fields in addition to connection_id.
> It seems that this request should be handled by a downstream analysis tool, rather than the trace manager directly.
This feature is more useful and convenient than currently available connection_id.
And more than - it gives opportunity for server to trace less data - it would increase
performance and decrease logfile size.
I think, third party tools haven't to be mentioned here at all.
Submitted by: Viktor Belzetskiy (viktor_bs)
Votes: 6
For example there can be situations when you had to trace actions from particular USER, IP or Application with several seconds of session duration.
It is unreal to determine connection_id during these seconds and change config file, but it is necessary to trace all sessions by USER/IP for a long period.
The text was updated successfully, but these errors were encountered: