Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Update Tracing integration documentation #203
(HERE keep introduction on tracing...)
In cluster URL
In order to fetch data from Jaeger, Kiali needs to get an URL that can be resolved from inside the cluster, typically using Kubernetes DNS. This is the
external_services: tracing: in_cluster_url: 'http://tracing.istio-system/jaeger'
!NOTE! If you use the Kiali operator (recommended), this config can be set in the Kiali CR. But in most cases, the Kiali operator will set a valid default
-- screenshots to tracing-enabled Kiali --
Configuring an external URL for Jaeger will enable more links from Kiali to Jaeger UI. This URL needs to be accessible from the browser (it's used for links generation). Example:
external_services: tracing: in_cluster_url: 'http://tracing.istio-system/jaeger' url: 'http://my-jaeger-host'
-- screenshots to external links --
!NOTE! You may have
For advanced configuration on Jaeger integration, please refer to the Kiali CR description. It is relevant for config map as well, if you don't use the Kiali operator.
(THEN follow on features description - assuming Kiali is fully configured for tracing)
I agree but the oproblem here is that we have a FAQ about tracing, another page with the information about tracing and another one for the config..
3 places about tracing information !!! without links to each other so the user must check the 3 views. we need to reorganize the website
@aljesusg what is the page about configuration? I can't find that...
About FAQ, it's a different approach, focused on troubleshooting / Q&A. It answers very specific problems, not like here. Maybe some items in FAQ should be rewritten, I haven't checked yet.
FAQ to me is more "the documentation of the last chance" ; when stuff doesn't work as expected and I can't figure out why. Ideally I should never have to check a FAQ, as a user... (this is how I see it, maybe it's just me)
mmm maybe we removed that page I can't find it neither
jotak left a comment
Sending some suggestions that we can discuss. Most notably, after checking on deployed site I think screenshots of Traces screen are better placed outside of the configuration section (so I created a new section).