Skip to main content
Redhat Developers  Logo
  • Products

    Featured

    • Red Hat Enterprise Linux
      Red Hat Enterprise Linux Icon
    • Red Hat OpenShift AI
      Red Hat OpenShift AI
    • Red Hat Enterprise Linux AI
      Linux icon inside of a brain
    • Image mode for Red Hat Enterprise Linux
      RHEL image mode
    • Red Hat OpenShift
      Openshift icon
    • Red Hat Ansible Automation Platform
      Ansible icon
    • Red Hat Developer Hub
      Developer Hub
    • View All Red Hat Products
    • Linux

      • Red Hat Enterprise Linux
      • Image mode for Red Hat Enterprise Linux
      • Red Hat Universal Base Images (UBI)
    • Java runtimes & frameworks

      • JBoss Enterprise Application Platform
      • Red Hat build of OpenJDK
    • Kubernetes

      • Red Hat OpenShift
      • Microsoft Azure Red Hat OpenShift
      • Red Hat OpenShift Virtualization
      • Red Hat OpenShift Lightspeed
    • Integration & App Connectivity

      • Red Hat Build of Apache Camel
      • Red Hat Service Interconnect
      • Red Hat Connectivity Link
    • AI/ML

      • Red Hat OpenShift AI
      • Red Hat Enterprise Linux AI
    • Automation

      • Red Hat Ansible Automation Platform
      • Red Hat Ansible Lightspeed
    • Developer tools

      • Red Hat Trusted Software Supply Chain
      • Podman Desktop
      • Red Hat OpenShift Dev Spaces
    • Developer Sandbox

      Developer Sandbox
      Try Red Hat products and technologies without setup or configuration fees for 30 days with this shared Openshift and Kubernetes cluster.
    • Try at no cost
  • Technologies

    Featured

    • AI/ML
      AI/ML Icon
    • Linux
      Linux Icon
    • Kubernetes
      Cloud icon
    • Automation
      Automation Icon showing arrows moving in a circle around a gear
    • View All Technologies
    • Programming Languages & Frameworks

      • Java
      • Python
      • JavaScript
    • System Design & Architecture

      • Red Hat architecture and design patterns
      • Microservices
      • Event-Driven Architecture
      • Databases
    • Developer Productivity

      • Developer productivity
      • Developer Tools
      • GitOps
    • Secure Development & Architectures

      • Security
      • Secure coding
    • Platform Engineering

      • DevOps
      • DevSecOps
      • Ansible automation for applications and services
    • Automated Data Processing

      • AI/ML
      • Data Science
      • Apache Kafka on Kubernetes
      • View All Technologies
    • Start exploring in the Developer Sandbox for free

      sandbox graphic
      Try Red Hat's products and technologies without setup or configuration.
    • Try at no cost
  • Learn

    Featured

    • Kubernetes & Cloud Native
      Openshift icon
    • Linux
      Rhel icon
    • Automation
      Ansible cloud icon
    • Java
      Java icon
    • AI/ML
      AI/ML Icon
    • View All Learning Resources

    E-Books

    • GitOps Cookbook
    • Podman in Action
    • Kubernetes Operators
    • The Path to GitOps
    • View All E-books

    Cheat Sheets

    • Linux Commands
    • Bash Commands
    • Git
    • systemd Commands
    • View All Cheat Sheets

    Documentation

    • API Catalog
    • Product Documentation
    • Legacy Documentation
    • Red Hat Learning

      Learning image
      Boost your technical skills to expert-level with the help of interactive lessons offered by various Red Hat Learning programs.
    • Explore Red Hat Learning
  • Developer Sandbox

    Developer Sandbox

    • Access Red Hat’s products and technologies without setup or configuration, and start developing quicker than ever before with our new, no-cost sandbox environments.
    • Explore Developer Sandbox

    Featured Developer Sandbox activities

    • Get started with your Developer Sandbox
    • OpenShift virtualization and application modernization using the Developer Sandbox
    • Explore all Developer Sandbox activities

    Ready to start developing apps?

    • Try at no cost
  • Blog
  • Events
  • Videos

