Skip to main content
AI
  • Get started with AI

    • Red Hat AI

      Accelerate the development and deployment of enterprise AI solutions.

    • AI learning hub

      Explore learning materials and tools, organized by task.

    • AI interactive demos

      Click through scenarios with Red Hat AI, including training LLMs and more.

    • AI/ML learning paths

      Expand your Red Hat OpenShift AI knowledge using these learning resources.

    • AI quickstarts

      Focused AI use cases designed for fast deployment on Red Hat AI platforms.

    • No-cost AI training

      Foundational Red Hat AI training.

  • Featured resources

    • Red Hat OpenShift AI
    • Open source AI for developers
    • AI product application development
    • Open source-powered AI/ML for hybrid cloud
    • AI and Node.js cheat sheet

Red Hat AI Factory with NVIDIA

Red Hat AI Factory with NVIDIA is a co-engineered, enterprise-grade AI solution for building, deploying, and managing AI at scale across hybrid cloud environments.

Learn
  • Self-guided

    • Documentation

      Find answers, get step-by-step guidance, and learn how to use Red Hat products.

    • Learning paths

      Explore curated walkthroughs for common development tasks.

    • Guided learning

      Receive custom learning paths powered by our AI assistant.

    • See all learning
  • Hands-on

    • Developer Sandbox

      Spin up Red Hat's products and technologies without setup or configuration.

    • Interactive labs

      Learn by doing in these hands-on, browser-based experiences.

    • Interactive demos

      Click through product features in these guided tours.

  • Browse by topic

    • AI/ML
    • Automation
    • Java
    • Kubernetes
    • Linux
    • See all topics
  • Training & certifications

    • Courses and exams
    • Certifications
    • Skills assessments
    • Red Hat Academy
    • Learning subscription
    • Explore training
Build
  • Get started

    • Red Hat build of Podman Desktop

      A downloadable, local development hub to experiment with our products and builds.

    • Developer Sandbox

      Spin up Red Hat's products and technologies without setup or configuration.

  • Download products

    • Red Hat Enterprise Linux
    • Red Hat AI
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products
  • Featured

    • Red Hat build of OpenJDK
    • Red Hat JBoss Enterprise Application Platform
    • Red Hat OpenShift Dev Spaces
    • Red Hat Developer Toolset
  • References

    • E-books
    • Documentation
    • Cheat sheets
    • Architecture center
Community
  • Get involved

    • Events
    • Live AI events
    • Red Hat Summit
    • Red Hat Accelerators
    • Community discussions
  • Follow along

    • Articles & blogs
    • Developer newsletter
    • Videos
    • Github
  • Get help

    • Customer service
    • Customer support
    • Regional contacts
    • Find a partner

Join the Red Hat Developer program

Download Red Hat products and project builds, access support documentation, learning content, and more.

ConsoleDocsSupport Search
New For you

Recommended

We'll recommend resources you may like as you browse. Try these suggestions for now.

  • Product downloads
  • Cheat sheets
  • Red Hat Developer learning portal
  • Developer blog
  • E-books
  • Developer Sandbox
Log in

Get more with a Red Hat Developer account

  • Product downloads
  • Console access
  • Event registration
  • Training & trials
Explore more account benefitsLog in or register

A subscription may be required for some services.

Contact us

Tracing Kubernetes applications with Jaeger and Eclipse Che

