Setting up On-Premise Metrics
Setting up VictoriaMetrics and Grafana
From the Installer's Integrations page, click "Install" under "Monitoring"
For the provided prom.yml, see the following descriptions of the parameters:
If you want to write prometheus data to a remote prometheus instance, please define these 4 variables :
remote_write_url: The URL of the endpoint to which to push remote writes
remote_write_external_labels: The labels to add to your data, to identify the writes from this cluster
remote_write_username: The username to use to push the writes
remote_write_password: The password to use to push the writes
You can configure which prometheus components you want to deploy :
trueto deploy VictoriaMetrics
deploy_node_exporter: requires prometheus deployment. Set to
trueto gather data about the k8s nodes.
deploy_kube_control_plane_monitoring: requires prometheus deployment. Set to
trueto gather data about the kube controle plane.
deploy_kube_state_metrics: requires prometheus deployment. Set to
trueto gather data about kube metrics.
deploy_element_service_monitors: Set to
ServiceMonitorresources into the K8S cluster. Set it to
trueif you want to monitor your element services stack using prometheus.
You can choose to deploy grafana on the cluster :
grafana_fqdn: The FQDN of the grafana application
For the specified
grafana_fqdn, you will need to provide a crt/key PEM encoded key pair in
~/.element-enterprise-server/config/legacy/certs prior to running the installer. If our hostname were
metrics.airgap.local, the installer will expect to find
metrics.airgap.local.key in the ~/.element-enterprise-server/config/legacy/certs` directory. If you are using Let's Encrypt, you do not need to add these files.
After running the installer, open the FQDN of Grafana. The initial login user is
admin and password is the value of
admin_password. You'll be required to set a new password, please define one secured and keep it in a safe place.