Cryostat cluster-wide Java profiling

July 4, 2023
Andrew Azores
Related topics:
Java
Related products:
Red Hat build of Cryostat

Share:

    Cryostat 2.3 includes another popular community-requested feature: multi-namespace support*. With this release it is now possible to deploy a single Cryostat instance for monitoring and profiling Java application instances across all of your OpenShift projects, whereas previous Cryostat releases required you to deploy one Cryostat instance into each project. This is the first half of multi-tenant support in Cryostat.

    * Kubernetes Namespaces are referred to as Projects in OpenShift Container Platform (OCP).

    Before I continue, there is an important caveat to be aware of with this initial support. Cryostat 2.3 can be deployed such that it discovers target applications in multiple projects, but it does not silo the data. What this means is that any user who can access the Cryostat instance has access to all target applications in any project visible to that Cryostat instance. When deploying a multi-namespace Cryostat instance, administrators must be careful and considerate about which projects to select for monitoring, which project to install Cryostat into, and which users to grant access.

    In order to deploy a new multi-namespace-enabled instance, users can create a new ClusterCryostat Custom Resource (CR) in OCP after installing or updating the Cryostat Operator. The old Cryostat CR is still available and is used for creating single-namespace Cryostat instances. The Cryostat Operator will warn the user and fail the deployment if there is a collision between a Cryostat CR namespace and the installation namespace or target namespaces of any ClusterCryostat CR.

    The installation namespace of a ClusterCryostat is straightforward - it is the namespace (OpenShift Project) into which the Cryostat Operator will create a Deployment, Service, etc. for Cryostat and its associated components. This namespace should be separate from the target application(s), ideally reserved for the ClusterCryostat instance alone, and RBAC permissions within this installation namespace are how administrators can control which users have access to the instance.

    The target namespaces of a ClusterCryostat are simply those namespaces within which the Cryostat instance attempts to discover target applications. This is still done in the Cryostat conventional way of querying for Kubernetes Endpoints objects that have a port with either the name jfr-jmx or the number 9091. This list of target namespaces may also optionally include the installation namespace, if you want Cryostat to be able to discover its own components as applications to be monitored.

    What if the conventional Endpoints name and number querying mechanism does not suit your application deployment scenario? In this case, I recommend you use the new Cryostat Agent to instrument your workload containers. This is an easy to use implementation of the Cryostat Discovery Plugin API from the last 2.2.0 release, which also works across namespaces. If you exclusively use the Discovery Plugin API (via the Agent or otherwise) then you may choose to leave the target namespaces list empty. Otherwise, an application container could be discovered both via the Discovery Plugin and via Endpoint querying. This is generally harmless but may be cluttered and confusing.

    If the Endpoints query-based discovery does suit your deployment scenario, why should you consider creating a ClusterCryostat rather than a simple Cryostat? This mainly comes down to overhead and operating costs. If your application deployment spans multiple namespaces, or if you have a team of developers with their own individual workspace namespaces (and no concerns about data visibility across them), then choosing to install a single ClusterCryostat rather than many Cryostats can add up to significant memory overhead savings and more efficient utilization of resources.

    Cryostat single-namespace deployment graph
    Cryostat sharing a single namespace with the workload applications it monitors
    Cryostat multi-namespace deployment graph
    Cryostat deployed in its own namespace, monitoring application workload containers in other namespaces
    Last updated: August 12, 2024
    Disclaimer: Please note the content in this blog post has not been thoroughly reviewed by the Red Hat Developer editorial team. Any opinions expressed in this post are the author's own and do not necessarily reflect the policies or positions of Red Hat.

    Recent Posts

    • More Essential AI tutorials for Node.js Developers

    • How to run a fraud detection AI model on RHEL CVMs

    • How we use software provenance at Red Hat

    • Alternatives to creating bootc images from scratch

    • How to update OpenStack Services on OpenShift

    Red Hat Developers logo LinkedIn YouTube Twitter Facebook

    Products

    • Red Hat Enterprise Linux
    • Red Hat OpenShift
    • Red Hat Ansible Automation Platform

    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

    Red Hat legal and privacy links

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

    Report a website issue