Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add example folder with common values.yaml scenarios #138

Closed
TylerHelmuth opened this issue Mar 4, 2022 · 3 comments · Fixed by #156
Closed

Add example folder with common values.yaml scenarios #138

TylerHelmuth opened this issue Mar 4, 2022 · 3 comments · Fixed by #156
Labels
chart:collector Issue related to opentelemetry-collector helm chart

Comments

@TylerHelmuth
Copy link
Member

It would be nice to have some example values.yaml for common scenarios customers might have. Some scenarios could be:

  • agent only configuration
  • standalone only configuration
  • agent and standalone
  • Traces only
  • Metrics only
  • Logs only
  • Common receivers (hostmetrics?)
  • Common processors (resourceprocessor or k8sattributeprocessor?)
  • Proxy configuration

Could be worth combining certain examples so we don't have too many values.yaml to maintain on breaking changes.

@dmitryax dmitryax added the chart:collector Issue related to opentelemetry-collector helm chart label Mar 4, 2022
@TylerHelmuth
Copy link
Member Author

Working on this

@TylerHelmuth
Copy link
Member Author

I think this is blocked by #90. I wanted to create an agent example with only the metrics pipeline but can't overwrite the default config so that trace and logs are excluded.

@TylerHelmuth
Copy link
Member Author

TylerHelmuth commented Mar 21, 2022

Narrowing the scope of this to only

  • agent only configuration
  • standalone only configuration
  • agent and standalone

while we work towards #91

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chart:collector Issue related to opentelemetry-collector helm chart
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants