-
Notifications
You must be signed in to change notification settings - Fork 271
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
#229 Add OpenTelemetry Collector Server Auth Extensions to Receivers #2203
#229 Add OpenTelemetry Collector Server Auth Extensions to Receivers #2203
Conversation
@grafana/grafana-alloy-maintainers I am going to hold back on reviewing the doc input until after a technical code review has been completed. There are some questions I have about the way things are phrased in the docs that may be resolved with the code review. |
Thanks for taking a look! Happy to clarify once the code review is complete. |
The latest commits should fix the issue with the race condition in auth_basic.go. I have also addressed the outstanding comments on the PR. |
@@ -10,6 +10,8 @@ title: otelcol.auth.oauth2 | |||
|
|||
`otelcol.auth.oauth2` exposes a `handler` that can be used by other `otelcol` components to authenticate requests using OAuth 2.0. | |||
|
|||
This extension only supports client authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this an extension to a component? Or do we mean component
here?
docs/sources/reference/components/otelcol/otelcol.auth.sigv4.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/otelcol/otelcol.extension.jaeger_remote_sampling.md
Outdated
Show resolved
Hide resolved
docs/sources/reference/components/otelcol/otelcol.extension.jaeger_remote_sampling.md
Outdated
Show resolved
Hide resolved
@clayton-cornell I have made the requested changes to the docs. Based on your previous feedback I also slightly modified each receiver's docs. Let me know if you would like any more changes. |
3913159
to
4665aaf
Compare
…re/add_auth_to_otlp_receiver
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some really minor tweaks to the docs and they look OK to me.
{{< admonition type="note" >}} | ||
Not all OpenTelemetry Collector authentication plugins support receiver authentication. | ||
Refer to the [documentation](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/otelcol/) for each `otelcol.auth.*` component to determine its compatibility. | ||
{{< /admonition >}} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{{< admonition type="note" >}} | |
Not all OpenTelemetry Collector authentication plugins support receiver authentication. | |
Refer to the [documentation](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/otelcol/) for each `otelcol.auth.*` component to determine its compatibility. | |
{{< /admonition >}} | |
{{< admonition type="note" >}} | |
Not all OpenTelemetry Collector authentication plugins support receiver authentication. | |
Refer to the [documentation](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/otelcol/) for each `otelcol.auth.*` component to determine its compatibility. | |
{{< /admonition >}} |
Removing extra space
@@ -11,7 +11,7 @@ title: otelcol.auth.basic | |||
`otelcol.auth.basic` exposes a `handler` that can be used by other `otelcol` | |||
components to authenticate requests using basic authentication. | |||
|
|||
This extension supports both server and client authentication. | |||
This `component` supports both server and client authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This `component` supports both server and client authentication. | |
This component supports both server and client authentication. |
Ooops, my fault. I used the inline code syntax to emphasize in the previous comment.
@@ -11,7 +11,7 @@ title: otelcol.auth.bearer | |||
`otelcol.auth.bearer` exposes a `handler` that can be used by other `otelcol` | |||
components to authenticate requests using bearer token authentication. | |||
|
|||
This extension supports both server and client authentication. | |||
This `component` supports both server and client authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This `component` supports both server and client authentication. | |
This component supports both server and client authentication. |
@@ -11,7 +11,7 @@ title: otelcol.auth.headers | |||
`otelcol.auth.headers` exposes a `handler` that can be used by other `otelcol` | |||
components to authenticate requests using custom headers. | |||
|
|||
This extension only supports client authentication. | |||
This `component` only supports client authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This `component` only supports client authentication. | |
This component only supports client authentication. |
@@ -10,7 +10,7 @@ title: otelcol.auth.oauth2 | |||
|
|||
`otelcol.auth.oauth2` exposes a `handler` that can be used by other `otelcol` components to authenticate requests using OAuth 2.0. | |||
|
|||
This extension only supports client authentication. | |||
This `component` only supports client authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This `component` only supports client authentication. | |
This component only supports client authentication. |
@@ -12,7 +12,7 @@ title: otelcol.auth.sigv4 | |||
components to authenticate requests to AWS services using the AWS Signature Version 4 (SigV4) protocol. | |||
For more information about SigV4 see the AWS documentation about [Signing AWS API requests][]. | |||
|
|||
This extension only supports client authentication. | |||
This `component` only supports client authentication. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This `component` only supports client authentication. | |
This component only supports client authentication. |
Documentation changes have been implemented. However, the recent merge with the main branch seems to have caused a test failure. This pull request PR appears to be the culprit. The same test is also failing on the main branch. I wanted to flag this issue here to ensure the failure doesn't hinder the progress of this PR. |
@aidanleuck It's probably OK to ignore the failing test here. The @grafana/grafana-alloy-maintainers over to someone on the dev team for code review |
// authentication extensions to all of our components. | ||
// Auth is a binding to an otelcol.auth.* component extension which handles | ||
// authentication. | ||
Auth *auth.Handler `alloy:"auth,attr,optional"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should name this to a authentication
in both the var name and alloy name. This is so it doesnt overlap with authentication
. Same with the documentation.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think about renaming the var name to Authentication but keeping the alloy name as auth? That way when using client auth or server auth the field is consistent.
client auth looks like this. We can't easily change this without breaking the user interface.
otelcol.exporter.otlp "otlp"{
auth = <component>.handler
}
server auth would look like this if we changed auth to authentication.
otelcol.receiver.otlp "receiver"{
authentication = <component>.handler
}
As a user I like the consistency between it being auth for both exporters and receivers. Let me know what you think.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can live with that. Can you add a comment in the code saying why its that way?
} | ||
|
||
// Configure the authentication if args.Auth is set. | ||
var auth *otelconfigauth.Authentication | ||
var authz *otelconfigauth.Authentication |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Var name feels like authorization.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks good, minor nits on var naming and alloy configuration naming.
if err != nil { | ||
return err | ||
} else if ext != nil { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This merge conflict was already handled in this PR in the function createExtension() on line 388 of this file.
This is looking great. One last comment to add and I will merge. Likely will pull this into the RC candidate before release. |
Comments addressed! I also changed the var name for client blocks from Auth to Authentication for consistency. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm thank you for the PR!
* update changelog for rc (#2360) * update changelog for rc * update changelog for rc * update changelog for rc (#2361) * update version (#2362) * update changelog for rc (#2360) * update changelog for rc * update changelog for rc Signed-off-by: matt durham <[email protected]> * fix conversion * Fix changelog main (#2364) * update version * Fix changelog * update the image version to work with the given example (#2358) * docs: fixed kafka config example (#2359) Example shows `loki.source.kafka "local"` pointing to `loki.relabel.kafka.receiver`. This leads to no new label being added. Correct example should have the kafka source pointing directly to `loki.write.local.receiver` * feat(helm): add the ability to deploy extra manifest files (#2347) * feat(helm): add the ability to deploy extra manifest files * docs(helm): run helm-docs * ci(helm): add tests * Update wal queue tls (#2363) * add tls to wal * add alloy config * update version * Add support for TLS doc. * Add changelog. * fix import order * add support and doc for round robin. * fix conversion * Update docs/sources/reference/components/prometheus/prometheus.write.queue.md Co-authored-by: Clayton Cornell <[email protected]> * Add test * fix merge * Update internal/component/prometheus/write/queue/types.go Co-authored-by: William Dumont <[email protected]> --------- Co-authored-by: Clayton Cornell <[email protected]> Co-authored-by: William Dumont <[email protected]> * #229 Add OpenTelemetry Collector Server Auth Extensions to Receivers (#2203) * Work on adding auth so far * Cleanup * Made a ton of progress * Fix test fails? * Refactor * Add auth blocks to implementing extensions * Refactor to use feature flag * Comments * Cleanup * Spacing * Update docs * Update CHANGELOG * Last auth extension missing * We also need grpc auth * Fix opencensus docs * Fix extra comment * Update comment with findings * Properly fix merge conflict * Save file * Spelling error * That has been released now * Add auth support to influxdb receiver * Fix failing auth test/MAIL * Comment cleanup * MAIL for documentation * docs MAIL * MAIL * Move from Auth to Authentication * Update triton-go dependency to avoid embedded RSA key (#2380) * Fix examples for filter and transform processors (#2379) * fix examples filter and transform processors * remove unecessary docs about escaping strings and backticks * fix(loki.secretfilter): Fix partial masking for short secrets and support multiple allowlists per rule (#2320) * Fix partial masking bug and support new allowlist format * Add docs and changelog * Update docs * Add comments * Add comments * Minor docs update * Add more tests * Change criteria for partial redaction * Changes to partial masking rules * Fix comment location * Clarify usage of secret types * Clarify usage of secret types * Update docs/sources/reference/components/loki/loki.secretfilter.md Co-authored-by: Clayton Cornell <[email protected]> * Suggestions * Suggestions --------- Co-authored-by: Clayton Cornell <[email protected]> * Fix only run on fork guard (#2378) * Fix only run on fork guard The previous guard fails because `github.repository` resolves to the base repository on `pull_request` events. * Fix syntax * Fix relabel processed bug (#2394) * Fix issue where alloy_prometheus_relabel_metrics_processed was not being incremented. * Add unit tests * Update WAL to version that supports v2. (#2397) * Update WAL to version that supports v2. * Update WAL to version that supports v2. * Add samples check. * Clean up Alloy component docs (#2387) * First pass at cleanup, pretty tables, sort lists * Sort content, add badge * Fix link * Set link URL correctly * Still fxing link targets * One more tidy pass * database_observability: report health of component and collectors (#2392) Report unhealthy in case of errors when starting up the collectors or of any collector is stopped during operations. * update for rc.1 (#2401) * Update version. * fix version * fix version --------- Signed-off-by: matt durham <[email protected]> Co-authored-by: Adam ABICHOU <[email protected]> Co-authored-by: Jay Clifford <[email protected]> Co-authored-by: dbluxo <[email protected]> Co-authored-by: Clayton Cornell <[email protected]> Co-authored-by: William Dumont <[email protected]> Co-authored-by: Aidan Leuck <[email protected]> Co-authored-by: Sam DeHaan <[email protected]> Co-authored-by: Romain Gaillard <[email protected]> Co-authored-by: Jack Baldry <[email protected]> Co-authored-by: Cristian Greco <[email protected]>
PR Description
Adds server authentication support to
otelcol.receivers.*
that support the OpenTelemetry collector auth extension model. Some receivers are not wrappers of the collector so they are excluded from this PR.Receivers that now support server auth:
Which issue(s) this PR fixes
Fixes #229
Notes to the Reviewer
TestAuthServer in auth_basic_test.go is consistently failing due to a race condition in startup. Any ideas or potential solutions to this problem would be appreciated. The auth_basic plugin appears to function as expected when running from the binary.
User interface for client auth has not changed.
PR Checklist