-
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
[Page Feedback]: Please add full configuration details for setting up internal telemetry #6044
Comments
Hi @srimandarbha, thanks for your feedback! Could you provide more information on the configuration details you need? The page you mentioned includes snippets to enable collection of each signal (metrics, logs, and traces). Please let us know what is missing. Thanks. |
Hi Tiffany
I was actually looking to include attributes for telemetry data ,so data
sent from node to collector is further parsed and routed to a specific
bucket on influxdb like hostmetric bucket or internal telemetry bucket.
With the details provided I can understand only the pull or push mechanism
but I was looking for complete configuration details to customize the
telemetry configuration. Apologies if it is already published somewhere
else but I was not able to find.
Thanks
SD
…On Thu, 23 Jan 2025, 23:49 Tiffany Hrabusa, ***@***.***> wrote:
Hi @srimandarbha <https://github.com/srimandarbha>, thanks for your
feedback!
Could you provide more information on the configuration details you need?
The page you mentioned includes snippets to enable collection of each
signal (metrics, logs, and traces). Please let us know what is missing.
Thanks.
—
Reply to this email directly, view it on GitHub
<#6044 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKXOLVQAD7A7V3IXVZINBD2MEXBRAVCNFSM6AAAAABVW5KNNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJQGYZDSNBQGA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for the details, @srimandarbha. It sounds like you might want to process the telemetry, so I'll recommend you check the Processors section of the docs, which has links out to the code repositories where the processor documentation lives. I'm also going to tag the @open-telemetry/collector-approvers to see if they have guidance that should be added to the website docs about processing internal telemetry. Lastly, you might want to ask for guidance on your specific use case in the #otel-collector channel of CNCF Slack. Thanks. |
Thanks Tiffany, I'll check it out!
Regards
SD
…On Sat, 25 Jan 2025, 03:17 Tiffany Hrabusa, ***@***.***> wrote:
Thanks for the details, @srimandarbha <https://github.com/srimandarbha>.
It sounds like you might want to process the telemetry, so I'll recommend
you check the Processors
<https://opentelemetry.io/docs/collector/configuration/#processors>
section of the docs, which has links out to the code repositories where the
processor documentation lives.
I'm also going to tag the @open-telemetry/collector-approvers
<https://github.com/orgs/open-telemetry/teams/collector-approvers> to see
if they have guidance that should be added to the website docs about
processing internal telemetry.
Lastly, you might want to ask for guidance on your specific use case in
the #otel-collector <https://cloud-native.slack.com/archives/C01N6P7KR6W>
channel of CNCF Slack <https://slack.cncf.io/>. Thanks.
—
Reply to this email directly, view it on GitHub
<#6044 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABKXOLSPDZRXOBNPBNVPVO32MKYFLAVCNFSM6AAAAABVW5KNNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJTGQZTEOBYGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
URL
https://opentelemetry.io/docs/collector/internal-telemetry/
Description
Please add full configuration details for setting up internal telemetry
The text was updated successfully, but these errors were encountered: