[UTR Logging] New Integration Test that compares LogEntries from UTR vs Google cloud exporter - #2234
Draft
XuechunHou wants to merge 65 commits into
Draft
[UTR Logging] New Integration Test that compares LogEntries from UTR vs Google cloud exporter#2234XuechunHou wants to merge 65 commits into
XuechunHou wants to merge 65 commits into
Conversation
1. otlp_exporter + otlp_logging, the generated otel.yaml only has one logging pipeline with otlp receiver and otlp exporter. 2. otlp_exporter + otel_logging, the generated otel.yaml has all the logging pipeline using otlp exporter. 3. otlp_exporter + otlp_logging + otel_logging, the generated otel.yaml has all the logging pipelines using otlp exporter. 4. otlp_logging + otel_logging, the generated otel.yaml has all the logging pipelines using the google cloud exporter.
XuechunHou
changed the title
quentinmit
reviewed
Mar 12, 2026
| return plogotlp.NewGRPCClient(conn), nil | ||
| } | ||
|
|
||
| func entryToMap(entry *loggingpb.LogEntry) map[string]any { |
Member
There was a problem hiding this comment.
Why are you manually extracting the LogEntry proto here? That's going to interact poorly with int64 fields because you'll get them as the wrong type.
XuechunHou
force-pushed
the
compare-log-entries
branch
from
March 13, 2026 21:46
4208e77 to
323da2f
Compare
XuechunHou
force-pushed
the
compare-log-entries
branch
from
March 13, 2026 21:50
323da2f to
4d79afd
Compare
…o compare-log-entries
XuechunHou
force-pushed
the
compare-log-entries
branch
from
March 16, 2026 19:14
d5e1335 to
2de3c8b
Compare
XuechunHou
added
the
kokoro:force-run
stackdriver-instrumentation-release
removed
the
kokoro:force-run
…o compare-log-entries
…o compare-log-entries
…o compare-log-entries
Merged
9 tasks
…o compare-log-entries
|
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
|
Closed as inactive. Feel free to reopen if this PR is still being worked on. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Description
This PR includes an integration test that compares LogEntries from the telemetry endpoint, VS those from google cloud exporter, given the same input log.
[Update August 20, 2026] The test is failing on two things
LogEntry.traceasprojects/<projectName>/traces/<traceID>, whereas otlp endpoint populatesLogEntry.traceastraceIDonly. This is WAI.LogEntry.sourceLocation.function, but Ops Agent populatesgcp.source_location.function. This results infunctioninformation dropped in the finalLogEntryproto. - the otlp endpoint should be able to accommodate.functionin their implementation. Fixed by: cl/967990629Related issue
b/490113021
How has this been tested?
Checklist: