Merge branch 'open-telemetry:main' into embrace-distro

Author: davidlawrencer

.gitmodules

@@ -23,7 +23,7 @@
 [submodule "content-modules/opamp-spec"]
 	path = content-modules/opamp-spec
 	url = https://github.com/open-telemetry/opamp-spec
-	opamp-pin = v0.9.0-2-g950df29
+	opamp-pin = v0.10.0
 [submodule "content-modules/opentelemetry-go"]
 	path = content-modules/opentelemetry-go
 	url = https://github.com/open-telemetry/opentelemetry-go

.htmltest.yml

@@ -8,6 +8,8 @@ CheckMailto: false
 TestFilesConcurrently: true
 IgnoreDirs:
   # DO NOT EDIT! IgnoreDirs list is auto-generated from markdown file front matter.
+  # 2024-11-03 The following entry is for `en` pages only. Other locales do
+  # not currently require it.
   - ^blog/(\d+/)?page/\d+
   # TODO drop next line after https://github.com/open-telemetry/opentelemetry.io/issues/5423 is fixed for ja pages:
   - ^ja/docs/concepts/instrumentation/libraries/

content-modules/opamp-spec

@@ -0,0 +1,9 @@
+---
+title: KubeCon North America 2024
+date: 2024-10-15
+expiryDate: 2024-11-15
+---
+
+<i class="fas fa-bullhorn"></i> Join us in Salt Lake City for
+[**KubeCon + CloudNativeCon North America 2024**](/blog/2024/kubecon-na/) ,
+November 12 - 15, 2024

content/en/announcements/kubecon-na-2024.md

