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

[WIP] Add lintprocessor #126

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

[WIP] Add lintprocessor #126

wants to merge 1 commit into from

Conversation

ymtdzzz
Copy link
Owner

@ymtdzzz ymtdzzz commented Aug 7, 2024

Add lintprocessor to otel-tui. This processor is powered by otel-lint (WIP) and checks whether the received signals adhere to semantic conventions.
Currenlty, if there are any issues, it pushes lint.* attributes to it.

image

@ymtdzzz ymtdzzz self-assigned this Aug 7, 2024
@ymtdzzz ymtdzzz force-pushed the feature/lintprocessor branch from a958d50 to 893f993 Compare August 7, 2024 13:40
@codefromthecrypt
Copy link

looks neat. I wonder if we shouldn't add a synthetic attribute for the semantic conventions version we are testing against? The version of the SDK and the version tested could be different (e.g. go.opentelemetry.io/otel/semconv)

@@ -68,15 +69,15 @@ service:
pipelines:
traces:
receivers: [otlp]
processors: []
processors: [lint]

Choose a reason for hiding this comment

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

maybe make a flag for this as when you are developing a new semver, it may be clutter to see incompatabilities. I don't mind if it is on by default.

Choose a reason for hiding this comment

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

I would love to one day have a choice like semver=1.27.0 (vs one before that) because it takes a month or two for some changes to break free. We don't need to take action here now though. Just a thought

@ymtdzzz ymtdzzz changed the title Add lintprocessor [WIP] Add lintprocessor Aug 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants