The general suggestion is to use a configuration management system such as Ansible to create the configuration file. Equally you can use the different service discovery mechanisms to simplify your configuration too, including the file_sd to pull targets into separate files (which themselves might be build via configuration management tools or scripts that interact with database of record type systems).
On 31 March 2020 15:59:52 BST, Ishvar B <[email protected]> wrote: >Hi, > >I have a prometheus set up which has too many (roughly 50 static >configs) >and this number would increase as we have lot of vms still be scraped >for >prometheus. The file is becoming huge , especially when some >applications >require basic auth. is there any best practice to maintain the config >file >as with such huge file some times changes would cause accidental >errors. > >Thanks >Eswar > >-- >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/65a0249c-c27a-479d-9df0-b68e5102b883%40googlegroups.com. -- Sent from my Android device with K-9 Mail. Please excuse my brevity. -- 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/80F29B6C-5736-4155-8B2A-5988AA2DF855%40Jahingo.com.
