The trigger API should warn the client when an unsupported condition is being used
Clients should be warned whenever they register a trigger that won't be evaluated. For the moment, the main use case is warning a client if a buffer usage condition is used and the lttng-modules version being used is older than 2.10.
Updated by Jérémie Galarneau about 3 years ago
- A deactivated monitor timer being set on a channel to which a condition is being associated
- An absolute size that is larger than the buffer size of a given channel
Those should be warnings since a channel matching the same criteria may be registered later on. A low-effort fix would consist in logging this warning as part of the lttng-sessiond's logs.