It's a broad topic, so please let us know if there's anything specific you'd like to know, in order to give you better feedback.
If are interested in the "configuration as code" approach, I'd recommend you look into our project monitor initiative. With these, you'll be able to manage your monitors as if it were a deploy-able artifact instead of manually setting them up through the UI. Both options are supported, but project monitors are a better DX experience.
Since you'll be using self-hosted, please also consider our scalability guidelines for private locations. Scaling will be directly correlated to the amount of monitors you're expecting to run so you might to fine-tune resource allocation for these.
If data retention is a point of concern, I'd recommend reading through this doc section and follow this tutorial if you need to customize any of them. Other than browser monitors' indeces, data volume is fairly minimal on average across tcp, icmp and http monitor types.
As additional topics, we have this guide on managing secrets/credential inside synthetics and this statement on how data is secured on clusters.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.