-
Notifications
You must be signed in to change notification settings - Fork 529
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
added the right pointer for OTLP endpoint #7375
Conversation
Having a look. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apart from my specific comment, I wonder if we shouldn't be editing Grafana Cloud documentation instead, making sure that (Grafana Cloud) users are directed towards the OTel Gateway instead (as opposed to using the Mimir OTLP endpoint directly.
Having thought it over again, I see that the point of these admonitions should be to steer readers of Grafana Cloud documentation away from using the Mimir OTLP endpoint directly. I wonder though if we have the ability to put the admonitions into the Grafana Cloud docs sources instead, so they get merged with Mimir docs sources? Maybe we're not able to 🤷
You also need make doc
locally to fix the formatting, and pass CI.
@@ -61,6 +61,9 @@ service: | |||
``` | |||
|
|||
## OTLP | |||
{{% admonition type="note" %}} | |||
If you are on Grafana Cloud, please use the OpenTelemetry Protocol (OTLP), and you can find more information [here] (https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it makes sense to say to use OTLP, since this section is in fact about using OTLP. What we want to instead is to recommend using the OTel Gateway endpoint in Grafana Cloud.
Also fixing the link while I'm here. I recall furthermore that our documentation style guidelines say to use something more descriptive than "here", for links.
If you are on Grafana Cloud, please use the OpenTelemetry Protocol (OTLP), and you can find more information [here] (https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). | |
If you are on Grafana Cloud, please use the OpenTelemetry Gateway, which you can find more information on in [this guide](https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As @aknuds1 has pointed out, it is important to write useful link text for those reading the documentation on a screen reader.
For guidance, refer to Useful link text
I don't think it makes sense to say to use OTLP, since this section is in fact about using OTLP. What we want to instead is to recommend using the OTel Gateway endpoint in Grafana Cloud.
I agree, perhaps the following, also applied to the other note.
If you are on Grafana Cloud, please use the OpenTelemetry Protocol (OTLP), and you can find more information [here] (https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). | |
To send OTLP data to Grafana Cloud, refer to [Send data using OpenTelemetry Protocol (OTLP)](https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). |
I also think the note makes sense at the beginning of this page rather than under the OTLP heading.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdbaldry do you think it's problematic at all to include Grafana Cloud specifics in Mimir OSS docs? I'm uncertain whether we have a policy on this, or not (re: my wondering on whether we could merge in the admonitions from Grafana Cloud docs sources).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I actually like @jdbaldry's suggestion better than my own, especially since it doesn't mention OTel Gateway (which may be replaced in the future).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
do you think it's problematic at all to include Grafana Cloud specifics in Mimir OSS docs?
That's a great question that I'm not certain of the answer to. I will find out and get back to you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Another interesting question.
I am not certain about the intention of this page but at a scan, I believed it to be a task intending to help the user write OpenTelemetry metrics to Mimir. In that case I think it makes sense to tell them as early as possible in the process.
I'm not sure if I would expect users to be linked directly to the OTLP heading unless they are certainly interested in sending to OSS Mimir.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jdbaldry ah my bad, I was confusing this change and the other one. The latter is the HTTP API reference page, and is for a lot more than just OTel. Never mind :) My comment in this regard only makes sense for the HTTP API change.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No worries at all, I think for HTTP API you are absolutely right. I'd also consider leaving out the note in that page because I think it is less relevant there. I'm on the fence to be honest. Let's see what the rest of the doc squad has to say about Grafana Cloud notes in OSS docs first :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got some feedback on that actually, it's fine to have Grafana Cloud notes in the docs, especially if it eliminates confusion.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for figuring this out @jdbaldry!
@@ -317,6 +317,9 @@ Requires [authentication](#authentication). | |||
``` | |||
POST /otlp/v1/metrics | |||
``` | |||
{{% admonition type="note" %}} | |||
If you are on Grafana Cloud, please use the OpenTelemetry Protocol (OTLP), and you can find more information [here] (https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See my comment above. Copying @jdbaldry's suggestion ;)
If you are on Grafana Cloud, please use the OpenTelemetry Protocol (OTLP), and you can find more information [here] (https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). | |
To send OTLP data to Grafana Cloud, refer to [Send data using OpenTelemetry Protocol (OTLP)](https://grafana.com/docs/grafana-cloud/send-data/otlp/send-data-otlp/). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the contribution @zhehao-grafana!
To summarize the discussion and next steps:
-
I believe both notes should be updated to instead use the following text:
To send OTLP data to Grafana Cloud, refer to Send data using OpenTelemetry Protocol (OTLP).
-
I believe the note in
docs/sources/mimir/configure/configure-otel-collector.md
should be moved to the top of the page as part of the introduction text. -
You need to sign the CLA so that we can accept your changes.
@jdbaldry Thanks for the review! Do you mind taking a look at the latest change I made? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nearly there, thanks for considering our suggestions!
https://github.com/grafana/mimir/pull/7375/files#diff-027d0564bef402ca0e98549c7f5ceb3fcfbdb1e8d2fc78b667d1bf360cbd6059L63-L64
looks to be an accidental deletion. If you can restore those two lines, this is good to go!
please review the latest change. @jdbaldry |
e9db13e
to
9b00d7e
Compare
Signed-off-by: Arve Knudsen <arve.knudsen@gmail.com>
What this PR does
It is used to point to the right OTLP sources on cloud so people don't use the wrong one
Which issue(s) this PR fixes or relates to
Fixes #
Checklist
CHANGELOG.md
updated - the order of entries should be[CHANGE]
,[FEATURE]
,[ENHANCEMENT]
,[BUGFIX]
.about-versioning.md
updated with experimental features.