Skip to content

Latest commit

 

History

History
73 lines (59 loc) · 3.01 KB

README.md

File metadata and controls

73 lines (59 loc) · 3.01 KB

PoC usecase

demofigure

The PoC demonstrates two edges connected to a central cloud. Each edge comprises of metric generator whose metrics are scraped by prometheus. The prometheus does a remote write to thanos (running in the central cloud) for long term storage and analysis. The remote write is intercepted by our processor proxy running at each edge location. The processor applies various transformation to the collected metrics.

In this PoC we showcase how our controller generate insights that trigger pruning of metrics based on similarity across east and west edge/clouds.

Environment Setup

The PoC requires docker installed on the machine to test the scenario. The following containers get installed when the PoC environment is bought up.
Central containers:

  • thanos-receive
  • thanos-query
  • thanos-ruler
  • ruler-config
  • alertmanager
  • controller
  • manager
    Edge containers:
  • metricgen1,2
  • prometheus1,2
  • pmf_processsor1,2

Running the PoC story

  1. Bring up the PoC environment
make start

or

docker-compose -f docker-compose-quay.yml up -d
  1. Confirm that the metrics are available in thanos query UI http://127.0.0.1:19192:

The following metrics should be available: k8s_pod_network_bytes or nwdaf_5G_network_utilization.

There should be a single metric for each edge, hence a total of four metrics.

  1. Next, we trigger the controller to draw insights
make perform_analysis

or via the manager API.
http://127.0.0.1:5010/apidocs/#/Controller/post_api_v1_analyze

  1. Verify the generated insights in the Controller UI: http://127.0.0.1:5000/insights
    Click Insights details 3 and the analysis should show three metrics:
    k8s_pod_network_bytes($app,c0,metricgen2:8001,west,$IP)
    nwdaf_5G_network_utilization(analytic_function,c0,metricgen1:8000,east,$IP)
    nwdaf_5G_network_utilization(analytic_function,c0,metricgen2:8001,west,$IP)
    Those metrics are analyzed as correlated with k8s_pod_network_bytes.

  2. The insights can be used just as a recommendation or for full-automation where corresponding transform will be applied to each edge to handle the pruning. In this POC we demonstrate the full automation mode.

  3. The controller triggers transformation in each cloud which can be seen using the manager UI:
    Access http://127.0.0.1:5010/apidocs/#/Processor%20Configuration/getProcessorConfig.
    Use east and west in the UI combo box as the processor ids to check transformation added to individual clouds.

  4. You can visualize the change in the metrics values: Execute the query k8s_pod_network_bytes or nwdaf_5G_network_utilization) in the thanos query UI (in graph mode).
    You will see only k8s_pod_network_bytes with label processor="east" flowing. Other analyzed as similar metrics are now being pruned/dropped.

  5. To end the POC and clean docker execute:

make end

or

docker-compose -f docker-compose-quay.yml down