Uploaded image for project: 'Red Hat 3scale API Management'
  1. Red Hat 3scale API Management
  2. THREESCALE-6314

[DDF] The current guide with the localAgentHostPort being the jaeger-agent assumes jaeger deployment in the same namespace.

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • Documentation
    • False
    • False
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Not Started
    • Undefined

      The current guide with the localAgentHostPort being the jaeger-agent assumes jaeger deployment in the same namespace. However, there will be many instances where this won't be the case. A very likely scenario is to report the traces to the jaeger-collector in another namespace without a local jaeger agent. Please provide documentation regarding such a configuration.

      Reported by: berkeragir

      https://access.redhat.com/documentation/en-us/red_hat_3scale_api_management/2.9/html/administering_the_api_gateway/operating-apicast#annotations:7abd7f1e-5a19-472f-99e5-9328871f6ab0

              Unassigned Unassigned
              ddf-bot DDF Bot
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: