Please document that envoy metrics are not automatically available

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure

https://docs.microsoft.com/azure

Creative Commons Attribution 4.0 International

10.28k stars 21.47k forks source link

Please document that envoy metrics are not automatically available #110110

Closed chitturs closed 1 year ago

chitturs commented 1 year ago

OSM provides envoy metrics by default. Istio doesn't. This wasn't clear from the docs until this got debugged by the Istio team.

Please document this limitation to allow smoother migration from OSM to Istio.

Workaround is to use Istio Standard Metrics available by default.

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: df0ffbaf-13e7-d3af-15e6-553c6ef4cc73
Version Independent ID: 06397549-1fbf-29ea-61ac-2510bd2f861f
Content: Istio-based service mesh add-on for Azure Kubernetes Service (preview) - Azure Kubernetes Service
Content Source: articles/aks/istio-about.md
Service: azure-kubernetes-service
GitHub Login: @MGoedtel
Microsoft Alias: shasb

AjayBathini-MSFT commented 1 year ago

@chitturs Thanks for your feedback! We will investigate and update as appropriate.

Naveenommi-MSFT commented 1 year ago

@MGoedtel Could you please review add comments on this, update as appropriate.

Naveenommi-MSFT commented 1 year ago

@chitturs Thank you for bringing this to our attention. It is true that OSM provides envoy metrics by default, while Istio does not. This limitation is not explicitly mentioned in the Istio documentation, but it is a known issue that has been reported by users. To allow for a smoother migration from OSM to Istio, it is recommended to use Istio Standard Metrics, which are available by default. These metrics provide a comprehensive view of the service mesh and can be used to monitor the health and performance of the mesh.

Naveenommi-MSFT commented 1 year ago

@chitturs We are going to close this thread, if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

chitturs commented 1 year ago

Please update the documentation and then close. Thanks. @Naveenommi-MSFT

Naveenommi-MSFT commented 1 year ago

Hi @chitturs Our team is updating the documentation. Please keep track of any updates on the identical case brought up by one of our customers. https://github.com/MicrosoftDocs/azure-docs/issues/110547