Metricbeat complains about lack of platinum license on standard install

[piotrp]

When xpack.enabled: true is used with the Elasticsearch module on a non-platinum cluster I get the message about ccr metricset, repeated every minute:

the CCR feature is available with a platinum or enterprise Elasticsearch license. You currently have a basic license. Either upgrade your license or remove the ccr metricset from your Elasticsearch module configuration.

I didn't have any metricsets manually configured, so I followed this advice and listed all of them execept for ccr, and I still got this warning.

Metricbeat 8.16.1, installed from official deb repository.

Configuration:

name: "nodename"

metricbeat.modules:
  - module: system
    enabled: false
  - module: elasticsearch
    xpack.enabled: true
    period: 10s
    hosts:
      - "http://127.0.0.1:9200"

output.elasticsearch:
    hosts: [ "http://127.0.0.1:9200" ]

There was a previous issue (#24059) that got closed without any solution, so feel free to reopen it and close mine.

[botelastic]

This issue doesn't have a Team:<team> label.

[PrplHaz4]

I'm running down the same path of troubleshooting this message. It's important to note that the current documentation states:

The elasticsearch module can be used to collect metrics shown in our Stack Monitoring UI in Kibana. To enable this usage, set xpack.enabled: true and remove any metricsets from the module’s configuration. Alternatively, run metricbeat modules disable elasticsearch and metricbeat modules enable elasticsearch-xpack.

Adding scope: node also does not resolve this message.

Per the text above, it sounds like removing xpack and adding individual metricsets (excluding ccr) should resolve the message, but I'm not sure it will continue to recognize them as the legacy fields, and am unsure of any other side effects that may have.