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.

Sign up for GitHub

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

Jump to bottom

Enable libcnb tracing #768

Closed
edmorley opened this issue Jan 23, 2025 · 0 comments · Fixed by #779
Closed

Enable libcnb tracing #768

edmorley opened this issue Jan 23, 2025 · 0 comments · Fixed by #779
Assignees
@edmorley

Comments

@edmorley
Copy link
Member

edmorley commented Jan 23, 2025 •
edited
Loading

For parity with our other buildpacks, we should enable libcnb's trace feature.

See:

GUS-W-15148616.
edmorley added a commit that referenced this issue Feb 28, 2025
@edmorley
Enable libcnb tracing
f4eebeb 
This enables `libcnb`'s `trace` feature, which means traces, spans, and
events are written to OpenTelemetry export files on disk in the ephemeral
build container, which can then be read by the Heroku build system or
when debugging locally with Pack (so long as a suitable `--volume` mount
has been configured).

See:
heroku/libcnb.rs#723

Closes #768.
GUS-W-15148616.
@edmorley edmorley self-assigned this Feb 28, 2025
@edmorley edmorley mentioned this issue Feb 28, 2025
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@edmorley edmorley

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Enable libcnb tracing heroku/buildpacks-jvm
1 participant
@edmorley