> so if any new host spin up not required to add manually on targets That depends on how you are detecting the new hosts which are spun up. Prometheus normally does this using "service discovery". You are currently using the "file" service discovery mechanism, which reads your targets.yml file, but there are many other options which you can read about in the prometheus documentation.
For example, if you are spinning up hosts as AWS EC2 instances, then you can use EC2 service discovery: https://prometheus.io/docs/prometheus/latest/configuration/configuration/#ec2_sd_config > I want to know that can I manage this Targets.yml from puppet If you wish to continue using the file service discovery mechanism (i.e. use targets.yml and manage it through puppet), then it's up to you to work out how to detect a new hosts, update targets.yml, and push it out. On Friday, 25 March 2022 at 05:28:57 UTC [email protected] wrote: > Team anyone have idea about this? > > On Wed, 23 Mar 2022 at 12:27 PM, ritesh patel <[email protected]> > wrote: > >> Hello Team, >> >> Hope You are doing well ๐ >> >> I have prometheus running on docker and My all targets are managed from >> targets.yml, now I want to know that can I manage this Targets.yml from >> puppet so if any new host spin up not required to add manually on targets. >> >> Any one have any idea about this? How itโs work and any flow chart for >> how I can manage targets.yml from puppet. >> >> Thanks and regards >> Ritesh patel >> > -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/f006628b-5d86-4987-a4a2-987ebb4df1fan%40googlegroups.com.
