Improve documentation for sidekiq instrumentation

[plantfansam]

We've had users tell us that our documentation for Sidekiq instrumentation is lacking. We should improve documentation on the library's options.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.

[bmulholland]

We're improving out Sidekiq telemetry now and it's both difficult and confusing without good docs. Normally I'd just add my +1 but need a comment for stalebot.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.

[bmulholland]

Another comment for stalebot

[bmulholland]

And actually, while I'm here, I was reminded of this issue when reading OT discussion on HN a couple days ago: https://news.ycombinator.com/item?id=38971964

[arielvalentin]

@bmulholland we have limited capacity and we are looking for help in all aspects of maintenance and development including documentation.

Would you be interested in contributing documentation for Sidekiq?

[bmulholland]

No, sorry, I don't have bandwidth for that. And I very much understand that others don't, either.

[github-actions]

👋 This issue has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the keep label to hold stale off permanently, or do nothing. If you do nothing this issue will be closed eventually by the stale bot.

[kaylareopelle]

We think this is closed by #825. Feel free to re-open if anyone disagrees!