topic Re: Bucket assign configuration matcher field question in Open Q&A

Bucket assign configuration matcher field question

dynatrace_curio — Tue, 23 Dec 2025 14:43:42 GMT

Hello everybody,

I'm trying to configure the bucket assignment to extend the log retention period to all kubernetes associated to this following query. Is it possible to fit this query in the matcher field?

fetch dt.entity.cloud_application_namespace
| filter in(id, classicEntitySelector(concat("type(CLOUD_APPLICATION_NAMESPACE),toRelationship.isClusterOfNamespace(type(KUBERNETES_CLUSTER),entityName.equals(<Entity_Name>))")))
| fieldsFlatten cloudApplicationLabels, fields: {`field.cattle.io/projectId`}
| filter `field.cattle.io/projectId` == "<project_ID_number>"

Thank you very much

Re: Bucket assign configuration matcher field question

PierreGutierrez — Sun, 04 May 2025 04:06:47 GMT

Hi @dynatrace_curio
I haven't tested that you can apply classicEntitySelector in the DQL Matcher, but I doubt it's possible.

I haven't tested whether you can apply classicEntitySelector to the DQL Matcher, but I doubt it's possible.

I suggest adding a unique log value for the entity (like the Project ID you're already using) to make it more maintainable over time and easier to understand.

Then continue with what the documentation indicates that it can be done.

More Info : https://docs.dynatrace.com/docs/shortlink/lma-log-processing-matcher