-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Correct telemetry for Prometheus doc #2866
Conversation
Hi @clyang82. 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. |
/ @douglas-reid is my understanding right? please review. Thanks. |
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 so much for tackling this item! I had a few nits/suggestions, but this is great.
to monitor Mixer itself. | ||
1. *envoy* (`istio-mixer.istio-system:9102`): raw stats generated by Envoy (and | ||
translated from Statsd to Prometheus). | ||
1. *envoy* (`istio-proxy:15090`): raw stats generated by Envoy. |
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.
while we are here, can we also add entries for pilot, galley, and istio-policy (and update the "The configured Prometheus add-on scrapes three endpoints:" to read "The configured Prometheus add-on scrapes the following endpoints:") ?
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.
added.
|
||
For more on querying Prometheus, please read their [querying | ||
Prometheus configures to look for pods with the endpoint exposed and filters out a large number of envoy metrics based on scraping configuration. For more on querying Prometheus, please read their [querying |
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.
nit: "Prometheus is configured to look for pods with the envoy-prom
endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data processed by the add-on."
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.
updated
@douglas-reid Thanks for your suggestions. I have updated accordingly. I have one question about Prometheus? there are some configurations to define how to scrape the data. this is prometheus pull mode. In mixer adapter, there is a prometheus adapter which is using push mode. Is my understanding right? What is the difference in istio for these 2 modes? Thanks. |
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 not use parenthesis; they are ambiguous in their meaning. Instead use verbs and prepositions to make the actions the reader can take and the results of those actions clear.
|
||
1. *istio-mesh* (`istio-mixer.istio-system:42422`): all Mixer-generated mesh | ||
1. *istio-mesh* (`istio-telemetry.istio-system:42422`): all Mixer-generated mesh |
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.
Why are these not capitalized and separated. Is that the actual value of the endpoint? That case seems unlikely since I see the actual code in the parenthesis. Please capitalize appropriately and write them as separate words. Please use verbs and prepositions to make the actions explicit:
1. *istio-mesh* (`istio-telemetry.istio-system:42422`): all Mixer-generated mesh | |
1. **Istio mesh** addressable at `istio-telemetry.istio-system:42422`: Returns all Mixer-generated mesh |
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.
@rcaballeromx Thanks for your suggestions. actually, they are job names configured in prometheus. refer this document - https://preliminary.istio.io/help/ops/telemetry/missing-metrics/#verify-prometheus-configuration , you can find the job name
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.
Then, please refer to them as jobs and link to that page in your content. For example: The istio-mesh
job ...
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.
@rcaballeromx The page is used to tell the user how to verify the prometheus configurations. I do not think it is proper to link that here. How about change to - istio-telemetry.istio-system:42422
: The istio-mesh
job returns all Mixer-generated mesh
metrics. | ||
1. *mixer* (`istio-mixer.istio-system:9093`): all Mixer-specific metrics. Used | ||
1. *istio-telemetry* (`istio-telemetry.istio-system:9093`): all Mixer-specific metrics. Used |
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 on line 96:
1. *istio-telemetry* (`istio-telemetry.istio-system:9093`): all Mixer-specific metrics. Used | |
1. **Istio telemetry** addressable at `istio-telemetry.istio-system:9093`: Returns all Mixer-specific metrics. Use this endpoint |
to monitor Mixer itself. | ||
1. *envoy* (`istio-mixer.istio-system:9102`): raw stats generated by Envoy (and | ||
translated from Statsd to Prometheus). | ||
1. *envoy-stats* (`istio-proxy:15090`): raw stats generated by Envoy. Prometheus is configured to look for pods with the `envoy-prom` endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data processed by the add-on. |
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 on line 96:
1. *envoy-stats* (`istio-proxy:15090`): raw stats generated by Envoy. Prometheus is configured to look for pods with the `envoy-prom` endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data processed by the add-on. | |
1. Envoy stats addressable at `istio-proxy:15090`: Returns the raw stats generated by Envoy. Prometheus is configured to look for pods with the `envoy-prom` endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data the add-on processes. |
1. *envoy* (`istio-mixer.istio-system:9102`): raw stats generated by Envoy (and | ||
translated from Statsd to Prometheus). | ||
1. *envoy-stats* (`istio-proxy:15090`): raw stats generated by Envoy. Prometheus is configured to look for pods with the `envoy-prom` endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data processed by the add-on. | ||
1. *pilot* (`istio-pilot.istio-system:9093`): all pilot metrics. |
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.
1. *pilot* (`istio-pilot.istio-system:9093`): all pilot metrics. | |
1. **Pilot** addressable at`istio-pilot.istio-system:9093`: Returns all the Pilot-generated metrics. |
translated from Statsd to Prometheus). | ||
1. *envoy-stats* (`istio-proxy:15090`): raw stats generated by Envoy. Prometheus is configured to look for pods with the `envoy-prom` endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data processed by the add-on. | ||
1. *pilot* (`istio-pilot.istio-system:9093`): all pilot metrics. | ||
1. *galley* (`istio-galley.istio-system:9093`): all galley metrics. |
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.
1. *galley* (`istio-galley.istio-system:9093`): all galley metrics. | |
1. **Galley** addressable at `istio-galley.istio-system:9093`: Returns all the Galley-generated metrics. |
1. *envoy-stats* (`istio-proxy:15090`): raw stats generated by Envoy. Prometheus is configured to look for pods with the `envoy-prom` endpoint exposed. The add-on configuration filters out a large number of envoy metrics during collection in an attempt to limit the scale of data processed by the add-on. | ||
1. *pilot* (`istio-pilot.istio-system:9093`): all pilot metrics. | ||
1. *galley* (`istio-galley.istio-system:9093`): all galley metrics. | ||
1. *istio-policy* (`istio-policy.istio-system:9093`): all policy metrics. |
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.
1. *istio-policy* (`istio-policy.istio-system:9093`): all policy metrics. | |
1. **Istio policy** addressable at `istio-policy.istio-system:9093`: Returns all policy-related metrics. |
Can we move this forward? Only a few grammatical fixes left... Thanks. |
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang <[email protected]>
9dfc292
to
d03a298
Compare
translated from Statsd to Prometheus). | ||
The configured Prometheus add-on scrapes the following endpoints: | ||
|
||
1. `istio-telemetry.istio-system:42422`: The `istio-mesh` job returns all Mixer-generated mesh. |
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.
mesh metrics
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.
done
Signed-off-by: Chun Lin Yang <[email protected]>
/lgtm |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: clyang82, gyliu513 If they are not already assigned, you can assign the PR to them by writing The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* Correct telemetry for prometheus doc Signed-off-by: Chun Lin Yang <[email protected]> * Add galley,polit and policy Signed-off-by: Chun Lin Yang <[email protected]> * update zh doc Signed-off-by: Chun Lin Yang <[email protected]> * Address review comments Signed-off-by: Chun Lin Yang <[email protected]> * mesh to metrics Signed-off-by: Chun Lin Yang <[email protected]>
Signed-off-by: Chun Lin Yang [email protected]
Make the document (https://preliminary.istio.io/docs/tasks/telemetry/querying-metrics/) changes to reflect - istio/istio#8415