add blogpost on migrating away from the Jaeger exporter

[codeboten]

This is to help users that upgrade to v0.85.0 of the OTel Collector.

[svrnm]

I am happy to have it as a blog post to announce and promote it better, but eventually this should be placed somewhere here: https://opentelemetry.io/docs/migration/#jaeger-client

[codeboten]

I am happy to have it as a blog post to announce and promote it better, but eventually this should be placed somewhere here: https://opentelemetry.io/docs/migration/#jaeger-client

Right the documentation already covers how to use OTLP to send data to Jaeger since #3262, I'm happy to move this content wherever it makes the most sense in the future.

[yurishkuro]

TLS is not enabled in Jaeger by default, it's worth calling out here.

[cartermp]

@codeboten if you run npm run test-and-fix then this should go green.

[codeboten]

@cartermp what should i do with the refcache check?

[cartermp]

Hmm, did npm run test-and-fix not work? That should be the fix.

[codeboten]

so test-and-fix didn't show any changed files.... and running fix:format gives me a bunch of unrelated changes:

        modified:   assets/js/registrySearch.js
        modified:   content/en/blog/2022/instrument-apache-httpd-server/index.md
        modified:   content/en/docs/instrumentation/js/getting-started/browser.md
        modified:   content/en/docs/instrumentation/js/manual.md
        modified:   content/en/docs/instrumentation/js/propagation.md
        modified:   content/en/docs/instrumentation/js/serverless.md
        modified:   gulp-src/_md-rules/trim-code-block-and-unindent.js
        modified:   gulp-src/prune.js
        modified:   scripts/registry-scanner/index.mjs

Do i have to commit those?

Addressed

[cartermp]

@codeboten I'll just go ahead and merge this and fix stuff in main. I think we had some errant unformatted changes (which is weird since CI should have caught them)

[codeboten]

Thanks @cartermp!