Skip to content

[receiver/gitlab] add tracing functionality #39123

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

Merged

Conversation

niwoerner
Copy link
Contributor

@niwoerner niwoerner commented Apr 2, 2025

Description

This PR adds tracing functonality for the gitlabreceiver. It's only possible to create deterministic Trace/SpanIDs once a pipeline is finished. Correlation with manual instrumented jobs during pipeline runtime is not possible because of limitations in Gitlab. More details can be found here

(I would like to become an OpenTelemetry member to be a codeowner of the gitlabreceiver - would someone be willing to sponsor the membership for me? - Thank you! :) )

Link to tracking issue

#35207

Testing

Added unit tests and performed manual testing

Documentation

Updated README how to use the receiver

@niwoerner niwoerner requested review from atoulme and a team as code owners April 2, 2025 15:30
@github-actions github-actions bot requested a review from adrielp April 2, 2025 15:31
@niwoerner niwoerner marked this pull request as draft April 2, 2025 15:42
@niwoerner niwoerner marked this pull request as ready for review April 5, 2025 12:28
@github-actions github-actions bot removed the Stale label May 13, 2025
@niwoerner
Copy link
Contributor Author

I implemented the code changes based on @adrielp and mine latest discussions. Additionally, I raised a proposal/request on GitLab to potentially enable the GitLab receiver to rely on deterministic IDs, which could also be generated during pipeline execution.

More details can be found here

@niwoerner niwoerner marked this pull request as ready for review May 14, 2025 20:53
@atoulme
Copy link
Contributor

atoulme commented May 15, 2025

@adrielp please review.

@songy23 songy23 merged commit 88ba312 into open-telemetry:main May 19, 2025
175 checks passed
@github-actions github-actions bot added this to the next release milestone May 19, 2025
dragonlord93 pushed a commit to dragonlord93/opentelemetry-collector-contrib that referenced this pull request May 23, 2025
#### Description
This PR adds tracing functonality for the gitlabreceiver. It's only
possible to create deterministic Trace/SpanIDs once a pipeline is
finished. Correlation with manual instrumented jobs during pipeline
runtime is not possible because of limitations in Gitlab. More details
can be found
[here](open-telemetry/semantic-conventions#1749 (comment))

(I would like to become an OpenTelemetry member to be a codeowner of the
gitlabreceiver - would someone be willing to sponsor the membership for
me? - Thank you! :) )

#### Link to tracking issue
 open-telemetry#35207

#### Testing
Added unit tests and performed manual testing

#### Documentation
Updated README how to use the receiver
dd-jasminesun pushed a commit to DataDog/opentelemetry-collector-contrib that referenced this pull request Jun 23, 2025
#### Description
This PR adds tracing functonality for the gitlabreceiver. It's only
possible to create deterministic Trace/SpanIDs once a pipeline is
finished. Correlation with manual instrumented jobs during pipeline
runtime is not possible because of limitations in Gitlab. More details
can be found
[here](open-telemetry/semantic-conventions#1749 (comment))

(I would like to become an OpenTelemetry member to be a codeowner of the
gitlabreceiver - would someone be willing to sponsor the membership for
me? - Thank you! :) )

#### Link to tracking issue
 open-telemetry#35207

#### Testing
Added unit tests and performed manual testing

#### Documentation
Updated README how to use the receiver
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