add note about micrometer

[zeitlinger]

No description provided.

[zeitlinger]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/9450569700

[chalin]

As mention on Slack. I think that the entire content of this section should be moved one level up, into the Java landing page (or it's own Comparing page).

[trask]

As mention on Slack. I think that the entire content of this section should be moved one level up, into the Java landing page (or it's own Comparing page).

I think I prefer its own Comparing page under Spring Boot Starter

[zeitlinger]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/9460735466

[theletterf]

There's something in adding a recommendation in user docs that is a bit jarring to me (using Spring Boot starter instead of another solution). I think docs should be more neutral. Perhaps the recommendation or even the whole content could go into a blog post. @svrnm What do you reckon?

[zeitlinger]

There's something in adding a recommendation in user docs that is a bit jarring to me (using Spring Boot starter instead of another solution). I think docs should be more neutral. Perhaps the recommendation or even the whole content could go into a blog post. @svrnm What do you reckon?

the tone should be neutral
we keep getting those questions - so it would be helpful to have an easy-to-find answer

[zeitlinger]

/fix:format

[opentelemetrybot]

You triggered fix:format action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/9462194586

[chalin]

Here's a proposal: @zeitlinger make the minor suggested edits, we land this PR, and after that look at moving the content to a dedicated comparing page. WDYT?

[chalin]

100% agree with @theletterf comment about neutrality -- and thanks for bring that up, it had bothered me too.

[chalin]

/fix:refcache

[opentelemetrybot]

You triggered fix:refcache action run at https://github.com/open-telemetry/opentelemetry.io/actions/runs/9464160116

[svrnm]

on the topic of neutrality: since this seems to be a frequently asked question it can/should live in the docs not in the blog, I actually think we can have more of that in the future, but key is that the wording is friendly and embracing the other open source solution as well. I will reread the PR under that aspect once again

[svrnm]

Taking a closer look under the "neutrality" perspective, see my suggestions.

A general comment: the differences are very high level, so as an end user I might want to know even more. Can we expand on that a little bit (e.g. my understanding is that micrometer is a facade around different metric/tracing solutions ("Micrometer provides a simple facade over the instrumentation clients for the most popular observability systems"), I think that's a key differentiator, if someone thinks they do not want to be "vendor-locked" by opentelemetry, they can have another layer of abstraction.

[svrnm]

Suggested change

	As the authors of the OpenTelemetry Spring Boot starter, we recommend using the
	OpenTelemetry Spring Boot starter. We have a great community behind it, and are
	continuously making improvements. If you try it out and have any problems or
	suggestions, open an
	[issue](https://github.com/open-telemetry/opentelemetry-java-instrumentation/issues)
	in our repository.
	Both solutions are open source and support different exporters, including OTLP and Prometheus,
	and both are compatible for tracing use cases. This means, that they fit equally into an existing
	observability architecture. It is up to the end user to decide, which solution satisfies their requirements better.

This is the sentence I would remove in the light of "neutrality". It's very obvious that we recommend the otel solution, so we don't have to say that explicitly.

[zeitlinger]

It sounds a bit like we would not be convinced that our solution is the better one.

We do try to become the standard API in the java world - can we say that in a friendly way?

[svrnm]

Suggested change

	- Offers optional bridges into parts of the OpenTelemetry ecosystem.
	- Offers optional bridges into OpenTelemetry Tracing and Metrics.

[zeitlinger]

you also don't get SDK features

[zeitlinger]

if someone thinks they do not want to be "vendor-locked" by opentelemetry, they can have another layer of abstraction.

the message of this PR is that you're not locked, because only otel is governed by an independent body

[svrnm]

@zeitlinger can we make any progress on this? If I remember correctly @trask wanted to take another look at this?

[zeitlinger]

yes, @trask is still on it

[cartermp]

Closing out old PR -- I realize we wanted to say something here but it's been a few months, so feel free to re-open if you think it's still worth it