Daniel Gomez Blanco

Thanks! Let me know if you need any more info

Hi there! We are currently running onto this issue as well. When the fix is allocated, will it be backported to 2.x? I know 3.x was released a few days...

Thanks @shiva-bandari, are there any docs on any limitations that perhaps we're not aware on NRQL used in drop rules? The following queries: ``` FROM Log SELECT * WHERE service.name...

Also, probably worth pointing out that the query that @aravind-bigfish had in the original post: ``` SELECT * FROM Log, LogExtendedRecord WHERE message LIKE '%value not found%' AND newrelic.logs.customEventType IS...

As @SelinErkan said, this worked, thanks! Perhaps something to follow up on separately because the NRQL console did not seem to like the query with `r`. Possibly nothing relate to...

Never mind, found the original issue. The query above ``` FROM Log SELECT * WHERE service.name = 'my-service' AND message RLIKE r'.*([a-zA-Z0-9_+&*-]+(?:\\.[a-zA-Z0-9_+&*-]+)*@(?:[a-zA-Z0-9-]+\\.)+[a-zA-Z]{2,}).*' ``` Would not work in the NRQL console...

Also running `0.18.2` and running into the same issue. After reading the docs, I would expect Atlantis to run the plan with the changes on the branch merged on top...

I'm hitting a similar issue. It does not result in forced replacement of notification channels, and instead gets ignored (unless changes are made to the notification channel) but it does...

What is the expected behaviour for incoming requests containing a trace context when the `batch` processor is used in a pipeline? As with the `k8sattributes` processor (which uses `Context`), I...

https://github.com/open-telemetry/opentelemetry-collector/blob/bb193a24d0a968027ad48c397899ae3688165756/obsreport/obsreport_exporter.go#L102 would mean that it picks up the current context. I assume this will not have an active span context after the `batch` processor so a new trace is started?