[Metadata][Processor] Elastic Agent + VMware Metadata
- Dominant language
- Go
- Stars
- 12.7k
- Forks
- 5k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 385
Description
**Describe the enhancement:**
Add a new processor (similar to add_cloud_metadata) to add from virtual stack provider
**Describe a specific use case for the enhancement or feature:**
As a user, we don't have all of our hosts/elastic agent in the cloud, and more metadata driven fields, like which vcenter the host/elastic agent its located in.
**What is the definition of done?**
The inclusion of VMware metadata fields that can help with observability use cases.
Contributor guide
Research direction
Start by reviewing the existing add_cloud_metadata processor as the stated model for a new virtual-stack metadata processor. Define which VMware metadata fields are required for observability and validate that the completed processor includes those fields; the issue does not identify files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100