-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Configuration #3929
Comments
@oliver-sturrock what page are you talking about, can you provide a link? |
Sorry - that would have been useful info... This page: https://opentelemetry.io/docs/collector/configuration/ I did find the file in /etc/otelcol/, but it took some searching. |
Mmm, yes, we should clarify where you'll generally find (or need to place) a config file. |
As a minor, related point: I created this issue by clicking on the "Create documentation issue" link within the documentation. I assumed (wrongly) that it would automatically provide you the context/page link when I did that. Probably others will make the same assumption.
Thanks,
Oliver.
…________________________________
From: Phillip Carter ***@***.***>
Sent: Friday, February 2, 2024 11:02 AM
To: open-telemetry/opentelemetry.io ***@***.***>
Cc: Oliver Sturrock ***@***.***>; Mention ***@***.***>
Subject: Re: [open-telemetry/opentelemetry.io] Configuration (Issue #3929)
You don't often get email from ***@***.*** Learn why this is important<https://aka.ms/LearnAboutSenderIdentification>
Mmm, yes, we should clarify where you'll generally find (or need to place) a config file.
—
Reply to this email directly, view it on GitHub<#3929 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BCUTPH5EFLX33TN4JDZRZA3YRUZ2VAVCNFSM6AAAAABCWDANRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGUYDIOBTGU>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Thanks for calling this out, GitHub allows to send some properties with a new issue link, maybe that can be added to those links, cc @chalin |
Let's track that via: |
This page goes into a lot of detail about the content of the configuration file, but never states what the configuration file is called or where it is located.
The text was updated successfully, but these errors were encountered: