[
https://issues.apache.org/jira/browse/NIFI-15034?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Koldo updated NIFI-15034:
-------------------------
Issue Type: Bug (was: New Feature)
> Access to nifi-api/flow/metrics/prometheus
> ------------------------------------------
>
> Key: NIFI-15034
> URL: https://issues.apache.org/jira/browse/NIFI-15034
> Project: Apache NiFi
> Issue Type: Bug
> Components: Docker, NiFi API
> Affects Versions: 2.5.0
> Reporter: Koldo
> Priority: Major
>
> Hello, I am deploying Nifi on Kubernetes through the Docker image. In this
> deployment, I have configured OIDC, so it has to go through HTTPs.
> Now I want to monitor the metrics that are exposed in the path
> /nifi-api/flow/metrics/prometheus with Open Telemetry. To test that it
> receives the metrics correctly, I have used the following configuration:
> ```
> prometheus:
> config:
> scrape_configs:
> \- job_name: nifi-metrics
> scrape_interval: 10s
> scheme: https
> metrics_path: /nifi-api/flow/metrics/prometheus
> authorization:
> type: Bearer
> credentials:
> tls_config:
> insecure_skip_verify: true
> static_configs:
> \- targets: [pruebas.argocd.svc.cluster.local:8082]
> ```
> In the credentials, I have entered a JWT token that I generated manually when
> accessing the Nifi UI, but it expires. Is there a way to have a Nifi access
> token that does not expire? Or, to configure this path so that it does not
> require authentication?
> The idea would be for OTLP to be able to obtain the metrics over time without
> having to renew this token.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
