How Do I Check Whether a Custom Tag Key of a Resource Conflicts with a Built-in Tag Key of cloudeye-exporter?

Symptom

If the custom tag key of a resource is the same as the built-in tag key of the data exported by cloudeye-exporter, the metric data of the resource cannot be exported.

Solution

1. Log in to the server where cloudeye-exporter is deployed as user root.
2. Go to the directory where cloudeye-exporter is located.
3. View the error information in the cloudeye-exporter run log.

   grep "Duplicate label names were found" server.log

   If the following information is displayed, a tag key conflict occurs. You can locate the cloud service, resource instance, and tag key based on the log information:

   [xxx] Duplicate label names were found between custom tags and system tags and the metrics export is skipped for this resource(namespace: {Service namespace}, dimensions info: {Dimension information},  labels: {Conflicting tag name}).

   Table 1 Log parameters

   Parameter	Description	Example Value
   namespace	Namespace of the cloud service where the duplicate custom tag key is used, which is used to locate the cloud service where the fault occurs.	SYS.ECS
   dimensions info	Dimension information of the resource using the duplicate custom tag key, which is used to locate the resource.	&[MetricsDimension {"name":"instance_id","value":"9fd995cb-67a1-4b4a-9a10-df48489e****"}]
   labels	Duplicate custom tag key, which is used to confirm the custom tag to be modified.	hostIP,epName,hostname

4. Modify the custom tag of the resource. For details, see Modifying Resource Tags.
5. Restart cloudeye-exporter and ensure that no error information is generated in the run log.
6. View the monitoring data of the resource on the third-party monitoring platform.