Stage 2 Orchestrator RFC #1299
Stage 2 Orchestrator RFC #1299
Conversation
|
|
||
| ### Ingestion mechanisms | ||
|
|
||
| - The Filebeat [Kubernetes processor][5] will need updating, as it currently |
There was a problem hiding this comment.
@ChrsMark @jsoriano @kaiyan-sheng Any other integrations or components that might populate these orchestrator fields that we might want to capture here?
There was a problem hiding this comment.
Same change will be needed in Cloud Foundry and Nomad features. Btw, I see that nomad docs are not available in the public guides, I will take a look.
There was a problem hiding this comment.
Adding the missing docs for Nomad: elastic/beats#24557
There was a problem hiding this comment.
++ I also expect Metricbeat Kubernetes module to need updates, in the line of the Filebeat processor/autodiscover provider: https://www.elastic.co/guide/en/beats/metricbeat/current/running-on-kubernetes.html
There was a problem hiding this comment.
Thanks all - I have added the mentioned services to the document.
|
Thanks all - will set the today's date and merge! |
Progress the Orchestrator RFC to Stage 2.
I have made an attempt to identify anything that will need updating if when the RFC process for this is complete, but I expect those with more familiarity with the entire Elastic stack will have a better idea!
Any additional concerns around the fieldset are also welcome.