Pod and Prometheus service relationship

[maxa101]

Relevant information

Stg Implementation for the following

• Invert the Lookup to be based on EXT Prometheus service metrics instead of Pod (will remove individual candidates in a future PR)
• Standardize the k8s attributes used for candidates lookup (support both otel and prometheus conventions) for Pod

Checklist

• I've read the guidelines and understand the acceptance criteria.
• The value of the attribute marked as identifier will be unique and valid.
• I've confirmed that my entity type wasn't already defined. If it is I'm providing an explanation above.

[entityBot]

beep boop bop.

I have found some errors processing these changes:

* Error VALIDATING domainType: 'EXT-COREDNS' on synthesis - Exception: No entity matches 'EXT-COREDNS' synthesis rules for the given test data: 'MetricOtel.json file - #1' data point. Please review test data and synthesis rules.

Let's validate those changes.

[entityBot]

beep boop bop.

I have found some errors processing these changes:

* Error VALIDATING domainType: 'EXT-COREDNS' on synthesis - Exception: No entity matches 'EXT-COREDNS' synthesis rules for the given test data: 'MetricOtel.json file - #1' data point. Please review test data and synthesis rules.

Dismissing reviews