Rashmi
Rashmi
I have a stack trace of NPE happening at logstash end (not at jaeger collector). ```java could not process event: undefined method `each' for nil:NilClass {:script_path=>"/etc/logstash/conf.d/tags_flatten.rb", :class=>"NoMethodError", :backtrace=>["/etc/logstash/conf.d/tags_flatten.rb:36:in `filter'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-filter-ruby-3.1.7/lib/logstash/filters/ruby/script/context.rb:55:in...
This rescued me from a possible unproductive day. Since Java 8 corretto also has the -Xshare issues, kind of in a fix for sometime.
This line https://github.com/opendistro-for-elasticsearch/index-management/blob/v1.12.0.0/src/main/kotlin/com/amazon/opendistroforelasticsearch/indexmanagement/rollup/util/RollupUtils.kt#L246 should be changed to `state.sums = 0L; state.counts = 0L;` Ref: https://www.elastic.co/guide/en/elasticsearch/painless/7.10/painless-literals.html#integer-literals Ref: https://github.com/elastic/elasticsearch/issues/27199 All the aggs which shows wrong value for `avg` assumes `sum` as **2147483647**...
@laurit I don't see any auto instrumentation being added in the contrib repo for java packages/frameworks. Can you share any guide on what type of instrumentation goes to which repo(either...
@trask The extensions are working out pretty neat 🎉 . Thanks for that. One question though, Sampler's `shouldSample`only works with the following data to set the sampling decision. 1. parentContext...
Thanks @trask. That was really helpful. Yes. https://github.com/open-telemetry/opentelemetry-java/issues/3963#issuecomment-988460277 is also my exact use case. Wanted to achieve the same thing to push all errors irrespective of the sampling decision. Do...
You could refer this sample which is more specific to your needs. https://github.com/freshdesk/fresh-samples/blob/master/c-sharp_samples/CreateTicketWithAttachment.cs
Can you raise a ticket regarding this to support.freshdesk.com attaching your script? Your issues will be addressed appropriately there.
I have a PR ready to be submitted along the same lines as how logstash has been handling this.