November 14, 2019
Gary Brown
Related topics:
IDEsKubernetes
Related products:
Developer Toolset

    Developing distributed applications is complicated. You can wait to monitor for performance issues once you launch the application on your test or staging servers, or in production if you’re feeling lucky, but why not track performance as you develop? This allows you to identify improvement opportunities before rolling out changes to a test or production environment. This article demonstrates how two tools can work together to integrate performance monitoring into your development environment: Eclipse Che and Jaeger.

    According to the Eclipse Che website:

    "Che brings your Kubernetes application into your development environment and provides an in-browser IDE, allowing you to code, build, test, and run applications exactly as they run on production from any machine."

    In this article, we show how simple it is to add Jaeger to your Eclipse Che development workspace and observe how your Kubernetes application performs. We will use che.openshift.io as the hosting environment, although you could set up a local Che server if you prefer.

    Create the workspace

    Che 7 introduced the capability to define a development workspace in a YAML format called a devfile. Example devfiles can be found in the Red Hat Developers GitHub.

    For this post, we use a modified version of the Spring Boot getting started devfile, which adds the Jaeger all-in-one backend to the workspace. The main change is to add the following section just before the commands top-level node:

    -  
        type: dockerimage  
        alias: tracing  
        image: jaegertracing/all-in-one:latest  
        env:  
          - name: MEMORY_MAX_TRACES  
            value: "5000"  
          - name: COLLECTOR_ZIPKIN_HTTP_PORT  
            value: "9411"  
        memoryLimit: 128Mi  
        endpoints:  
          - name: 'tracing-ui'  
            port: 16686  
          - name: 'collector-grpc'  
            port: 14250  
            attributes:  
               public: 'false'  
          - name: 'collector-http'  
            port: 14268  
            attributes:  
               public: 'false'  
          - name: 'collector-zipkin'  
            port: 9411  
            attributes:  
               public: 'false'  
          - name: 'agent-config'  
            port: 5778  
            attributes:  
               public: 'false'  
          - name: '6831/udp'  
            port: 6831  
            attributes:  
               public: 'false'  
          - name: '6832/udp'  
            port: 6832  
            attributes:  
               public: 'false'  
        volumes:  
          - name: tmp  
            containerPath: /tmp
    

    The fully modified version of the devfile can be found here, with the additional memory limit changes required for using che.openshift.io.

    To start the workspace on che.openshift.io, point a browser to this url. Chrome is recommended due to issues on some versions of Firefox.

    Add OpenTracing instrumentation

    When the workspace is initially opened, the application has no OpenTracing instrumentation, as you can see in Figure 1:

    The initial workspace

    Figure 1: The initial workspace.">

    OpenTracing instrumentation can implicitly be added by including a dependency on opentracing-spring-jaeger-cloud-starter (shown in the updated pom.xml file in Figure 2), along with updating the spring-boot-starter-parent version to 2.2.0.RELEASE (which is required by the OpenTracing instrumentation):

    OpenTracing

    Figure 2: Adding the OpenTracing instrumentation.">

    This dependency automatically instruments the inbound and outbound HTTP requests. It also bootstraps the Jaeger tracer to report the tracing data to the Jaeger back end (included in the workspace). The default tracer configuration will report the data via UDP to the Jaeger agent, although the application can be configured to report the data via HTTP directly to the collector.

    The final step is to add a property that defines the service name within the tracing data. This goal is achieved by creating the src/main/resources folder and then creating the file application.properties with the contents shown in Figure 3:

    Figure 3: Defining the service name within the tracing data.">

    Trace the running application

    On the right side of the workspace is a cube symbol. When selected, this icon expands a tree. Under the User Runtimes/tools tree node is a task called run webapp. Selecting this option will run the Spring Boot application. When it starts, a window appears with the button Open Link as shown in Figure 4. Press this button to start a browser for the application.

    Figure 4: Opening a browser for the application.

    Figure 4: Opening a browser for the application.">

    In the same tree, select the User Runtimes/tracing option tracing-ui, which launches the Jaeger UI in a separate browser tab as shown in Figure 5:

    Launching a new browser tab for tracing

    Figure 5: Launching a new browser tab for tracing.">

    Press the refresh button at the top of the browser a couple of times to see the text Span reported in the console window, as shown at the bottom of Figure 6:

    Running application with console log showing spans being reported

    Figure 6: Running application with console log showing spans being reported.">

    Change to the Jaeger UI tab to see the resulting traces that were reported from the application, as shown in Figures 7 and 8:

    Figure 7: The completed traces.

    Figure 7: The completed traces.">

    Details for the first completed trace

    Figure 8: Details for the first completed trace.">

    Summary

    This article has shown how OpenTracing with Jaeger can easily be introduced into an Eclipse Che workspace so you can obtain tracing information from applications during development.

    This particular example is simple and only captures tracing from a single service. The benefit offered by Che is enabling complete applications (multiple services) to be used within the same workspace, thus producing more interesting traces and helping developers understand the performance of their developed service in the context of the complete application.

    Last updated: November 8, 2023

    Recent Posts

    • A day in the life of an NVIDIA H100 on Red Hat OpenShift 5

    • Migrate BuildConfigs to builds for Red Hat OpenShift with one plug-in install

    • Run Red Hat Enterprise Linux CoreOS on NVIDIA BlueField DPUs

    • Agent harness engineering: Separating model capabilities from enforcement

    • What's new for developers in Red Hat Enterprise Linux 10.3 and 9.9

    Red Hat Developers logo

    Platforms

    • Red Hat AI
    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform
    • See all products

    Build

    • Developer Sandbox
    • Developer tools
    • Interactive tutorials
    • API catalog

    Quicklinks

    • Learning resources
    • E-books
    • Cheat sheets
    • Blog
    • Events
    • Newsletter

    Communicate

    • About us
    • Contact sales
    • Find a partner
    • Report a website issue
    • Site status dashboard
    • Report a security problem

    Red Hat Developer

    Build here. Go anywhere.

    We serve the builders. The problem solvers who create careers with code.

    Join us if you’re a developer, software engineer, web designer, front-end designer, UX designer, computer scientist, architect, tester, product manager, project manager or team lead.

    Sign me up

    Red Hat legal and privacy links

    • About Red Hat
    • Jobs
    • Events
    • Locations
    • Contact Red Hat
    • Red Hat Blog
    • Inclusion at Red Hat
    • Cool Stuff Store
    • Red Hat Summit
    © 2026 Red Hat

    Red Hat legal and privacy links

    • Privacy statement
    • Terms of use
    • All policies and guidelines
    • Digital accessibility
    Ask AI