Merge pull request #167 from MovieStoreGuy/msg/add-ninja-section-1

Adding ninja section as expands to help keep with the flow of content

Author: rcastley

content/en/conf/opentelemetry-collector/1-installation.md

@@ -14,6 +14,112 @@ Obtain the `.deb` package for your platform from the [OpenTelemetry Collector Co
 wget https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.75.0/otelcol-contrib_0.75.0_linux_amd64.deb
 ```
 
+{{%expand "🥷 Ninja: Build your own collector using _Open Telemetry Collector Builder (ocb)_"%}}
+For this part we will require the following installed on your system:
+
+- Golang (latest version)
+- ocb installed
+  - Most recent from the [project releases](https://github.com/open-telemetry/opentelemetry-collector/releases)
+  - Install using go by `go install go.opentelemetry.io/collector/cmd/builder@latest`
+- (Optional) Docker
+
+## Why build your own collector?
+
+The default distrobutions of the collector (core and contrib) either container too much or too little in what they have to offer.
+It is also not advised to run the contrib collector in your production environments due to the amount of components installed
+which more than likely are not needed by your deployment.
+
+## Benefits of building your own collector?
+
+When creating your own collector binaries, (commonly referred to as distrobutions), means you build what you need.
+The benefits of this are:
+
+1. Small binaries sizes
+1. Can use existing go scanners for vulnerabilites 
+1. Include internal components that can tie in with your organisation
+
+## Considerations for building your own collector?
+
+Now, this would not be a 🥷 ninja zone if it didn't come with some draw backs:
+
+1. Go experience is recommended if not required
+1. No splunk support
+1. Responsibiliy of distrobution and lifecycle management
+
+It is important to note that project is working towards stability but it does not mean
+changes made will not break your workflow. The team at Splunk provide increased support
+and a higher level of stability so they can provide a curated experience helping you
+with your deployment needs.
+
+## The Ninja Zone
+
+Once you have all the required tools installed to get started, you will need to create a
+new file named `otelcol-builder.yaml` and we will follow this directory structure:
+
+```
+.
+└── otelcol-builder.yaml
+```
+
+Once we have the file created, we need to add a list of components for it to install with some additional metadata.
+For this example, we are going to create a builder manifest that will install only the components we need for the introduction config:
+```yaml
+dist:
+  name: otelcol-ninja
+  description: A custom build of the Open Telemetry Collector
+  output_path: ./dist
+
+extensions:
+- gomod: go.opentelemetry.io/collector/extension/ballastextension v0.75.0
+- gomod: go.opentelemetry.io/collector/extension/zpagesextension  v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/httpforwarder v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/extension/healthcheckextension v0.75.0
+
+exporters:
+- gomod: go.opentelemetry.io/collector/exporter/loggingexporter v0.75.0
+- gomod: go.opentelemetry.io/collector/exporter/otlpexporter v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/splunkhecexporter v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/exporter/signalfxexporter v0.75.0
+- gomod:  github.com/open-telemetry/opentelemetry-collector-contrib/exporter/sapmexporter v0.75.0
+
+processors:
+- gomod: go.opentelemetry.io/collector/processor/batchprocessor v0.75.0
+- gomod: go.opentelemetry.io/collector/processor/memorylimiterprocessor v0.75.0
+
+receivers:
+- gomod: go.opentelemetry.io/collector/receiver/otlpreceiver v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/hostmetricsreceiver v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/jaegerreceiver v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/prometheusreceiver v0.75.0
+- gomod: github.com/open-telemetry/opentelemetry-collector-contrib/receiver/zipkinreceiver v0.75.0
+```
+
+Once the yaml file has been updated for the _ocb_, then run the following command:
+
+```shell
+> ocb --config=otelcol-builder.yaml
+```
+
+Which leave you with the following directory structure:
+
+```
+├── dist
+│   ├── components.go
+│   ├── components_test.go
+│   ├── go.mod
+│   ├── go.sum
+│   ├── main.go
+│   ├── main_others.go
+│   ├── main_windows.go
+│   └── otelcol-ninja
+└── otelcol-builder.yaml
+```
+
+### References:
+
+1. https://opentelemetry.io/docs/collector/custom-collector/
+{{% /expand%}}
+
 ## 2. Installing the OpenTelemetry Collector Contrib distribution
 
 Install the `.deb` package using `dpkg`. Not we are installing as root. Take a look at the Output tab in the box below to see what the exmple output of a successful install will look like:
@@ -163,4 +269,4 @@ Splunk does provide its own, fully supported, distribution of the OpenTelemetry
 
 - The Splunk Distribution of the OpenTelemetry Collector is production tested; it is in use by a number of customers in their production environments.
 - Customers that use our distribution can receive direct help from official Splunk support within SLA's.
-- Customers can use or migrate to the Splunk Distribution of the OpenTelemetry Collector without worrying about future breaking changes to its core configuration experience for metrics and traces collection (OpenTelemetry logs collection configuration is in beta). There may be breaking changes to the Collector's own metrics.
+- Customers can use or migrate to the Splunk Distribution of the OpenTelemetry Collector without worrying about future breaking changes to its core configuration experience for metrics and traces collection (OpenTelemetry logs collection configuration is in beta). There may be breaking changes to the Collector's own metrics.

content/en/conf/opentelemetry-collector/_index.md

@@ -10,6 +10,8 @@ alwaysopen: false
 
 Adopting OpenTelemetry within your organisation can bring issues such as dealing with metric naming changes, rollout, and where to start. In this workshop, we will be focusing on using the OpenTelemetry collector and starting with the fundamentals of configuring the receivers, processors, and exporters ready to use with Splunk Cloud. The journey will take attendees from novices to being able to start adding custom components to help solve for their business observability needs for their distributed platform.
 
+Throughout the workshop there will be **🥷 Ninja** sections that will be more hands on and go into further technical detail that you can explore within the workshop or in your own time. Please note that the content in these sections may go out of date due to the frequent development being made to the Open Telemetry project. Links will be provided in the event details are out of sync, please let us know if you spot something that needs updating.
+
 ### Target Audience
 
 This talk is for developers and system administrators who are interested in learning more about architecture and deployment of the OpenTelemetry Collector.