Skip to content

Conversation

@JonathanWamsley
Copy link
Contributor

@JonathanWamsley JonathanWamsley commented Aug 3, 2022

This PR adds the enhanced otel mongodb metrics

@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 3, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 3, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 4, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 4, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 4, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 4, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 5, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 5, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 8, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 8, 2022
@JonathanWamsley JonathanWamsley added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 19, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 19, 2022
@JonathanWamsley JonathanWamsley marked this pull request as ready for review August 19, 2022 15:10
Copy link
Contributor

@ridwanmsharif ridwanmsharif left a comment

Choose a reason for hiding this comment

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

I don't see the receiver update yet, can you link the PR that brought it in?

monitored_resource: gce_instance
labels:
database: .*
- type: workload.googleapis.com/mongodb.extent.count
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see this metric in the scope doc, does it need to be added there?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, this should not be in this enhancements PR. It is in the scope doc but got left out of the original implementation. extent.count can only be used for mongodb version <= 4.2 and if the storage engine is MMAPv1. The default storage engine as of starting with 3.2 is the Wired Tiger. Updated.

kind: CUMULATIVE
monitored_resource: gce_instance
labels:
operation: .*
Copy link
Contributor

Choose a reason for hiding this comment

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

This can be more strict right? (insert | query | update | delete | getmore | command) is what the scope doc says

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Updated

Copy link
Contributor

@ridwanmsharif ridwanmsharif left a comment

Choose a reason for hiding this comment

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

The test changes look good to me. Has the update to the mongo otel receiver been brought in yet? I see that its not in this PR, can you link the PR that brought it in?

@ridwanmsharif ridwanmsharif added the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 22, 2022
@stackdriver-instrumentation-release stackdriver-instrumentation-release removed the kokoro:force-run Forces kokoro to run integration tests on a CL label Aug 22, 2022
@JonathanWamsley
Copy link
Contributor Author

Sure, mongodb enhancements got added in when the operations collector upgraded to 0.57.2. The Otel release v0.57.2 with this issue and this otel pr. I also rebuilt the docker image and tested on a vm to confirm that I am receiving the newest metrics.

@JonathanWamsley
Copy link
Contributor Author

I noticed the operations collector just got updated with go 1.18 update. So I can updated submodule opentelemetry-operations-collector to that 1.18. I ran a test pr with kokoro on latest otel version to confirm there were no new breaking changes being introduced.

@cpheps
Copy link
Contributor

cpheps commented Aug 23, 2022

@JonathanWamsley

I noticed the operations collector just got updated with GoogleCloudPlatform/opentelemetry-operations-collector#113. So I can updated submodule opentelemetry-operations-collector to that 1.18.

I would advise not doing this for this current PR as it's not necessary. The postgres updates @schmikei is working on will require an operations collector update that will pull in the 1.18 update. @ridwanmsharif is this ok with you?

@ridwanmsharif
Copy link
Contributor

Yup agreed with @cpheps, merging this as in now. Thanks for the explanation

@ridwanmsharif ridwanmsharif merged commit 978a047 into GoogleCloudPlatform:master Aug 23, 2022
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.

4 participants