Write a more complete Custom Instrumentation documentation about sentry-docs

[pbernery]

Hey @gggritso.
No I am not, or to be correct, I was not when I implemented my first custom transaction.
Now I also have custom transaction tracked in Sidekiq jobs, but now I know how to declare these transactions, it works well.

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[getsantry]

Routing to @getsentry/product-owners-performance for triage ⏲️

[gggritso]

@pbernery thanks for raising this! That's frustrating, sorry about the time waster—we'll take a look at fixing the error you found, and expanding the docs

As for attaching to the current scope, are you adding instrumentation in a threaded environment?

[sl0thentr0py]

transferring this to docs, will update the custom instrumentation sample.
regarding truncation, we'll try to have a page on the product side more transparent about the limits but ultimately these are enforced on the server and can change so it's somewhat hard to keep such lists up to date.

[getsantry]

Assigning to @getsentry/support for routing ⏲️

[pbernery]

transferring this to docs, will update the custom instrumentation sample. regarding truncation, we'll try to have a page on the product side more transparent about the limits but ultimately these are enforced on the server and can change so it's somewhat hard to keep such lists up to date.

I understand the limitations. I proposed some things here getsentry/sentry-ruby#2307, but still that would depend on the server. Maybe the server could return a status code directly when such content is posted? And thus the client could informed the developer.