Resolved the monitoring issue for krakend

[Rohan Shahi]

Hi Albert and Daniel,

Thank you for your responses.

I have successfully resolved the issue of monitoring Krakend using Prometheus and Grafana. The solution involved configuring the ConfigMap with the appropriate settings, as detailed below:

---
"extra_config": {
        "telemetry/metrics": {
          "collection_time": "60s",
          "proxy_disabled": false,
          "router_disabled": false,
          "backend_disabled": false,
          "endpoint_disabled": false,
          "listen_address": ":8090"
        },
"telemetry/opentelemetry": {
          "service_name": "krakend_prometheus_service",
          "metric_reporting_period": 1,
          "exporters": {
            "prometheus": [
              {
                "name": "local_prometheus",
                "port": 9091,
                "process_metrics": true,
                "go_metrics": true
              }
            ]
          }
        }
      },
----

As per the documentation here, these changes ensure proper integration with Prometheus and Grafana.

Additionally:

1. The Krakend service needs to expose the metrics on port 9091. Metrics can be accessed at http://<krakend-svc-ip>:9091/metrics.
2. Please ensure the Krakend service endpoint is validated and open for port 9091 to allow proper access.
   
   Validate the dasboards in prometheus and grafana
   

GRAFANA