Skip to content

Latest commit

 

History

History
135 lines (99 loc) · 5.42 KB

README.md

File metadata and controls

135 lines (99 loc) · 5.42 KB
Raw

Openshift Reporting Backend

OpenShift Reporting uses metering operator as backend.

More Details about Metering Operator Metering Operator

Prerequisites

  1. OpenShift Account as Cluster Administrator

  2. Locally downloaded OpenShift Cluster CRC. Refer this CRC for Openshift Reporting Backend.

  3. Enable Alerting,monitoring, telemetry on CRC cluster using following commands

oc scale --replicas=1 statefulset --all -n openshift-monitoring; 
oc scale --replicas=1 deployment --all -n openshift-monitoring

Note: if the above commands donot work, Please refer CRC for Openshift Reporting Backend under 'Error in starting Monitoting, Telemetry and Alerting Section'

Installation

  1. Clone the repository in your local machine.

  2. Make the installation.sh and report.sh file executable using -

chom +x <.sh file name>
  1. Run the installation script file with command -
./installation.sh

Every steps tells you what it does and print the output of each command on terminal after it's executed.

Expected output of few commands is mentioned here Script Details

Creating Reports

For Now, lets use the pre-defined reportdatasources and reportqueries to generate our first report

$ oc project openshift-metering
$ oc create -f https://raw.githubusercontent.com/dburugupalli/SSMT/feature-1/openshift-metering-templates/reports-templates/namespace-cpu-request-hourly.yaml

To view reports on the terminal. Run report.sh file.

./report.sh

Defining Report-Query and ReportDataSources to acheive specific functionality

What if we want to define our own reportquery and reportdatasource custom resources, to achieve specific functionality ?

Yes, We can define our own reportquery and reportdatasource

Define Reportdatasource custom resource,

it contains PromQL queries. We can write our own promQL queries to create datasource and achieve our functionality

...
spec:
  prometheusMetricsImporter:
    query: |
      sum(kube_pod_container_resource_requests_cpu_cores) by (pod, namespace, node)
.....
Define ReportQuery custom resource

if you inspect one reportquery custom resource, it contains SQL like queries. We can write our own SQL queries to achieve specific purpose. Presto Database provides functionality to execute SQL like queries. Presto has a dependency on Hive, and uses Hive for keeping metadata about the data Presto is working with.

oc edit reportquery pod-cpu-request
# output
# it takes various parameters as inputs, if we observe the yaml template
....
  query: |
    SELECT
      timestamp '{| default .Report.ReportingStart .Report.Inputs.ReportingStart| prestoTimestamp |}' AS period_start,
      timestamp '{| default .Report.ReportingEnd .Report.Inputs.ReportingEnd | prestoTimestamp |}' AS period_end,
      pod,
      namespace,
      node,
      sum(pod_request_cpu_core_seconds) as pod_request_cpu_core_seconds
    FROM {| dataSourceTableName .Report.Inputs.PodCpuRequestRawDataSourceName |}
    WHERE "timestamp" >= timestamp '{| default .Report.ReportingStart .Report.Inputs.ReportingStart | prestoTimestamp |}'
    AND "timestamp" < timestamp '{| default .Report.ReportingEnd .Report.Inputs.ReportingEnd | prestoTimestamp |}'
    AND dt >= '{| default .Report.ReportingStart .Report.Inputs.ReportingStart | prometheusMetricPartitionFormat |}'
    AND dt <= '{| default .Report.ReportingEnd .Report.Inputs.ReportingEnd | prometheusMetricPartitionFormat |}'
    GROUP BY namespace, pod, node
    ORDER BY namespace, pod, node ASC, pod_request_cpu_core_seconds DESC
...

Above queries gets the data in descending order. Lets, Define SQL query to get data in ascending order4

To get the data in ascending order, execute the following commands

oc delete reportquery pod-cpu-request
oc create -f https://raw.githubusercontent.com/dburugupalli/SSMT/feature-1/openshift-metering-templates/reportquery-templates/create-pod-cpu-request-reportquery.yaml

When the report is created, data will be populated in ascending order

Start the Flask web server using the following commands
# Create list-v1-projects-hourly report and reportquery 
oc create -f https://raw.githubusercontent.com/dburugupalli/SSMT/master/openshift-metering-templates/reportquery-templates/list-all-projects-v1-reportquery.yaml
oc create -f https://raw.githubusercontent.com/dburugupalli/SSMT/master/openshift-metering-templates/reports-templates/list-all-projects-v1-hourly.yaml
# Wait for some time untilhttps://raw.githubusercontent.com/dburugupalli/SSMT/feature2/openshift-metering-templates/reports-templates/list-all-projects-v1-hourly.yaml reports get generated.
# Install the python dependencies
pip install flask 
pip install flask_cors
pip install requests
# Set the Environment variables
. config.sh 
# Start the backend appplication server.
python3 app.py

Contributing

Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.

Please make sure to update tests as appropriate.