Can we have Elastic agent policy for Dev and Prod Environments

We were using beat prior to elastic agent. Now our requirement is Elastic agent to provision on dev and prod instances.

I have gone thru the documentation process of how to setup and configure Elastic agent on remote host but that pop up few queries in my mind which are referring below.

  1. Do we have to use multiple policies for each and every environment or can we have single policy which can used as common and uses variable.
  2. There is an option called "Namespace" which we see during configuiring agent policy. Will that work or not?
  3. Can we use modules which were being used by metricbeats. Can we use the same modules by elastic agent, if yes, then how?
  4. Considerations on how to implement variables like we do now (eg. fields.env, any tags, etc)
  5. Consideration of using different policies for other teams with different needs (eg. filebeat configured for logs in different locations, etc)

Any suggestion will be helpful.

I believe multiple policies is the standard way when working with 8.x

@lesio, thanks for reply and yes I am aware about multiple policies approach however I want to know whether is it possible to have single policy and use it for other envs accordingly.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.