We have a mapping problem where we have multiple K8s clusters with duplicate namespaces (AAAA-system, observability, security, etc.) Finding the corresponding namespace means matching both the cluster the namespace belongs to and the namespace, which doesn't seem to be possible with the current relationship mapping as it involves three entities (application, namespace, cluster) where application -> cluster, application -> namespace and namespace-> cluster is the set of required relationships where the cluster must be the same

The feature described here would be super useful for custom API integrations where you don't necessarily know the specific identifiers for a relation at entity creation time. The added feature for setting relation based on search query is great for ocean integrations, but it doesn't seem to have the same functionality for API integrations.

👋🏼 we didn't do this exact feature, but we did release setting relation based on search queries - which should help achieving similar flows when configuring data sources mappings

this would be super helpful as at this moment there is a burden on an entity to know the identities of the related entities at ingested time. I currently am relying on a naming schema (e.g. using the k8s exporter to ingest data about deployments and link them to related entities) to avoid having to run secondary scripts to query the api and link those relations