[Observability - Uptime - Synthetics] Monitor Management - Usage Agent Policy Default Namespace and Default Namespace

[BenB196]

Describe the feature:

When creating a new Monitor under Monitor Management, I would like for the Data stream namespace to default to the default namespace of the agent policy being used. When creating multiple monitors, I would like to not need to manually change the namespace being setup, when I've already set my preferred namespace at the Agent policy level.

Describe a specific use case for the feature:

I use namespaces to segment data based on environment. This helps with having varying retention policies (via ILM). When I need to create new Monitors I need to remember that I need to change the namespace, or else they will all use default.

[elasticmachine]

Pinging @elastic/uptime (Team:uptime)

[elasticmachine]

Pinging @elastic/obs-ux-management-team (Team:obs-ux-management)

[dominiqueclarke]

Hi @BenB196 ,

Currently, the Kibana space id is used as the default namespace for synthetics datastreams.

However, when the namespace is default it falls back to the agent policy namespace. That means that monitors saved in the default Kibana space automatically fall back to the agent policy namespace, whereas monitors that are saved in other Kibana spaces will utilize the id of that space as their namespace without falling back to the agent policy namespace.

Is this desired behavior for you? Or would you prefer your monitors to respect the agent policy namespace, regardless of the Kibana space they are saved in.

[BenB196]

Hi @dominiqueclarke in our case, I think we'd prefer monitors to respect the agent policy namespace. The way we use namespaces is like an additional RBAC layer, that is tied to the data and not to the Kibana namespace, where we have agent policy namespaces like:

• public.default.development
• private.default.development
• public.default.production
• private.default.production

This allows us to more finely control who can access what more easily. With the current default of using Kibana space name, we've had issues where people forget to update the namespace, and it results in users not being able to correctly access data.