Skip to content

[UTR Logging] Added gcp.use_legacy_mapping resource attribute to disable LogEntry.otlp field.#2250

Open
XuechunHou wants to merge 15 commits intomasterfrom
use-legacy-mapping
Open

[UTR Logging] Added gcp.use_legacy_mapping resource attribute to disable LogEntry.otlp field.#2250
XuechunHou wants to merge 15 commits intomasterfrom
use-legacy-mapping

Conversation

@XuechunHou
Copy link
Copy Markdown
Contributor

@XuechunHou XuechunHou commented Mar 30, 2026

Description

Issue b/491102815 was fixed recently. Added the gcp.use_legacy_mapping resource attribute to disable LogEntry.otlp population.

Related issue

b/491448977

How has this been tested?

Checklist:

  • Unit tests
    • Unit tests do not apply.
    • Unit tests have been added/modified and passed for this PR.
  • Integration tests
    • Integration tests do not apply.
    • Integration tests have been added/modified and passed for this PR.
  • Documentation
    • This PR introduces no user visible changes.
    • This PR introduces user visible changes and the corresponding documentation change has been made.
  • Minor version bump
    • This PR introduces no new features.
    • This PR introduces new features, and there is a separate PR to bump the minor version since the last release already.
    • This PR bumps the version.

@XuechunHou XuechunHou self-assigned this Mar 30, 2026
// all late entries flushed from a multiline parser after 1s.
"logs": {
otel.GCPProjectID("fake-project"),
otel.DisableOtlpRoundTrip(),
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does it make sense to have a testcase that enables the OtlpRoundTrip scenarion?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Currently, all logging receiver pipelines disable the OTLP round trip by default, including the otlp receiver. At least as part of the public preview, i dont think it's important to verify the 'on' scenario.

However, we do want to make sure that when otel.DisableOTLPRoundTrip() processor is set, LogEntry.otel field is unset by UTR. This can be done via an integration test and I already implemented it at: #2234

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants