All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yitschak, Yehuda via lttng-dev" <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Subject: [lttng-dev] delay between trigger and action
Date: Tue, 23 May 2023 12:17:20 +0000	[thread overview]
Message-ID: <ef30ea91bb3c427e84c6677350bda6d7@amazon.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 2137 bytes --]

Hi everyone

I am experimenting with enabling trace for a specific iteration of a loop in my application.
I created 2 trace points at the start and end of the loop which log the iteration number.
the loop itself creates thousands of trace points. It runs for ~5ms.

on lttng side I created 2 triggers to start and stop my session in case the loop tracepoint registers a specific iteration number.
the triggers seem to work since there is another session entry created under the session folder but there are very few tracepoints.

is it possible that the delay between the event happening and the session trace starting causes loss of events ?
If yes, is there a way around this  ?

here is my setup :

#lttng-status
Recording session session: [inactive]
    Trace output: /home/user/lttng-traces/session-20230523-113537

=== Domain: User space ===

Buffering scheme: per-user

Tracked process attributes
  Virtual process IDs:  all
  Virtual user IDs:     all
  Virtual group IDs:    all

Channels:
-------------
- user-channel: [enabled]

    Attributes:
      Event-loss mode:  discard
      Sub-buffer size:  16777216 bytes
      Sub-buffer count: 128
      Switch timer:     inactive
      Read timer:       inactive
      Monitor timer:    1000000 us
      Blocking timeout: 0 us
      Trace file count: 1 per stream
      Trace file size:  unlimited
      Output mode:      mmap

    Statistics:
      Discarded events: 0

    Recording event rules:
      trace_events* (type: tracepoint) [enabled]
      loop* (type: tracepoint) [enabled]

#lttng list-triggers

- name: iter-start
  owner uid: 1000
  condition: event rule matches
    rule: loop:iteration (type: user tracepoint, filter: iter==2 && start == 1)
    errors: none
  actions:
    start session `session`
      errors: none
  errors: none
- name: iter-stop
  owner uid: 1000
  condition: event rule matches
    rule: loop:iteration (type: user tracepoint, filter: iter==2 && start == 0)
    errors: none
  actions:
    stop session `session`
      errors: none
  errors: none


Thanks

Yehuda

[-- Attachment #1.2: Type: text/html, Size: 6525 bytes --]

[-- Attachment #2: Type: text/plain, Size: 156 bytes --]

_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

             reply	other threads:[~2023-05-23 12:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-23 12:17 Yitschak, Yehuda via lttng-dev [this message]
2023-05-23 14:51 ` [lttng-dev] delay between trigger and action Jérémie Galarneau via lttng-dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ef30ea91bb3c427e84c6677350bda6d7@amazon.com \
    --to=lttng-dev@lists.lttng.org \
    --cc=yehuday@amazon.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.