Add ability to the trace plugin to configure traced services events on per-service name basis [CORE2767] #3159
Comments
Modified by: @hvladassignee: Vlad Khorsun [ hvlad ] |
Modified by: @hvladstatus: Open [ 1 ] => In Progress [ 3 ] |
|
Commented by: @hvlad Unfortunately, proposed way to configure individual service is not possible with current implementation. The problem is that configuration passed to the trace plugin only at time when service attachment is created and at this time service task name is not known. It will known at time when service will start. Also note that same service attachment is able to run another task when current task is finished. Therefore i implemented another, less elegant but also useful way to configure which services should be traced (or not traced). Now "include_filter" and "exclude_filter" regular expressions also allowed in <services> section and when some service task is started (or queried) its name is matched agains this filters to determine if corresponding event should be logged. |
Modified by: @hvladstatus: In Progress [ 3 ] => Resolved [ 5 ] resolution: Fixed [ 1 ] Fix Version: 2.5 RC2 [ 10372 ] Fix Version: 3.0 Alpha 1 [ 10331 ] |
Modified by: @pcisarstatus: Resolved [ 5 ] => Closed [ 6 ] |
Modified by: @pavel-zotovQA Status: No test |
Submitted by: @hvlad
Extend syntax of <service> section of trace configuration and make it the same as for <database> section.
I.e. allow <service [pattern]> syntax, where optional "pattern" is matched against name of service, such as "Backup Database", "Repair Database" etc.
Full list of currently used names already present in svc.spp and should be part of sample fbtrace.conf file.
Commits: 950bcd8 0335e1c
The text was updated successfully, but these errors were encountered: