Ce contenu n'est pas disponible dans la langue sélectionnée.
Chapter 30. Using Metering on Streams for Apache Kafka
You can use the Metering tool that is available on OpenShift to generate metering reports from different data sources. As a cluster administrator, you can use metering to analyze what is happening in your cluster. You can either write your own, or use predefined SQL queries to define how you want to process data from the different data sources you have available. Using Prometheus as a default data source, you can generate reports on pods, namespaces, and most other OpenShift resources.
You can also use the OpenShift Metering operator to analyze your installed Streams for Apache Kafka components to determine whether you are in compliance with your Red Hat subscription.
To use metering with Streams for Apache Kafka, you must first install and configure the Metering operator on OpenShift Container Platform.
30.1. Metering resources
Metering has many resources which can be used to manage the deployment and installation of metering, as well as the reporting functionality metering provides. Metering is managed using the following CRDs:
| Name | Description |
|---|---|
|
| Configures the metering stack for deployment. Contains customizations and configuration options to control each component that makes up the metering stack. |
|
| Controls what query to use, when, and how often the query should be run, and where to store the results. |
|
|
Contains the SQL queries used to perform analysis on the data contained within |
|
| Controls the data available to ReportQueries and Reports. Allows configuring access to different databases for use within metering. |
30.2. Metering labels for Streams for Apache Kafka
The following table lists the metering labels for Streams for Apache Kafka infrastructure components and integrations.
| Label | Possible values |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Infrastructure
|
| Application
| |
|
|
|
Examples
Infrastructure example (where the infrastructure component is entity-operator)
com.company=Red_Hat rht.prod_name=Red_Hat_Application_Foundations rht.prod_ver=2024.Q2 rht.comp=AMQ_Streams rht.comp_ver=2.7 rht.subcomp=entity-operator rht.subcomp_t=infrastructure
Application example (where the integration deployment name is kafka-bridge)
com.company=Red_Hat rht.prod_name=Red_Hat_Application_Foundations rht.prod_ver=2024.Q2 rht.comp=AMQ_Streams rht.comp_ver=2.7 rht.subcomp=kafka-bridge rht.subcomp_t=application
