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

[receiver/gitlab] add tracing via webhook skeleton #36838

Merged

Conversation

niwoerner
Copy link
Contributor

Description

This PR adds the structure and trace skeleton for a new and already accepted Gitlabreceiver. (thanks @atoulme for sponsoring this!)

The Gitlabreceiver aligns very closely with the Githubreceiver and this PR mostly mirrors the change from this PR: #36632

I'm working together with @adrielp on building out the Gitlabreceiver. More PRs to introduce metrics and actual tracing functionality are about to follow with subsequent PRs.

Link to tracking issue

#35207

Testing

Added basic tests and built the component to test that the health check endpoint, when tracing is enabled, operates correctly.

Documentation

Docs how to configure the Gitlabreceiver via webhooks have been added. While the Gitlabreceiver can be configured after this PR, it will not actually do anything since it is under development and just the skeleton PR.

@niwoerner niwoerner marked this pull request as draft December 18, 2024 19:04
@niwoerner niwoerner marked this pull request as ready for review December 20, 2024 11:06
}

// Simple healthcheck endpoint.
func (gtr *gitlabTracesReceiver) handleHealthCheck(w http.ResponseWriter, _ *http.Request) {
Copy link
Contributor

Choose a reason for hiding this comment

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

Good idea to read the request so that the http connection can be reused. Not urgent to do this pr

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That's a good catch, thank you! I will handle this in one of the subsequent PRs

@atoulme atoulme added the Accepted Component New component has been sponsored label Jan 8, 2025
@atoulme atoulme added the ready to merge Code review completed; ready to merge by maintainers label Jan 8, 2025
@andrzej-stencel andrzej-stencel merged commit 778d8f7 into open-telemetry:main Jan 13, 2025
163 checks passed
@github-actions github-actions bot added this to the next release milestone Jan 13, 2025
TylerHelmuth added a commit to TylerHelmuth/opentelemetry-collector-contrib that referenced this pull request Jan 14, 2025
TylerHelmuth added a commit to TylerHelmuth/opentelemetry-collector-contrib that referenced this pull request Jan 14, 2025
@TylerHelmuth TylerHelmuth mentioned this pull request Jan 14, 2025
codeboten pushed a commit that referenced this pull request Jan 14, 2025
Fix lint issue caused by
#36912

This reverts commit
778d8f7.

@adrielp @niwoerner I can't explain why, but it seems that after
#36838
the extension integration tests never complete. You can see in
https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/workflows/build-and-test.yml?query=branch%3Amain
that we haven't got an integration test suite to pass since merging the
new receiver. Reverting to unblock CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Accepted Component New component has been sponsored ready to merge Code review completed; ready to merge by maintainers reports/distributions/contrib.yaml
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants