TRACING-5814 | RHOSDT 3.9 Document google managed prometheus

[pavolloffay]

Version(s):

RHOSDT 3.9
OCP 4.12-4.21 (all supported OCP versions at the merge time)

Issue:

https://issues.redhat.com/browse/TRACING-5814

Link to docs preview:

QE review:

• QE has approved this change.

Additional information:

• GMP OTLP metrics ingestion user facing doc https://docs.google.com/document/d/1FCHI6Qwv5F522j2ajd6Nhoq8FRTPutoVYDMYgZqagcw/edit?tab=t.0
• https://docs.google.com/document/d/1-C2Fx9BV58t7iyEQhWItBzO_3vC3HAM0_5hEfYLCM4o/edit?tab=t.0
• sample https://github.com/GoogleCloudPlatform/opentelemetry-operator-sample/blob/main/recipes/host-and-kubelet-metrics/collector-config.yaml

OTELcol 0.142.0

https://github.com/open-telemetry/opentelemetry-collector-contrib/blob/main/CHANGELOG.md#-breaking-changes-

receiver/prometheus: Promote the receiver.prometheusreceiver.RemoveStartTimeAdjustment feature gate to stable and remove in-receiver metric start time adjustment in favor of the metricstarttime processor, including disabling the created-metric feature gate. (#44180) Previously, users could disable the RemoveStartTimeAdjustment feature gate to temporarily keep the legacy start time adjustment behavior in the Prometheus receiver. With this promotion to stable and bounded registration, that gate can no longer be disabled; the receiver will no longer set StartTime on metrics based on process_start_time_seconds, and users should migrate to the metricstarttime processor for equivalent functionality. This change also disables the receiver.prometheusreceiver.UseCreatedMetric feature gate, which previously used the <metric>_created series to derive start timestamps for counters, summaries, and histograms when scraping non OpenMetrics protocols. However, this does not mean that the _created series is always ignored: when using the OpenMetrics 1.0 protocol, Prometheus itself continues to interpret the _created series as the start timestamp, so only the receiver-side handling for other scrape protocols has been removed.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[pavolloffay]

/test all

[ocpdocs-previewbot]

🤖 Tue Dec 23 15:21:29 - Prow CI generated the docs preview:

https://104286--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/otel/otel-forwarding-telemetry-data.html

[openshift-ci]

@pavolloffay: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/validate-asciidoc	35a1024	link	true	/test validate-asciidoc

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.