[ERROR][plugins.monitoring.monitoring] Could not find license information for cluster = 'mylogging'. Please check the cluster's master node server logs for errors or warnings

Elastic Stack Kibana
1

I am upgrading my elasticsearch stack hosted on an AKS cluster. The cluster is running with basic license. Everything seemed fine with 8.19.17. But after I upgraded to 9.4.2, kibana is throwing out following error (when I am viewing stact monitoring page).

[ERROR][plugins.monitoring.monitoring] Could not find license information for cluster = 'mylogging'. Please check the cluster's master node server logs for errors or warnings

However, I can see this popup message in UI from time to time:

Monitoring Request Error

Monitoring License Error: Could not find license information for cluster = 'mylogging'. Please check the cluster's master node server logs for errors or warnings.

HTTP 503

In kibana pod log, I can see:

[2026-06-30T18:38:14.515+00:00][ERROR][plugins.monitoring.monitoring] Could not find license information for cluster = 'mylogging'. Please check the cluster's master node server logs for errors or warnings.
[2026-06-30T18:38:14.516+00:00][ERROR][plugins.monitoring.monitoring] MonitoringLicenseError: Monitoring License Error
    at /usr/share/kibana/node_modules/@kbn/monitoring-plugin/server/lib/cluster/get_clusters_summary.js:44:13
    at Array.map (<anonymous>)
    at getClustersSummary (/usr/share/kibana/node_modules/@kbn/monitoring-plugin/server/lib/cluster/get_clusters_summary.js:18:19)
    at getClustersFromRequest (/usr/share/kibana/node_modules/@kbn/monitoring-plugin/server/lib/cluster/get_clusters_from_request.js:199:55)
    at processTicksAndRejections (node:internal/process/task_queues:104:5)
    at Object.handler (/usr/share/kibana/node_modules/@kbn/monitoring-plugin/server/routes/api/v1/cluster/cluster.js:49:26)
    at handler (/usr/share/kibana/node_modules/@kbn/monitoring-plugin/server/plugin.js:330:28)
    at handle (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/src/route.js:126:26)
    at handler (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/src/route.js:47:14)
    at Router.handle (/usr/share/kibana/node_modules/@kbn/core-http-router-server-internal/src/router.js:133:30)
    at exports.Manager.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/toolkit.js:60:28)
    at Object.internals.handler (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:46:20)
    at exports.execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/handler.js:31:20)
    at Request._lifecycle (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:384:32)
    at Request._execute (/usr/share/kibana/node_modules/@hapi/hapi/lib/request.js:294:9)

I am not seeing license related in master node logs. Also following check seems good to me:

GET /_license
{
  "license": {
    "status": "active",
    "uid": "95f7762f-18d0-4e4d-857b-b09259a5ae14",
    "type": "basic",
    "issue_date": "2026-06-03T19:05:15.971Z",
    "issue_date_in_millis": 1780513515971,
    "max_nodes": 1000,
    "max_resource_units": null,
    "issued_to": "mylogging",
    "issuer": "elasticsearch",
    "start_date_in_millis": -1
  }
}
GET .ds-metrics-elasticsearch.stack_monitoring.cluster_stats-default-2026.06.29-000002/_search
{
  "size": 1,
  "_source": false,
  "fields": [
    "cluster_uuid",
    "license.type",
    "license.status"
  ],
  "query": {
    "exists": {
      "field": "elasticsearch.cluster.stats.license.type"
    }
  },
  "sort": [
    {
      "@timestamp": "desc"
    }
  ]
}

{
  "took": 3,
  "timed_out": false,
  "_shards": {
    "total": 1,
    "successful": 1,
    "skipped": 0,
    "failed": 0
  },
  "hits": {
    "total": {
      "value": 7148,
      "relation": "eq"
    },
    "max_score": null,
    "hits": [
      {
        "_index": ".ds-metrics-elasticsearch.stack_monitoring.cluster_stats-default-2026.06.29-000002",
        "_id": "npLhGZ8Bzpb2wiCDdzJu",
        "_score": null,
        "fields": {
          "cluster_uuid": [
            "rHuqVISrSOi0b_HAXp-JYw"
          ],
          "license.status": [
            "active"
          ],
          "license.type": [
            "basic"
          ]
        },
        "sort": [
          1782845632575
        ]
      }
    ]
  }
}

Is there a problem with kbn/monitoring-plugin/server/lib/cluster/get_clusters_summary.js? or it is something I missed?

Has anyone run into this or similar issue? Can someone help to take a look please?

Thanks

2

I am running one kibana pod. Actually, sometimes kibana actually does return 200 and good metrics data, which is even more confusing. I am running 3 master pods and the cluster is healthy according to:

{
  "cluster_name" : "mylogging",
  "status" : "green",
  "timed_out" : false,
  "number_of_nodes" : 6,
  "number_of_data_nodes" : 3,
  "active_primary_shards" : 200,
  "active_shards" : 378,
  "relocating_shards" : 0,
  "initializing_shards" : 0,
  "unassigned_shards" : 0,
  "unassigned_primary_shards" : 0,
  "delayed_unassigned_shards" : 0,
  "number_of_pending_tasks" : 0,
  "number_of_in_flight_fetch" : 0,
  "task_max_waiting_in_queue_millis" : 0,
  "active_shards_percent_as_number" : 100.0
}