Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add dedicated policy for agents started through the vm extension #11

Closed
Tracked by #108456
narph opened this issue Jun 1, 2021 · 0 comments · Fixed by #47
Closed
Tracked by #108456

Add dedicated policy for agents started through the vm extension #11

narph opened this issue Jun 1, 2021 · 0 comments · Fixed by #47
Assignees
Labels
enhancement New feature or request Team:Cloud-Monitoring Label for the Cloud Monitoring team

Comments

@narph
Copy link
Contributor

narph commented Jun 1, 2021

We had some issues with the renaming of Default policies that we can avoid by creating a dedicated policy inside the install process of the vm extension and enrolling the agent to it.

  • investigate if this could be done with the current kibana fleet apis
  • could be named azure-vm-extension-policy and contain the system integration.
  • a check will be done if the policy exists first and then create if not
@narph narph self-assigned this Jun 1, 2021
@narph narph added enhancement New feature or request Team:Obs-DC Label for the Data Collection team Team:Platforms Label for the Integrations - Platforms team labels Jun 1, 2021
@masci masci unassigned narph Jan 20, 2022
@kaiyan-sheng kaiyan-sheng self-assigned this Jan 20, 2022
@masci masci added Team:Cloud-Monitoring Label for the Cloud Monitoring team and removed Team:Platforms Label for the Integrations - Platforms team Team:Obs-DC Label for the Data Collection team labels Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Team:Cloud-Monitoring Label for the Cloud Monitoring team
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants