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

kyma.resource.status.state metric gets filtered by namespace filter #1784

Open
a-thaler opened this issue Jan 23, 2025 · 1 comment
Open
Labels
area/metrics MetricPipeline

Comments

@a-thaler
Copy link
Collaborator

a-thaler commented Jan 23, 2025

Description
I have a MetricPipeline like that:

spec:
  input:
    otlp:
      namespaces:
        include:
        - cap
    runtime:
      enabled: true
      namespaces:
        include:
        - cap
        - observability

The pipeline exports the health metric "kyma.resource.status.conditions" but not "kyma.resource.status.state". The missing metric is namespace specific (kyma-system) and most probably gets blindly filtered out by the otlp input namespace selector.

Expected result

The metric is always emmitted

@a-thaler a-thaler added the area/metrics MetricPipeline label Jan 23, 2025
@shorim
Copy link
Contributor

shorim commented Jan 24, 2025

The reason for this bug is probably because we forgot to update the otlpInputSource() function to also exclude the scope metric.InstrumentationScopeKyma in the returned expression.

This otlpInputSource() function is used when creating the config for the namepace-filter processor https://github.com/kyma-project/telemetry-manager/blob/main/internal/otelcollector/config/metric/gateway/config_builder.go#L187-L190

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/metrics MetricPipeline
Projects
None yet
Development

No branches or pull requests

2 participants