feat: (observability) add spans for BatchTransaction and Table #2115
Conversation
product-auto-label
bot
added
size: m
|
@odeke-em I don't see any tests for these spans. |
surbhigarg92
changed the title
odeke-em
force-pushed
the
trace-instrument-BatchTransaction+Table
branch
from
e74c73e
to
ea6d7f2
Compare
product-auto-label
bot
added
size: l
|
Hey @surbhigarg92 I hadn't uploaded some of them as I created this PR early morning at around 3AM before bed and in interludes. I've added comprehensive tests, please take a look. |
odeke-em
force-pushed
the
trace-instrument-BatchTransaction+Table
branch
from
ea6d7f2
to
38708a8
Compare
| @@ -285,6 +286,7 @@ export class Snapshot extends EventEmitter { | |||
| queryOptions?: IQueryOptions; | |||
| resourceHeader_: {[k: string]: string}; | |||
| requestOptions?: Pick<IRequestOptions, 'transactionTag'>; | |||
| observabilityOptions?: ObservabilityOptions; | |||
There was a problem hiding this comment.
observabilityOptions should be injected by customers from SpannerOptions which should set this property. Do you plan to do that in separate PR ?
I would recommend to add that in the same PR, so that we can test batch-transaction and mutation flow end to end
There was a problem hiding this comment.
I shall have it plumbed in progressively as we get there. The reason being that this PR is bound to balloon if I add it straight from the top inside new Spanner({observabilityOptions: opts}). Just the way for each part I have been adding it in and testing.
| 1, | ||
| 'Exactly 1 span should have been exported' | ||
| ); | ||
| assert.strictEqual( |
There was a problem hiding this comment.
Why did we remove this check from here ?
There was a problem hiding this comment.
In the testing environment, when ran isolated, the checks pass but when ran as a whole this test flakes here and there, a potential problem with OpenTelemetry. Besides, the point of the code was to ensure that the parent span actually has the required annotations which we do have and now it is very well cut out just for that.
odeke-em
force-pushed
the
trace-instrument-BatchTransaction+Table
branch
3 times, most recently
from
db71593
to
7357d35
Compare
odeke-em
force-pushed
the
trace-instrument-BatchTransaction+Table
branch
from
7357d35
to
23032f9
Compare
| @@ -1367,34 +1352,12 @@ describe('SessionPool', () => { | |||
| }); | |||
|
|
|||
| describe('trace annotations on active span', () => { | |||
There was a problem hiding this comment.
maybe for separate PR. But It will be good to extract these tests in observability-test folder
This change is part of a series of changes to add OpenTelemetry traces, focused on BatchTransaction and Table. While here, made the tests for sessionPool spans much more precise to avoid flakes. Updates googleapis#2079 Built from PR googleapis#2087 Updates googleapis#2114
odeke-em
force-pushed
the
trace-instrument-BatchTransaction+Table
branch
from
23032f9
to
6adf870
Compare
surbhigarg92
added
kokoro:run
gcf-owl-bot
bot
removed
the
owlbot:run
yoshi-kokoro
removed
the
kokoro:run
surbhigarg92
added
the
automerge
gcf-merge-on-green
bot
removed
the
automerge
This change is part of a series of changes to add
OpenTelemetry traces, focused on BatchTransaction and Table.
While here, made the tests for sessionPool spans much more precise to avoid flakes.
Updates #2079
Built from PR #2087
Updates #2114