I notice that the metadata of per-PID user-space traces has three attributes
which are dropped from the equivalent per-UID trace:
Per-PID trace:
env {
hostname = "sds-dut-vb";
domain = "ust";
tracer_name = "lttng-ust";
tracer_major = 2;
tracer_minor = 3;
tracer_patchlevel = 0;
vpid = 7024;
procname = "simple";
};
Per-UID trace:
env {
hostname = "sds-dut-vb";
domain = "ust";
tracer_name = "lttng-ust";
tracer_major = 2;
tracer_minor = 3;
};
The trace data are the same in this case (two trace sessions capturing the
same events in parallel), so this change in metadata only shows up in
babeltrace's output (when using '-f all -n all' for example).
Is this intentional? It does mean per-UID traces "anonymize" the event data
slightly. And why is "tracer_patchlevel" dropped alongside the process-related
attributes?
Daniel U. Thibault
Protection des systèmes et contremesures (PSC) | Systems Protection &
Countermeasures (SPC)
Cyber sécurité pour les missions essentielles (CME) | Mission Critical Cyber
Security (MCCS)
R & D pour la défense Canada - Valcartier (RDDC Valcartier) | Defence R&D
Canada - Valcartier (DRDC Valcartier)
2459 route de la Bravoure
Québec QC G3J 1X5
CANADA
Vox : (418) 844-4000 x4245
Fax : (418) 844-4538
NAC : 918V QSDJ <http://www.travelgis.com/map.asp?addr=918V%20QSDJ>
Gouvernement du Canada | Government of Canada
<http://www.valcartier.drdc-rddc.gc.ca/>
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
