Andreas Thaler

Results 28 issues of Andreas Thaler

**Description** The current logging setup is only configurable via installation overrides and restricts the user of changing the configuration dynamically at runtime without triggering the kyma upgrade procedure. Furthermore it...

Epic
area/logging

**Description** Setting the log level to "warn" as documented in [Log_level](https://github.com/fluent/fluent-bit-docs/blob/master/administration/configuring-fluent-bit/configuration-file.md) is not showing any effect, still "info" logs are printed **Expected Result** According to the [Log_Level](https://github.com/fluent/fluent-bit-docs/blob/master/administration/configuring-fluent-bit/configuration-file.md) documentation, the log...

**Description** When an installation fails (for different reasons like component readiness is timing out) it will be helpful to have a command to figure out basic investigation results like: -...

area/cli
area/ci

**Description** The current tracing solution is a simple in-cluster solution to get started quickly and get some insights in a fast way. It does not respect enough high availability aspects...

Epic
area/tracing

**Description** I created an APIRule on a subdomain which was already taken by a virtualservice resource. The resulting status of the APIRule was very understandable like that: ``` status: APIRuleStatus:...

kind/bug
area/api-gateway
lifecycle/stale

**Description** Following the new [Strategy](https://github.com/kyma-project/community/blob/main/concepts/observability-strategy/strategy.md), we will not be able to offer a Kiali component fullfilling enterprise-grade quality. With that, it should not be offered as a component which would...

area/service-mesh
Epic

**Description** Let's get started with the tracing journey by implementing the results of https://github.com/kyma-project/kyma/issues/11630. Again, the new collector setup should be fully managed by the existing telemetry-operator using a feature...

area/tracing

**Description** The current http output does not support custom headers, especially not for Authorization needs. That is a common feature used for integration with providers like for example https://www.axiom.co/docs/send-data/fluent-bit. However,...

area/logging

**Description** After the [Configurable Logging](https://github.com/kyma-project/kyma/issues/11236) feature is released for a while, the migration guide mentions that the old fluentbit installation will be removed from the logging chart with Kyma 2.8....

area/logging

**Description** When deploying a LogPipeline from time to time you can run into that decline of the resource: ``` {"log":"Failed calling webhook, failing closed validation.logpipelines.telemetry.kyma-project.io: failed calling webhook \"validation.logpipelines.telemetry.kyma-project.io\": failed...

kind/bug
area/logging