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

add default service name #7

Open
wants to merge 4 commits into
base: web3dev-version
Choose a base branch
from

Conversation

nomadbitcoin
Copy link

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Description

Related Tickets & Documents

  • Related Issue #
  • Closes #

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.

UI accessibility concerns?

If your PR includes UI changes, please replace this line with details on how
accessibility is impacted and tested. For more info, check out the
Forem Accessibility Docs.

Added/updated tests?

  • Yes
  • No, and this is why: please replace this line with details on why tests
    have not been included
  • I need help with writing tests

[Forem core team only] How will this change be communicated?

Will this PR introduce a change that impacts Forem members or creators, the
development process, or any of our internal teams? If so, please note how you
will share this change with the people who need to know about it.

  • I've updated the Developer Docs or
    Storybook (for Crayons components)
  • This PR changes the Forem platform and our documentation needs to be
    updated. I have filled out the
    Changes Requested
    issue template so Community Success can help update the Admin Docs
    appropriately.
  • I've updated the README or added inline documentation
  • I've added an entry to
    CHANGELOG.md
  • I will share this change in a Changelog
    or in a forem.dev post
  • I will share this change internally with the appropriate teams
  • I'm not sure how best to communicate this change and need help
  • This change does not need to be communicated, and this is why not: please
    replace this line with details on why this change doesn't need to be
    shared

[optional] Are there any post deployment tasks we need to perform?

[optional] What gif best describes this PR or how it makes you feel?

alt_text

@web3melk web3melk had a problem deploying to pt-w3d-commu-fix-sideki-wslzav October 23, 2024 23:25 Failure
@nomadbitcoin nomadbitcoin temporarily deployed to pt-w3d-commu-fix-sideki-wslzav October 23, 2024 23:37 Inactive
@web3melk web3melk temporarily deployed to pt-w3d-commu-fix-sideki-xaz9ki October 23, 2024 23:51 Inactive
@web3melk web3melk temporarily deployed to pt-w3d-commu-fix-sideki-zodjiy October 23, 2024 23:58 Inactive
@web3melk web3melk temporarily deployed to pt-w3d-commu-fix-sideki-uorcmi October 24, 2024 00:57 Inactive
@@ -7,7 +7,7 @@
c.tracing.instrument :rails, service_name: service_name
c.tracing.instrument :active_support, cache_service: "#{service_name}-cache"
c.tracing.instrument :active_record, service_name: "#{service_name}-db"
c.tracing.instrument :sidekiq, service_name: "#{service_name}-sidekiq"
c.tracing.instrument :sidekiq, service_name: "#{service_name}-sidekiq", client_service_name: "#{service_name}-sidekiq-client"

Choose a reason for hiding this comment

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

📝 [rubocop] <Layout/LineLength> reported by reviewdog 🐶
Line is too long. [127/120] (https://rubystyle.guide#max-line-length)

Suggested change
c.tracing.instrument :sidekiq, service_name: "#{service_name}-sidekiq", client_service_name: "#{service_name}-sidekiq-client"
c.tracing.instrument :sidekiq, service_name: "#{service_name}-sidekiq",
client_service_name: "#{service_name}-sidekiq-client"

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.

2 participants