[jira] [Updated] (MINIFICPP-1851) Add a processor to gather cluster-level pod metrics in Kubernetes, from inside the cluster

["Ferenc Gerlits (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MINIFICPP-1851?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ferenc Gerlits updated MINIFICPP-1851:
--------------------------------------
    Fix Version/s: 0.13.0

> Add a processor to gather cluster-level pod metrics in Kubernetes, from inside the cluster
> ------------------------------------------------------------------------------------------
>
>                 Key: MINIFICPP-1851
>                 URL: https://issues.apache.org/jira/browse/MINIFICPP-1851
>             Project: Apache NiFi MiNiFi C++
>          Issue Type: New Feature
>            Reporter: Marton Szasz
>            Assignee: Ferenc Gerlits
>            Priority: Major
>             Fix For: 0.13.0
>
>
> One may want to run minifi in a kubernetes cluster and use it to gather various metrics about the pods running there. A good first convenience processor could be one that gathers data from /apis/metrics.k8s.io/v1beta1/pods. It would be like a wrapper for InvokeHTTP, or just an HTTPClient, to get the necessary data with automatic API access from inside the cluster.
> There is no similar processor in NiFi. My first idea for a name is CollectKubernetesPodMetrics.
> Alternatively, add two separate entities: KubernetesPodMetrics, to the pattern of our internal metrics that are exported over C2, and CollectMetrics that takes an arbitrary metrics class and collects the metrics on every trigger. This would be easier to extend in the future with more metrics.
> Is it feasible to allow querying different metrics, or to add filtering capabilities?



--
This message was sent by Atlassian Jira
(v8.20.7#820007)