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
Rebrand and update lightstep docs #13779
base: master
Are you sure you want to change the base?
Rebrand and update lightstep docs #13779
Conversation
…rocedures to use OpenTelemetry
…update procedures to use OpenTelemetry" This reverts commit 25a4d05.
😊 Welcome! This is either your first contribution to the Istio documentation repo, or
Thanks for contributing! Courtesy of your friendly welcome wagon. |
Hi @robswhitmore. Thanks for your PR. I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
I'd like to also add the label |
/ok-to-test |
Depending on when this merges, it may or may not need the 1.19 label as there is no 1.19 branch (right now). The branch will be created when 1.19.0 is release.d. |
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.
/ok-to-test
I fixed the lint errors that I can, but the errors for spacing around lists can't be fixed because those are inside yaml code blocks. What should I do? Also, what should we tag this PR so that it goes into the latest release? |
The errors are:
This has to do with you incrementing the numbers. All ordered list items must be |
We can work on getting the PR into the latest releases once it's ready to merge. It'll first go into the preliminary.istio.io docs and ten we will cherry-pick to the branch that corresponds to istio.io. That branch is changing soon, so timing will dictate where we cherry-pick. |
@istio/wg-policies-and-telemetry-maintainers Can you review this as owners of the page as well. Thanks. |
Also, note that you can click on the |
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 believe these 3 suggestions will fix the numbering. Looks like the line numbering is off by 1.
content/en/docs/tasks/observability/distributed-tracing/lightstep/index.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/observability/distributed-tracing/lightstep/index.md
Outdated
Show resolved
Hide resolved
content/en/docs/tasks/observability/distributed-tracing/lightstep/index.md
Outdated
Show resolved
Hide resolved
…tep/index.md Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
…tep/index.md Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
…tep/index.md Co-authored-by: Eric Van Norman <ericvn@us.ibm.com>
that the call took 15.30 ms. The second span is labeled with the `reviews.default.svc.cluster.local:9080/*` operation | ||
and the `reviews.default: proxy server` service. The second span is a child of the first span and represents the | ||
server-side span of the call. The screenshot shows that the call took 14.60 ms. | ||
## View metrics in Cloud Observability |
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.
The folder content/en/docs/tasks/observability/distributed-tracing/lightstep is for tracing. Consider placing the metric guide into a different folder.
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.
Moved to the metrics section
aliases: | ||
- /docs/tasks/telemetry/distributed-tracing/lightstep/ | ||
owner: istio/wg-policies-and-telemetry-maintainers | ||
test: no | ||
--- | ||
|
||
{{< boilerplate telemetry-tracing-tips >}} | ||
You use the [OpenTelemetry Collector](https://opentelemetry.io/docs/collector/) to send Istio metrics to Cloud Observability using Istio proxies within each pod. Metrics are collected and forwarded to the OpenTelemetry Collector, which acts as a central collection and processing point and then sends those metrics to Cloud Observability. |
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.
The folder content/en/docs/tasks/observability/distributed-tracing/lightstep is for tracing. Consider placing the metric guide into a different folder.
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.
Moved to the metrics section
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.
Removed references to Lightstep in site where it was mentioned in the context of tracing (this also fixed broken links caused when moving the topics from Tracing to Metrics). There is still a broken link in /news/releases/1.1.x/announcing-1.1/change-notes/
, but I don't think I should change that, right?
…ed. Removed mentions of trace data and adjusted the title and description accordingly.
…cing. Updated page alias
/test lint |
I don't think I can fix this link because it's in a news post, right? The link goes to /news/releases/1.1.x/announcing-1.1/change-notes/ |
@lei-tang or whoever else might be able to help - |
@ericvn Do you have suggestions for fixing the broken link error above? |
Lint error is Running linkinator... You removed this file so makes sense that the link isn't found. What do you want people who pointed to it to point to now? You could point to an older release's version of the file by changing the URL to point to a specific older release. Maybe you want to add an alias to a new page so the page would then be used for the deleted page (ie. replace the alias I've asked you to remove with |
Also added the cherry-pick label since we have cut the new branch. |
The lint report tells you the file the link is originating from, which is https://github.com/robswhitmore/istio.io/blob/robswhitmore/rebrand-update-lightstep/content/en/news/releases/1.1.x/announcing-1.1/change-notes/index.md?plain=1#L165 Since you're changing the name of the file, link to an archived version of the page, for example: https://istio.io/v1.18/docs/tasks/observability/distributed-tracing/lightstep/ |
@robswhitmore Daniel is correct. There are two ways to fix the issue. One is to update the link which is pointing to the file you removed in As I noted, if the new page you replaced the deleted page with is an acceptable alternative, then you can simply add Pick whichever way yields the best information to the reader. |
weight: 11 | ||
keywords: [telemetry, metrics ,lightstep, servicenow, cloud observability] | ||
aliases: | ||
- /docs/tasks/observability/distributed-tracing/lightstep/ |
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'm wondering if there is a format issue with number of leading spaces, as this does look correct. Need to try pulling your PR and trying the link-check locally.
- /docs/tasks/observability/distributed-tracing/lightstep/ | |
- /docs/tasks/observability/distributed-tracing/lightstep/ |
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.
Basically, the alias discussion is here: https://istio.io/latest/docs/releases/contribute/front-matter/#rename-move-or-delete-pages
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 did pull your branch locally and try a few things with the aliases, and I never got it to work. I guess I would just do option 1 and update the 1 link to point to the archive and remove the alias.
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.
@frankbu is there some magic on the aliases:
?
--- | ||
title: Viewing Istio Metrics in Cloud Observability from ServiceNow | ||
description: This task shows you how to use OpenTelemetry to ingest and view Istio metrics in Cloud Observability (formerly Lightstep). | ||
weight: 11 |
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.
Also the weight here is used to set the order of the links within the page. You can look at your preview at https://deploy-preview-13779--preliminary-istio.netlify.app/latest/docs/tasks/observability/metrics/ to see if the orderings correct. Higher numbers go down the order.
|
||
## Configure Istio Operator | ||
|
||
Create an `istio-operator.yaml` file by copying the following code. |
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.
Is 'istio-operator.yaml' here used in the guide? A quick search did not return any results.
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'm not sure what you mean by "used in the guide?" Do you mean elsewhere in Istio docs? It's used in this topic to configure the k8s operator for Istio.
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 mean whether 'istio-operator.yaml' is used in this guide.
"It's used in this topic to configure the k8s operator for Istio."
Which command lines in this guide use 'istio-operator.yaml'?
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 think what @lei-tang is saying is that the instructions have you creating a number of files, like otel-collector-configmap.yaml
and otel-collector-deployment.yaml
and you look at the directions in the next sections, you can see kubectl apply -f
for these files. The question is where is there an instruction that actually uses the 'istio-operator.yaml' file.
And if there is no usage for the file, why are we creating it on this page?
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 - I realized what he was asking and agreed, so I sent it back to the engineering team. They are working on updates.Thanks for catching that - I definitely should have, but with this rebrand, I've been 🤪!
Does #13996 replace this? |
News to me! 😕 Let me find out what's going on... |
Looks like the eng team decided to focus on Tracing, so that new PR is separate from this one, and is taking precedence. Sorry for all the confusion! |
I think you are saying that at some point this PR will be revisited. |
Yes, at some point. Thanks - |
PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Please provide a description for what this PR is for.
Lightstep has been rebranded to Cloud Observability from ServiceNow. Additionally, we now use the OpenTelemetry Collector to ingest metrics, traces, and logs from third-parties. These updates include both changes.
And to help us figure out who should review this PR, please
put an X in all the areas that this PR affects.