up2neck

@inge4pres Log entry was taken from APM Server logs (stdout, collected by GCP Loggins if it matters) Trace was taken from Elasticsearch itself. Our team, has 2 environments (both facing...

@inge4pres There are few additional steps on the top of default "APM" integration-provided ingest pipelines, we have, but all of them don't interact with `http.response.status_code` field, keeps it original.

@inge4pres One interesting thing, that we don't use any TBS configuration in our manifests - APM Server is deployed with ECK operator, including the following config customization only: ``` config:...

@inge4pres Got it, I will disable sampling and check the log and trace correlation.

@carsonip @inge4pres I collected some more examples of non-consistent logs and traces. Unfortunately, most of the payload either obfuscated or removed due to the company privacy policy. But even though,...

@carsonip Great news! Thank you for detailed explanation, it's very useful to understand some parts of APM Server and how them work.

@carsonip I got a though crossed my mind - may such behavior affect APM Server metrics? Cause it potentially may has worse outcomes for end-users, if metrics aren't relevant.

@1pkg Hi! Thank you, I'm looking forward to the next release.

> Could you please provide the manifests you are using, this would help me reproduce. Thanks! It's slightly sanitized from sensitive data: affinity, specific labels, but cross-resource refers are persisted...

My installation of Logseq on Mac is experiencing the same issue after upgrade to 0.10.12. After open the app, it immediately crashes.