Jose Montoya

Found the issue to be with `es.tags-as-fields.all: true` since the SpansToDependencyLinks is using the constant tag keys for server spans. Thinking about solving this on the elasticsearch json deserializer since...

Hey guys, is there any work around for this atm? I'm trying to follow the thread of TLS related changes and options. Is there any skip-tls JAVA_OPT or something that...

@aleksandrovpa we're just composing the cron job manually in order to bootstrap the trust store through an init container. You can check this out https://github.com/MS3Inc/tavros/blob/main/tests/integration/targets/playbooks/provision_playbook/example.com/platform/jaeger/default/cronjob-spark-dependencies.yaml#L39

Thanks @jstoiko :) It's been a long while since I opened this, but I think you confirmed a bug since `{}` is incorrectly accepted while it doesn't have the required...

@jstoiko sorry to summon you back to this, but I'm reconsidering using RAML vs OpenAPI for some use cases (because I prefer RAML's data type system) but this specific question...

Did you happen to solve this? Seeing the same issue with gitea, and wondering if it might be related.

> How filebeat knows where to collect logs? We've been trying to figure this out as well. We're seeing filebeat output this on debug, for our auto discovered non-default_config'd nginx...

To answer my own question... I decided to dig into the code and found this https://github.com/elastic/beats/blob/a4e5a73af1df3020b5d50d5a198963bd66e5c370/filebeat/autodiscover/builder/hints/logs.go, which led me to trying this ``` autodiscover: providers: - type: kubernetes node: ${NODE_NAME}...

So the issue is between regular grizzly-http-server and mule-4-http-server rules. The grizzly setup that the http-service uses is not supported out of the box by the regular grizzly rule so...

Sure. We already have the release branch commit trigger the CI. The issue we're having is that some releases may still be done manually and may not use the plugin,...