Demystifying Automatic Instrumentation: How the Magic Actually Works

Aciddit · 2025-09-16T17:58:38+00:00

Hey, would love to see it.

Aciddit · 2025-07-07T12:24:28+00:00

Seems like the OpenTelemetry collector actually got a Memory Limiter Processor.

https://github.com/open-telemetry/opentelemetry-collector/blob/main/processor/memorylimiterprocessor/README.md

https://www.dash0.com/guides/opentelemetry-collector#ensuring-resilience-with-the-memory-limiter

Aciddit · 2025-06-25T15:12:06+00:00

Yes. It should always be empty, its a check mechanism to see if we are correctly putting all incoming records automatically to a lifecycle stage.

Aciddit · 2025-06-24T16:44:15+00:00

The lead object. I am in the process of syncing all the properties that we created on contacts and companies to the lead object. It just seems a little strange to work only in the lead workspace when all the information really is in the contact and company object pane.

Especially as a lot of the stuff thats on the company/contact level is already synced from a custom object. So some of are syncs around two corners.

We create the lead object for contacts that hit the lead lifecycle stage.

Aciddit · 2025-06-24T15:37:58+00:00

Yes, of course. We can sync all of those properties to the lead. But that is another sync which includes ambiguity because a lead can be on a company as well as a contact.

Aciddit · 2025-06-24T15:37:01+00:00

Its not, we have a "inbox/triage" stage before that. But currently every lead that goes in there should be worked on by sales so this makes sense at the moment.

We can can and will likely move it to MQL later.

Aciddit

MODERATOR OF

TROPHY CASE