Add instrumentation for Cassandra: github.com/gocql/gocql

[MrAlias]

https://github.com/gocql/gocql

Tasks

• code complete with tests passing
• Dockerfile with example app showing instrumentation
• documentation updated
• instrumentation added to the opentelemetry registry

Prior Art

• https://github.com/DataDog/dd-trace-go/tree/v1/contrib/gocql/gocql

[reggiemcdonald]

@MrAlias could I give this a try?

[reggiemcdonald]

After a bit of research it appears that I can either:

• Create an implementation of gocql.Tracer, which appears to be quite resource intensive with the multiple queries to the Database, but does not require the creation of a wrapper
• Create a wrapper around gocql.Session or gocql.Query and avoid using the Tracer hook

Any suggestions which might be the better approach?

[Aneurysm9]

The comment on the gocql.Tracer type says:

Gathering this information might be essential for debugging and optimizing queries, but this feature should not be used on production systems with very high load.

That would lead me to believe that creating a wrapper is the better approach. Ideally we'd be able to leave the instrumentation enabled at all times.

[reggiemcdonald]

The comment on the gocql.Tracer type says:

Gathering this information might be essential for debugging and optimizing queries, but this feature should not be used on production systems with very high load.

That would lead me to believe that creating a wrapper is the better approach. Ideally we'd be able to leave the instrumentation enabled at all times.

Perfect that's what I thought. Thanks!

[reggiemcdonald]

https://github.com/gocql/gocql

Tasks

• code complete with tests passing
• Dockerfile with example app showing instrumentation
• documentation updated
• instrumentation added to the opentelemetry registry

Prior Art

• https://github.com/DataDog/dd-trace-go/tree/v1/contrib/gocql/gocql

All tasks completed, ready to close

[MrAlias]

Awesome 🎉! Thanks for the help @reggiemcdonald