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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: Add upper bound to sidekiq instrumentation #300

Merged
merged 1 commit into from
May 24, 2023

Conversation

Ferenc-
Copy link
Contributor

@Ferenc- Ferenc- commented May 24, 2023

No description provided.

Signed-off-by: Ferenc G茅czi <ferenc.geczi@ibm.com>
@Ferenc- Ferenc- requested a review from basti1302 May 24, 2023 12:23
@@ -5,7 +5,8 @@ module Instana
module Activators
class SidekiqClient < Activator
def can_instrument?
defined?(::Sidekiq) && ::Sidekiq.respond_to?(:configure_client) && ::Instana.config[:'sidekiq-client'][:enabled]
defined?(::Sidekiq) && defined?(::Sidekiq::VERSION) && ::Sidekiq.respond_to?(:configure_client) && ::Instana.config[:'sidekiq-client'][:enabled] &&
Gem::Specification.find_by_name('sidekiq').version < Gem::Version.new('5.3')
Copy link
Contributor

Choose a reason for hiding this comment

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

question: Just out of curiosity: Do we ever log something if can_instrument? returns false? This is probably out of scope for this PR, but it might be valuable to log this at least at debug level.

@Ferenc- Ferenc- merged commit e7a9639 into master May 24, 2023
37 checks passed
@Ferenc- Ferenc- deleted the sidekiq-upper-bound branch May 24, 2023 14:56
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.

None yet

2 participants