Docs/add sensitive data logging policy #14442
Open
Conversation
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
When service.telemetry.metrics.level is set to 'none', the collector should skip registering process metrics to avoid errors on platforms where gopsutil is not supported (such as AIX). This change conditionally registers process metrics only when the metrics level is not LevelNone, preventing the 'failed to register process metrics: not implemented yet' error on unsupported platforms. Fixes regression introduced in v0.136.0 where the check for metrics level was removed.
Similar to the resolution for pcommon.Value in previous changes, this update ensures consistent documentation across all pdata types by clarifying that calling functions on zero-initialized instances is invalid usage. Changes: - Updated template files (one_of_field.go, one_of_message_value.go) to generate improved comment wording - Updated pcommon/value.go comments manually - Updated all generated pdata files to use consistent wording: 'is invalid and will cause a panic' instead of 'will cause a panic' This makes it clearer that using zero-initialized instances is not just dangerous but explicitly invalid usage, improving API documentation clarity.
Fixes open-telemetry#14326 mdatagen was generating invalid Go code for histogram metrics by using NumberDataPoint API methods (SetDoubleValue, ValueType) on HistogramDataPoint types, causing compilation errors. Changes: Update metrics.go.tmpl to use HistogramDataPoint API for histogram metrics with dp.SetCount(1) and dp.SetSum(val). Update metrics_test.go.tmpl to assert dp.Count() and dp.Sum() for histograms. Add system.cpu.utilization histogram to samplescraper metadata for validation.
6bb1997 to
3182b70
Compare
Author
|
Hey there , I will highly appreciate a review from the reviewers and update with any follow ups and changes if required . |
Member
|
Please keep your PRs atomic, without unrelated things within them. |
Author
|
Yeaah , Thanks for the update, will be maintaining the last pr with good atomicity.
Cheers.
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Damien Mathieu ***@***.***>
Sent: Monday, January 19, 2026 1:56:57 PM
To: open-telemetry/opentelemetry-collector ***@***.***>
Cc: Arunodoy Banerjee ***@***.***>; Author ***@***.***>
Subject: Re: [open-telemetry/opentelemetry-collector] Docs/add sensitive data logging policy (PR #14442)
[https://avatars.githubusercontent.com/u/9347?s=20&v=4]dmathieu left a comment (open-telemetry/opentelemetry-collector#14442)<#14442 (comment)>
Please keep your PRs atomic, without unrelated things within them.
—
Reply to this email directly, view it on GitHub<#14442 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BOEIQ3YZ4BHJC6IC5J4U4W34HSINDAVCNFSM6AAAAACSAXNXGSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONRXGA3DAMBUGU>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
Addresses #14431
Establishes formal security guidelines for logging to prevent exposure of sensitive telemetry data at Info/Warn/Error levels.
Added
docs/security/logging.mdwith policy rules:documentation aspect of #14431. Code changes to existing processors (in the contrib repository) will be handled in a separate PR.