Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: Milian Wolff via lttng-dev <lttng-dev@lists.lttng.org>
To: "lttng-dev@lists.lttng.org" <lttng-dev@lists.lttng.org>
Cc: Bala Gundeboina <Bala.Gundeboina@kpit.com>
Subject: Re: [lttng-dev] Discarded events
Date: Tue, 15 Aug 2023 07:24:34 +0200	[thread overview]
Message-ID: <2693785.mvXUDI8C0e@agathemoarbauer> (raw)
In-Reply-To: <MA0PR01MB6987563FB945A5A4C90312EE8516A@MA0PR01MB6987.INDPRD01.PROD.OUTLOOK.COM>

On Sonntag, 13. August 2023 16:58:17 CEST Bala Gundeboina via lttng-dev wrote:
> Hi,
> 
> I am Using LTTng in my project , I am recording a kernel session for long
> duration (eg more than 15minutes) I am enabling all the events for
> recording but some events discarding after stopping the session, if i run
> more than 5 minutes only some events are discarding. I have tried to change
> in the .ltttngrc file also to increase buffer-size.

While not directly related to your question, I strongly encourage you to 
review the list of events and only enable those that are actually required for 
the specific issue you are investigating. Some kernel events are _extremely_ 
high frequency but have often no practical use for many (at least in my 
experience and for my own purposes). Examples for the latter are esp. the 
kmalloc tracepoints.

> lttng destroy
> Destroying session `my-kernel-session`...
> Session `my-kernel-session` destroyed
> Warning: 94424667 events were discarded, please refer to the documentation
> on channel configuration
> 
> actually when i am running below command i am getting below warning i am
> thinking this is the issue because sometimes this warning is not coming
> that i didn't seen discarded events.  how to overcome this problem can you
> provide some detailed lttng-sessiond --daemonize
> Warning: Failed to produce a random seed using getrandom(), falling back to
> pseudo-random device seed generation which will block until its pool is
> initialized: Failed to get true random data using getre
> 
> Thanks & Regards
> Bala Gundeboina
> This message contains information that may be privileged or confidential and
> is the property of the KPIT Technologies Ltd. It is intended only for the
> person to whom it is addressed. If you are not the intended recipient, you
> are not authorized to read, print, retain copy, disseminate, distribute, or
> use this message or any part thereof. If you receive this message in error,
> please notify the sender immediately and delete all copies of this message.
> KPIT Technologies Ltd. does not accept any liability for virus infected
> mails.


-- 
Milian Wolff | milian.wolff@kdab.com | Senior Software Engineer
KDAB (Deutschland) GmbH, a KDAB Group company
Tel: +49-30-521325470
KDAB - The Qt, C++ and OpenGL Experts

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

  parent reply	other threads:[~2023-08-15  5:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-13 14:58 Bala Gundeboina via lttng-dev
2023-08-14 18:25 ` Erica Bugden via lttng-dev
2023-08-15  5:24 ` Milian Wolff via lttng-dev [this message]
2023-08-23 20:03   ` Erica Bugden 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=2693785.mvXUDI8C0e@agathemoarbauer \
    --to=lttng-dev@lists.lttng.org \
    --cc=Bala.Gundeboina@kpit.com \
    --cc=milian.wolff@kdab.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox