Project

General

Profile

Actions
Copy link

Bug #1105

open

The trigger API should warn the client when an unsupported condition is being used

Added by Jérémie Galarneau over 7 years ago. Updated over 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
LTTng - 2.10
Start date:
05/12/2017
Due date:
% Done:

0%

Estimated time:

Description

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.

Actions
Copy link
 #1

Updated by Jérémie Galarneau over 7 years ago

Other cases include
  • 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.

Actions
Copy link

Also available in: Atom PDF