Keeping it short, sweet, and all about the content our community has shared this past week:
to all our new members this week. We would love to meet you in the Welcome Thread. Stop by to say "hello" 😊
👉 If you're new here and would like some suggestions for people to follow who share your interests, we welcome you to share a bit about what you're working on and what you're like to learn and share!
- @avital_trifsik keeps the content flowing for @memphis_dev with a summary of ETL's past, present, and future,
- @eyalestrin got a little theoretical (in all the good ways) about connection models in this post,
- @eriklz followed up last week's comparison post with a sorta-Part Two post, this time just on Pulumi (kinda-Part One is here),
- @lob_dev is back with one of their excellent retro posts, this time using HTTP keep-alive to reduce waste and improve performance,
- - @jmarhee shared a note for resolving a state error when creating a Glusterfs deployment
- and @argonaut continues their ongoing contributions to the optimization conversation with this post on reducing your Kubernetes bill.
- @alvaradodaniel3 dropped a couple of juicy links in the latest round-up post](https://community.ops.io/newrelic/new-relic-technical-blogs-and-updates-of-october-2022-2935), including one on New Relic's handy Terraform integration, as well as an update post that includes a guide to Jenkins with OpenTelemetry integration,
- the PagerDuty Team invite you to watch their webinar Evolve to Resolve: Fewer Incidents, Faster Response,
- and @haviv kicked off a new series on operational excellence.
👉 Let me and the community know by commenting below. I'll be checking back with you next week to see how it went!