chore: Cherry Pick OTel Engine New Components and Documentation#5487
Closed
blewis12 wants to merge 4 commits into
Closed
chore: Cherry Pick OTel Engine New Components and Documentation#5487blewis12 wants to merge 4 commits into
blewis12 wants to merge 4 commits into
Conversation
Part of #4722 This addresses a couple points of feedback in the first iteration: * This PR introduces a separate "Introduction" page, which has a high level explanation of the two engines, and outlines the motivation/benefits of the OTel Engine * This main page has a list of components, so far I can't find a way to automate this - but using a dropdown component I feel like the information is more approachable. I've also linked to the OCB manifest just in case folks want to look in more detail * I've included a "Getting Started" page which has concrete examples to get off the ground with the new engine. I've moved the examples away from the CLI docs page to deduplicate --------- Co-authored-by: Clayton Cornell <clayton.cornell@grafana.com> Co-authored-by: Clayton Cornell <131809008+clayton-cornell@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
) ### Brief description of Pull Request Adds missing components which are used in the OTel Collector k8s helm chart via presets (https://opentelemetry.io/docs/platforms/kubernetes/helm/collector/#presets). This should enable someone to use the alloy distro for monitoring k8s with OTel successfully. ### Notes to the Reviewer I also included the `prometheusreceiver` which isn't necessary for the k8s use case but seemed useful in general. --------- Co-authored-by: Bejal Lewis <164711649+blewis12@users.noreply.github.com>
…lector helm chart (#5473) Turns out that we cannot change the OTel Collector Helm Chart's args to prepend an otel subcommand. To allow using Alloy's OTel Engine with OTel ecosystem more broadly, we add an otelcol alias to Alloy's Docker image.
Contributor
|
💻 Deploy preview deleted (chore: Cherry Pick OTel Engine New Components and Documentation). |
Member
Author
|
It was decided this isn't necessary for an internal bug bash, and best that we stick to including only bug fixes/cve's in patches |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Brief description of Pull Request
I'd like to cherry-pick the following:
builtinassetsbuild tag toembedalloyuias the former conflicts with an underlying build tag in the otel prometheus receiver. This should not change any behaviorThe reason i'd like to cherry-pick this is so that v1.13.x can be properly used in the upcoming bug bash to test out the OTel Engine internally. This way folks can pull an official tagged version of Alloy, which will be included in our different installation flows and can be easily referenced in helm charts. This might not be necessary though since our next release is scheduled for around the time of the bug bash - gonna keep this in draft and either open it or close it based on a final decision