Skip to content

Add more information in traces from GstTracer #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

thiblahute
Copy link
Contributor

  • Add pad name in traces

  • Add pad chain infos

  • tracer: Factor out a SpanBuilder struct to log different objects
    It is useful in the logs to know the query/message/event that are being
    handled so we log them.

  • tracer: Log elements state change and messages on the bus %

@@ -91,6 +91,22 @@ fn state_desc(state: gstreamer::ffi::GstState) -> &'static str {
}
}

fn query_name(query: &gstreamer::QueryRef) -> &'static str {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not use the proper bindings API for this but instead go via FFI?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We do not expose that API yet? The only reference I found was in our fmt::Debug implementation which is clearly not what I want here. Should we add it?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems useful to have, yes

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is fine to keep this open and rebase later on. I don't consider open PRs to be a maintenance burden on repos with as low traffic as this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants