Skip to content
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

Trace Liveview in Phoenix instrumentation #198

Merged

Conversation

derekkraan
Copy link
Contributor

Supercedes #108 since I don't have access to the source repo anymore.

I've removed the parent span that lives for the duration of the liveview process, and instead added thread.name with the pid, so that different events in the same liveview can be correlated to each other (per suggestion from @connorlay).

This sidesteps the whole discussion on monitoring spans. If we decide later that we want an overarching span, then that can always be added in at that point in time.

@derekkraan derekkraan changed the title Add the ability to trace Liveviews to the Phoenix instrumentation Trace Liveview in Phoenix instrumentation Aug 23, 2023
@tsloughter
Copy link
Member

thread.name actually needs to be removed to merge this. That needs to be a general attribute added in the SDK and updated in the spec. I can handle that. If you remove it from here I can merge this.

@derekkraan derekkraan force-pushed the opentelemetry_phoenix_liveview branch from af468c7 to 6e40de6 Compare August 23, 2023 09:56
@derekkraan
Copy link
Contributor Author

derekkraan commented Aug 23, 2023

@tsloughter Removed thread.name from the PR as requested. Do you mean that thread.name will be added to all spans from within the SDK?

@tsloughter
Copy link
Member

@derekkraan correct. tho needs to be configurable I assume since some SaaS charge for attributes.

@tsloughter
Copy link
Member

See open-telemetry/opentelemetry-erlang#550

It has thread.name as the scheduler id because I originally thought it would be that, but I came around to think pid was better.

@tsloughter
Copy link
Member

Looks like some formatting issues causing failure.

@derekkraan
Copy link
Contributor Author

derekkraan commented Aug 23, 2023

I formatted with Elixir 1.15. I have seen the formatter checks fail between versions of Elixir, are you sure it's not that? (ie the formatter changes sometimes between versions of Elixir)

@tsloughter
Copy link
Member

Ah.

We need to change the formatting job to only run on 1 version.

@tsloughter tsloughter merged commit 79aae55 into open-telemetry:main Aug 23, 2023
18 of 24 checks passed
@tsloughter
Copy link
Member

Opened #199 to track that

@bryannaegele
Copy link
Collaborator

There are no tests for this functionality. Can you get those created in another PR @derekkraan?

@tsloughter
Copy link
Member

Yup, need those before any release.

@derekkraan derekkraan deleted the opentelemetry_phoenix_liveview branch August 28, 2023 11:23
@connorlay
Copy link

Hey folks, I'm interested in getting this work published and am happy to help out with tests if needed @derekkraan @tsloughter 🙂

@derekkraan
Copy link
Contributor Author

I haven't been able to find time yet, so from my side it would be much appreciated!

@skbolton
Copy link

skbolton commented Jan 2, 2024

Yup, need those before any release.

Now that this the PR for tests has been merged can a new release be made with liveview tracing?

@tielur
Copy link

tielur commented Feb 2, 2024

Yup, need those before any release.

I'd love to see a release with this included as well, I'm excited to try out telemetry with liveview

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

Successfully merging this pull request may close these issues.

6 participants