Skip to content

feat(telemetryrouter): Onboarding TelemetryRouter#1425

Open
ozanichkovsky wants to merge 11 commits into
stackitcloud:mainfrom
ozanichkovsky:feature/telemetryrouter
Open

feat(telemetryrouter): Onboarding TelemetryRouter#1425
ozanichkovsky wants to merge 11 commits into
stackitcloud:mainfrom
ozanichkovsky:feature/telemetryrouter

Conversation

@ozanichkovsky
Copy link
Copy Markdown

Description

Telemetry Router resources and datasource

Checklist

  • Issue was linked above
  • Code format was applied: make fmt
  • Examples were added / adjusted (see examples/ directory)
  • Docs are up-to-date: make generate-docs (will be checked by CI)
  • Unit tests got implemented or updated
  • Acceptance tests got implemented or updated (see e.g. here)
  • Unit tests are passing: make test (will be checked by CI)
  • No linter issues: make lint (will be checked by CI)

@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 5, 2026

This PR was marked as stale after 7 days of inactivity and will be closed after another 7 days of further inactivity. If this PR should be kept open, just add a comment, remove the stale label or push new commits to it.

@github-actions github-actions Bot added the Stale PR is marked as stale due to inactivity. label May 5, 2026
@github-actions github-actions Bot removed the Stale PR is marked as stale due to inactivity. label May 6, 2026
@ozanichkovsky ozanichkovsky changed the title TelemetryRouter resources and datasources feat(telemetryrouter): Onboarding TelemetryRouter May 11, 2026
Comment thread stackit/internal/services/telemetryrouter/instance/resource.go Outdated
"description": "The description of the TelemetryRouter instance",
"filter": "The TelemetryRouter global filter settings",
"filter.attributes": "The TelemetryRouter global filter attributes",
"filter.attributes.key": "The TelemetryRouter global filter attribute key",
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

nitpick: we generally use _ instead of .

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

I actually saw . being used to distinguish between a name like "instance_id" and layers like "query_parameters.name" in other resource descriptions.

Comment thread stackit/internal/services/telemetryrouter/instance/resource.go Outdated
Comment thread stackit/internal/services/telemetryrouter/instance/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/instance/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/instance/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/instance/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/datasource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource.go Outdated
Comment thread stackit/internal/services/telemetryrouter/destination/datasource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/destination/datasource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/destination/datasource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/accesstoken/resource_test.go Outdated
Comment thread stackit/internal/services/telemetryrouter/destination/resource_test.go Outdated
"config_filter_matcher": config.StringVariable("="),
"config_filter_value0": config.StringVariable("value1"),
"config_filter_value1": config.StringVariable("value2"),
"config_opentelemetry_bearer_token": config.StringVariable("eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.KMUFsIDTnFmyG3nMiGM6H9FNFUROf3wh7SmqJp-QV30"),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

You should not use hard coded token like that. This wont work.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Destination represents an external destination logs are sent to. So it is a value, which a service user provides, not something that is generated by us.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

The only possibility I probably see is to use another instance as a destination with a token created for that instance. Should it be done that way?

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.

3 participants