No commit activity in last 3 years
No release in over 3 years
Instruments the graphql-ruby gem for opentracing
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
 Dependencies

Development

~> 2.0
~> 10.0
~> 3.0

Runtime

~> 0.5.0
 Project Readme

GraphQL Opentracing

Open Tracing instrumentation for the graphql gem. By default it starts a new span for every request handled by graphql. It follows the open tracing tagging semantic conventions

Installation

Add this line to your application's Gemfile:

gem 'graphql-opentracing'

And then execute:

$ bundle

Or install it yourself as:

$ gem install graphql-opentracing

Usage

First load the opentracing (Note: this won't automatically instrument the graphql gem)

require "graphql-opentracing"

If you have setup OpenTracing.global_tracer you can turn on spans for all requests with just:

    GraphQL::Tracer.instrument

You must also modify your GQL schema to add the ActiveSupportNotifications tracer provided by the GQL gem

tracer(GraphQL::Tracing::ActiveSupportNotificationsTracing)

Under the hood this gem subscribes to graphql instrumentation events through the ActiveSupport notifications framework. If you find the number of spans too noisy you can control which spans are reported though a callback like:

GraphQl::Tracer.instrument(
    schema: MyGQLSchema,
    tracer: tracer,
    ignore_request: ->(name, started, finished, id, data) { !name.include? 'execute_query' }
)

Development

After checking out the repo, run bundle install to install dependencies. Then, run rspec to run the tests.

Contributing

Bug reports and pull requests are welcome on GitHub at https://github.com/benedictfischer09/ruby-graphql-instrumentation. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.

License

The gem is available as open source under the terms of the MIT License.

Code of Conduct

Everyone interacting in the project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.