@@ -0,0 +1,134 @@
+---
+title: Join us for OpenTelemetry Talks and Activities at KubeCon NA 2024
+linkTitle: KubeCon NA '24
+date: 2024-11-05
+# prettier-ignore
+cSpell:ignore: Arnell Ashok Chandrasekar Clario Contribfest Ekansh Grabner Haeussler Helmuth Jernigan Kalkanis Kats Kowall Kruthika Liudmila Mclean Molkova Novatec OTTL Prasanna Shivanshu Shrivastava simha Woerner
+author: '[Severin Neumann](https://github.com/svrnm) (Cisco)'
+---
+
+The OpenTelemetry project maintainers, members of the governance committee, and
+technical committee are thrilled to be at [KubeCon NA][] in Salt Lake City from November
+12 - 15, 2024.
+
+Read on to learn about all the things related OpenTelemetry during KubeCon.
+
+## OpenTelemetry Contribfest
+
+Join the OpenTelemetry maintainers for the
+[OpenTelemetry Contribfest](https://sched.co/1hoyF) to make the project better
+for everyone. You can choose between several opportunities to contribute, and
+you can count on maintainers from different project areas to help you on your
+first steps: documentation, Collector, Java, JS, Ruby, Python, .NET, and more.
+
+## KubeCon Talks and Maintainer Sessions
+
+- **[Jaeger: Distributed Tracing with Jaeger and OpenTelemetry | Project Lightning Talk](https://sched.co/1iW8S)**<br>
+  by Jaeger Maintainers<br> Tuesday November 12, 2024 9:59am - 10:04am MST
+- **[OpenTelemetry: OpenTelemetry in Five Minutes | Project Lightning Talk](https://sched.co/1iW8Y)**<br>
+  by OpenTelemetry Maintainers<br> Tuesday November 12, 2024 10:13am - 10:18am
+  MST
+- **[OpenTelemetry: The OpenTelemetry Hero’s Journey: Working with Open Source Observability | Project Lightning Talk](https://sched.co/1iW8e)**<br>
+  Tuesday November 12, 2024 10:27am - 10:32am MST
+- **[OpenTelemetry: The Future of Network Monitoring, eBPF for Low-Level Insights | Project Lightning Talk](https://sched.co/1iW8k)**<br>
+  Tuesday November 12, 2024 10:41am - 10:46am MST
+- **[Lightning Talk: Minimizing Data Loss Within the OpenTelemetry (OTel) Collector](https://sched.co/1i7kC)**<br>
+  by Alex Kats, Capital One<br> Tuesday November 12, 2024 6:05pm - 6:10pm MST
+- **[Optimizing LLM Performance in Kubernetes with OpenTelemetry](https://sched.co/1i7lA)**<br>
+  by Ashok Chandrasekar, Google & Liudmila Molkova, Microsoft<br> Wednesday
+  November 13, 2024 2:30pm - 3:05pm MST
+- **[Unifying Observability: Correlating Metrics, Traces, and Logs with Exemplars and OpenTelemetry](https://sched.co/1i7lJ)**<br>
+  by Kruthika Prasanna Simha & Charlie Le, Apple<br> Wednesday November 13, 2024
+  2:30pm - 3:05pm MST
+- **[OpenTelemetry Project Update](https://sched.co/1hovy)**<br> by Alolita
+  Sharma, Apple; Juraci Paixão Kröhling, Grafana Labs; Ted Young, ServiceNow;
+  Morgan Mclean, Splunk; Daniel Dyla, Dynatrace<br> Wednesday November 13, 2024
+  3:25pm - 4:00pm MST
+- **[Using OpenTelemetry for Deep Observability Within Messaging Queues](https://sched.co/1i7li)**<br>
+  by Shivanshu Raj Shrivastava & Ekansh Gupta, SigNoz<br> Wednesday November 13,
+  2024 3:25pm - 4:00pm MST
+- **[Distributed Tracing with Jaeger and OpenTelemetry](https://sched.co/1hoyb)**<br>
+  by Jonah Kowall, Independent & Pavol Loffay, Red Hat<br> Wednesday November
+  13, 2024 4:30pm - 5:05pm MST
+- **[Understanding How OpenTelemetry Network Uses eBPF for Network Observability](https://sched.co/1how7)**<br>
+  by Shivanshu Raj Shrivastava, SigNoz & Jonathan Perry, PerfPod<br> Wednesday
+  November 13, 2024 5:25pm - 6:00pm MST
+- **[The OTTL Cookbook: A Collection of Solutions to Common Problems](https://sched.co/1i7mZ)**<br>
+  by Tyler Helmuth, Honeycomb & Evan Bradley, Dynatrace<br> Wednesday November
+  13, 2024 5:25pm - 6:00pm MST
+- **[Lesson’s Learned Adopting OpenTelemetry at Scale](https://sched.co/1i7nC)**<br>
+  by Alex Arnell, Heroku / Salesforce<br> Thursday November 14, 2024 11:00am -
+  11:35am MST
+- **[How We Made OpenTelemetry Be Our Fitness Tracker for Your CI/CD Pipelines!](https://sched.co/1i7nM)**<br>
+  by Nicolas Woerner, Clario & Andreas Grabner, Dynatrace<br> Thursday November
+  14, 2024 11:00am - 11:35am MST
+- **[Low-Overhead, Zero-Instrumentation, Continuous Profiling for OpenTelemetry](https://sched.co/1i7nz)**<br>
+  by Christos Kalkanis, Elastic<br> Thursday November 14, 2024 2:30pm - 3:05pm
+  MST
+- **[Fluent Bit: Better Pipelines for Observability](https://sched.co/1hoxB)**<br>
+  by Eduardo Silva, Chronosphere<br> Thursday November 14, 2024 4:30pm - 5:05pm
+  MST
+- **[Mastering OpenTelemetry Collector Configuration](https://sched.co/1i7ot)**<br>
+  by Steve Flanders, Cisco<br> Thursday November 14, 2024 4:30pm - 5:05pm MST
+- **[Tutorial: OpenTelemetry Hands-on - Automatic and Manual Instrumentation for Java and Python Apps](https://sched.co/1i7pd)**<br>
+  by Matthias Haeussler, Novatec Consulting GmbH & Tiffany Jernigan,
+  Independent<br> Friday November 15, 2024 11:00am - 12:30pm MST
+- **[Contribfest: OpenTelemetry Contribfest](https://sched.co/1hoyF)**<br> by
+  OpenTelemetry Maintainers<br> Friday November 15, 2024 4:00pm - 5:30pm MST
+
+## Observability Day
+
+_[Observability Day][] fosters collaboration, discussion, and knowledge sharing of
+cloud-native observability projects_. This event will be held on November 12, 2024
+from 9am to 6pm. [Check the full schedule](https://colocatedeventsna2024.sched.com/overview/type/Observability+Day)
+to find your favorite talks about Observability and OpenTelemetry.
+
+> <i class="far fa-exclamation-triangle"></i> **IMPORTANT access note**: You
+> need an _in-person all-access_ pass for on-site access to **Observability
+> Day**. For details, see [KubeCon registration][]. If you have a virtual ticket,
+> you will be able to follow **Observability Day** through a live stream.
+
+## OpenTelemetry Observatory
+
+Drop by and say _"Hi!"_ at OpenTelemetry Observatory presented by Splunk in the
+Expo Hall. This will be a place for informal chats, meetups, and other
+discussions led by OpenTelemetry community members and maintainers.
+
+Note, that the Observatory may show up as "Splunk Activation Booth" on the event
+map.
+
+For the activity schedule, see the
+[OTel Observatory Schedule](https://docs.google.com/spreadsheets/d/1E23Dkz1B2us71BtlQq8oG4o_QFsTeLPeh-X2uVnlubg/edit?usp=sharing).
+Note that this schedule may be updated up until the day of the event, so check
+back for the latest!
+
+New for this year!
+
+- SIG Office Hours: Come meet the people behind the project, learn about their
+  work, ask questions, share feedback, or find out how to contribute.
+- Special Topic Discussions: Come learn about two of the hottest OTEPs right
+  now, Events and Entities!
+
+If you'd like to participate by leading a discussion, or if there is a
+discussion topic you're interested in, please reach out to the
+[OpenTelemetry End User SIG](https://cloud-native.slack.com/archives/C01RT3MSWGZ)
+to let us know, and we will see what we can do.
+
+You can help us improve the project by sharing your thoughts and feedback about
+your OpenTelemetry adoption, implementation, and usage.
+
+We will create action items from your comments as appropriate. Check
+[#otel-sig-end-user][] in CNCF's Slack instance for results and action item
+updates to come after KubeCon EU.
+
+Come join us to listen, learn, and get involved in OpenTelemetry.
+
+See you in Salt Lake City!
+
+[kubecon na]:
+  https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/
+[Observability Day]:
+  https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/co-located-events/observability-day/
+[kubecon registration]:
+  https://events.linuxfoundation.org/kubecon-cloudnativecon-north-america/register/
+[#otel-sig-end-user]: https://cloud-native.slack.com/archives/C01RT3MSWGZ

content/en/blog/2024/kubecon-na.md

@@ -1,9 +1,15 @@
 ---
 title: Blog
 menu: { main: { weight: 50 } }
-redirects: [{ from: '', to: '2024/ 301!' }]
+redirects:
+  # Every January, update the year number in the paths below
+  - { from: '', to: '2024/ 301!' }
+  # Workaround to https://github.com/open-telemetry/opentelemetry.io/issues/4440:
+  - { from: 'index.xml', to: '2024/index.xml 301!' }
 outputs: [HTML, RSS]
 htmltest:
   IgnoreDirs:
+    # 2024-11-03 The following entry is for `en` pages only. Other locales do
+    # not currently require it.
     - ^blog/(\d+/)?page/\d+
 ---

content/en/blog/_index.md

@@ -52,6 +52,11 @@ It is also easier to [setup a collector](quick-start) than you might think: the
 default OTLP exporters in each language assume a local collector endpoint, so if
 you launch a collector it will automatically start receiving telemetry.
 
+## Collector security
+
+Follow best practices to make sure your collectors are [hosted] and [configured]
+securely.
+
 ## Status and releases
 
 The **Collector** status is: [mixed][], since core Collector components
@@ -70,6 +75,8 @@ for more details.
 {{% docs/latest-release collector-releases /%}}
 
 [registry]: /ecosystem/registry/?language=collector
+[hosted]: /docs/security/hosting-best-practices/
+[configured]: /docs/security/config-best-practices/
 [mixed]: /docs/specs/otel/document-status/#mixed
 [stability levels]:
   https://github.com/open-telemetry/opentelemetry-collector#stability-levels

content/en/docs/collector/_index.md

@@ -14,7 +14,8 @@ the following content:
 
 - [Data collection concepts][dcc], to understand the repositories applicable to
   the OpenTelemetry Collector.
-- [Security guidance](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md)
+- [Security guidance for end users](/docs/security/config-best-practices/)
+- [Security guidance for component developers](https://github.com/open-telemetry/opentelemetry-collector/blob/main/docs/security-best-practices.md)
 
 ## Location {#location}
 

content/en/docs/collector/configuration.md

@@ -8,13 +8,16 @@ The OpenTelemetry Collector consists of a single binary which you can use in
 different ways, for different use cases. This section describes deployment
 patterns, their use cases along with pros and cons and best practices for
 collector configurations for cross-environment and multi-backend deployments.
+For deployment security considerations, see [Collector hosting best
+practices][security].
 
 ## Resources
 
 - KubeCon NA 2021 Talk on [OpenTelemetry Collector Deployment
   Patterns][y-patterns]
 - [Deployment Patterns][gh-patterns] accompanying the talk
 
+[security]: /docs/security/hosting-best-practices/
 [gh-patterns]:
   https://github.com/jpkrohling/opentelemetry-collector-deployment-patterns/
 [y-patterns]: https://www.youtube.com/watch?v=WhRrwSHDBFs

content/en/docs/collector/deployment/_index.md

@@ -4,7 +4,8 @@ description:
   Why and how to send signals to a single OTLP end-point and from there to
   backends
 weight: 3
-cSpell:ignore: hostnames loadbalancer loadbalancing
+# prettier-ignore
+cSpell:ignore: filelogreceiver hostmetricsreceiver hostnames loadbalancer loadbalancing resourcedetectionprocessor
 ---
 
 The gateway collector deployment pattern consists of applications (or other
@@ -198,6 +199,38 @@ The load-balancing exporter emits metrics including
 that you can use for health and performance monitoring of the OTLP endpoint
 collector.
 
+## Combined deployment of Collectors as agents and gateways
+
+Often a deployment of multiple OpenTelemetry collectors involves running both
+Collector as gateways and as [agents](/docs/collector/deployment/agent/).
+
+The following diagram shows an architecture for such a combined deployment:
+
+- We use the Collectors running in the agent deployment pattern (running on each
+  host, similar to Kubernetes daemonsets) to collect telemetry from services
+  running on the host and host telemetry, such as host metrics and scrap logs.
+- We use Collectors running in the gateway deployment pattern to process data,
+  such as filtering, sampling, and exporting to backends etc.
+
+![gateway](otel-gateway-arch.svg)
+
+This combined deployment pattern is necessary, when you use components in your
+Collector that either need to be unique per host or that consume information
+that is only available on the same host as the application is running:
+
+- Receivers like the
+  [`hostmetricsreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/hostmetricsreceiver)
+  or
+  [`filelogreceiver`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/filelogreceiver)
+  need to be unique per host instance. Running multiple instances of these
+  receivers will result in duplicated data.
+
+- Processors like the
+  [`resourcedetectionprocessor`](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/resourcedetectionprocessor)
+  are used to add information about the host, the collector and the application
+  are running on. Running them within a Collector on a remote machine will
+  result in incorrect data.
+
 ## Tradeoffs
 
 Pros: