STAC-22435 TODOs for restructuring some more

Author: rb3ckers

setup/otel/getting-started/getting-started-other.md

@@ -10,6 +10,11 @@ To get started we'll setup monitoring with these components:
 * The Open Telemetry collector running on the same VM
 * SUSE Observability or SUSE Cloud Observability
 
+TODO: Replace with inline basic collector config (also possible to run a single collector for multiple applications on different nodes), that includes references to URL and link to ingress docs for self-hosted
+TODO: Also inline collector setup for Kubernetes that uses a minimal config? Link to separate collector config page to explain the details and customizations (next todo)
+TODO: Create separate page on more detailed config (the existing collector.md minus the Kubernetes installation guide, with separate sections for customizations like sampling, host metrics)
+TODO: Also inlince the collector setup for AWS getting started
+
 DIAGRAM...
 
 ## Install the Open Telemetry collector
@@ -20,11 +25,11 @@ It is strongly adviced to install the collector to centralize all the tasks ment
 
 First we'll install the collector. It handles several tasks:
 
-* Enrich collected data with host attributes
 * Sampling of traces
 * Forward the data to SUSE Observability, including authentication using the API key
 * Retries sending data when there are a connection problems
 
+
 To configure the collector you'll need the OTLP or OTLP over HTTP endpoint of SUSE Observability to be securely accessible. The SUSE Observability Helm chart allows you to set that up via an ingress configuration. If you didn't do that during installation now is the time to [add that ingress configuration](/setup/install-stackstate/kubernetes_openshift/ingress.md#configure-ingress-rule-for-open-telemetry). If you're using SUSE Cloud Observability these are the applicable URLs:
 * https://otel-<your-suse-observabillity>.app.stackstate.com - For the OTLP protocol
 * https://otel-http-<your-suse-observabillity>.app.stackstate.com - For OTLP over HTTP