Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cassandra driver instrumentation #763

Merged
merged 9 commits into from
Jul 3, 2020

Conversation

mladens
Copy link
Contributor

@mladens mladens commented Apr 7, 2020

Merging cassandra driver instrumentation from kamon-io/kamon-cassandra/pull/6

@eugenemiretsky
Copy link
Contributor

Is there a plan to merge this?

@dispalt
Copy link
Contributor

dispalt commented May 19, 2020

Im interested too!

@osbornk
Copy link

osbornk commented Jun 8, 2020

What is the status of this? We would love to use this feature.

@lustefaniak
Copy link
Contributor

Current java-driver is 4.6.1, maybe it would be a good idea to make it more obvious from artifact name that this is for older Cassandra driver?

@ivantopo
Copy link
Contributor

I didn't get the chance to look into the actual code behind the new driver yet, only high level review of the APIs and documentation.

The plan I have so far for this PR is to:

  • Merge the PR with support for 3.x driver only. Support for 4.x should come soon after.
  • Remove the "cluster" tag. It was removed from the 4.x driver and wasn't even accurate on 3.x.
  • Rename mentions of "host" to "node". The word node aligns much better with the language on the cassandra documentation.
  • Reduce the number of generated Spans. Out of the box, the instrumentation is generating two spans for every executed query: one for the query and one for the actual round trip to cassandra. It makes sense because there might be more than one round trip if a query needs to be retried or speculated on, but we are still getting a fuckton of useless Spans out of the box:

image

I see a few options for reducing the number of Spans:

  • Turn all the executions/retries into marks in the span. This would allow to keep track of all round trips, while still keeping a single span for the query.
  • Have a setting to enable/disable tracking of executions/retries.
  • Both?

I'll be working on this in the next few days, feedback is welcome!

@ivantopo
Copy link
Contributor

I just applied the changes I mentioned above. Went for a setting to disable tracking of executions (for reducing the number of Spans).

Changes were pushed to this branch in case anyone wants to take a look!

@ivantopo ivantopo merged commit 8200d5b into kamon-io:master Jul 3, 2020
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.

6 participants