alex boten

@kcqon oh yeah! I only saw you that one time going in the opposite direction on the escalator :D will post an update once the #rejekts talk is up

@codeboten not surprised we didn't get to catch up much during #KubeCon , but I'm surprised I missed your #Rejekts2023 observability talk. One of the things I wanted to discuss is auto-instrumention in OpenTelemetry

After working on OpenTelemetry for 3.5 years, it was wonderful to finally meet contributors I’ve only met virtually before

@SonjaChevre @SoormallyAhmet I love this slide

@TheKaterTot Did Bear just commit some changes to prod that were intended for dev only???

SO RELAXED

Bear is actually feeling very relaxed and she's not taking questions

@cziclix @CanalystModels @TegusHQ Congrats! 🎉

I'm very appreciative of all the people @CanalystModels who built such an incredible product which lead to an incredible business and ultimately today's news. Thank you! Bringing fundamental models to @TegusHQ sets us up to be a force in the capital markets. Watch this space...

@ahidalgosre @1z0b31 @argablarg Did you settle on bash?

@o11yfest @LightstepHQ Thanks for having me! It was a blast :)

It was truly a treat to have @codeboten speak on Day 1, co-host a bookclub on Day 2, and run a @LightstepHQ workshop on Day 4!

@paulsbruce @o11yfest @mipsytipsy Talk about timing!!

On the final day of @o11yfest, pre-order of @codeboten's new #observability book arrived! Bonus foreword by @mipsytipsy! What a self-treat to me! cloudnativeobservability.com

@austinlparker Are there discounts if you query between certain times like after 6pm? Long distance calling styles

@TheKaterTot Bear is the highlight of my timeline

Bear is a good girl

@goanonthego @o11yfest @newrelic Troubleshooting gRPC is often a pain... the GRPC_TRACE and GRPC_VERBOSITY environment variables are super useful github.com/grpc/grpc/blob…

Coming up on #o11yfest LIVE stream: Reese Lee on "Where the heck are my spans?!" ===> buff.ly/3kOtsZF

@salmonwithad I’m sure if you tweet your banking details someone will gladly help…

@ahidalgosre Why stop there?

@austinlparker @tedsuo I was just going over some old tweets and found this gem twitter.com/codeboten/stat…

@rakyll Once in a lifetime opportunity!!

Achievement unlocked: Got that SDE II opportunity recruitment mail!

@ahidalgosre kube ctrl

@Aneurysm9 @tveastman @mjingle @kentquirk @honeycombio Yes, sorry I just re-read the thread. There is a 1.11.1 release planned for Python to address the issue.

@codeboten @tveastman @mjingle @kentquirk @honeycombio That issue assumes a collector is involved. Direct OTLP export to a vendor will still be impacted until wire compatibility is restored unless the vendor has also implemented the InstrumentationLibrary to InstrumentationScope conversion.

@argparse There is! The community page (#special-interest-groups" target="_blank" rel="nofollow noopener">github.com/open-telemetry…) has all the details to join the slack channel. There is also a SIG meeting happening today at 9am pacific time. Check the otel calendar for the zoom details

@codeboten hey there thanks for your work on opentelemetry. I stumbled upon this issue > github.com/open-telemetry… (I opened it). Which might just be me doing something stupid. I was wondering if there is slack or otherwise open forum where you can ask about stuff like that.

@Aneurysm9 @tveastman @mjingle @kentquirk @honeycombio Yeah. This issue was raised here: github.com/open-telemetry…

@tveastman @mjingle @kentquirk @honeycombio Pretty sure this is due to github.com/open-telemetry… being merged and included in the 1.11.0 release but github.com/open-telemetry… not. The former updates the OTLP proto to 0.15 which moves message fields in a way that's wire compatible iff the latter is also done. @codeboten

@bwplotka @go_perf @goinggodotnet

@go_perf @goinggodotnet Glad someone asked... 🤗oreilly.com/library/view/e…

#golang Developer Survey 2021 Results go.dev/blog/survey202…