Rename Elasticsearch clusters created by Extension

[siavash1996]

I've set up the Elasticsearch extension to monitor several of our Elastic Cloud endpoints, each one belonging to a different environment, but now I've run into the issue that the cluster names that have been assigned are the cluster ID from Elastic, rather than the cluster name. This has created a situation where it's impossible to tell which cluster each entity belongs to without clicking through several pages to get tags or the extension configuration name.

I thought I could pretty simply update the display name with the monitored entities API, but that just seems to create brand new custom services, even when I pass the same entityID through the API.

How can I rename these remotely-monitored Elasticsearch cluster instances?

[Mike_L · Accepted solution]

You can’t do that without forking the extension and changing the generic entity rules and pass in additional dimensions through the code to fill in the required names.

Maybe raise a product idea on renaming generic entities in general.

[dt-moviri]

Hi @siavash1996 the Elasticsearch extension uses the "cluster" dimension to create these entity names. This "cluster" dimension comes directly from "cluster_name" field returned from the Elasticsearch api - specifically the "/_cluster/health" endpoint. The entity names shouldn't be the cluster UUID unless each cluster's name is also their UUID. Are you able to see the cluster name if you perform a request to the "/_cluster/health" endpoint? If the result shows the UUID in the "cluster_name" field then you may need to rename the clusters.

Regards,
Loucas