New component: Semantic Convention Checker Connector

[MadVikingGod]

The purpose and use-cases of the new component

The Semantic Convention Checker Connector can be used to monitor your streams of telemetry data for conformance with a semantic convention. This allows users to measure and monitor instrumentation quality of your system.

We could monitor all telemetry for the presence of project_id and enviornment to ensure that we can attribute the telemetry to the correct groups. We could also monitor to ensure that traces from http server produce the current http semantic convention

Example configuration for the component

scc:
  trace:
  - match: .*
    include:
    - project_id
    - environment
  - semantic_version: "https://opentelemetry.io/schemas/1.26.0"
    match: http.server.*
    groups:
    - trace.http.server
    ignore:
    # Errors are not always present
    - error.type
  metric:
  - match: .*
    include:
    - project_id
    - environment
  log:
  - match: .*
    include:
    - project_id
    - environment  

Telemetry data types supported

Traces, Metrics, Logs -> Logs
Metrics of the connector running

Is this a vendor-specific component?

• This is a vendor-specific component
• If this is a vendor-specific component, I am a member of the OpenTelemetry organization.
• If this is a vendor-specific component, I am proposing to contribute and support it as a representative of the vendor.

Code Owner(s)

@MadVikingGod

Sponsor (optional)

@codeboten

Additional context

Proof of concept work: https://github.com/MadVikingGod/otel-semconv-checker/tree/main/pkg/sccconnector

[codeboten]

I'm happy to sponsor this component. As per the discussion in the 03-July-2024 SIG call, it would be great to validate there's no overlap between this and the schema transform processor.

[dmitryax]

I'd suggest renaming it to validation connector. Otherwise, it's too easy to confuse with OTel Semantic Conventions.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.