Tectonic’s Prometheus Open Cloud Service provides a one-click, fully managed, application monitoring and metrics stack for both operations and applications teams on-top of a Tectonic cluster. Use Prometheus’s Alertmanager to route, email, page, or message teams when something goes wrong with an application or the container infrastructure. Prometheus OCS is:
Allows you to deploy and manage Prometheus instance into any namespace.
Use Tectonic Console to enable the Prometheus OCS for selected namespaces.
By default, objects created using the Prometheus OCS will be labeled
Using the Prometheus Open Cloud Service to deploy a Prometheus instance will create the following Kubernetes objects:
Prometheus Open Cloud Service will not enable Ingress for the cluster. First configure Ingress to access the Prometheus UI.
Once enabled, go to *https://
Use the built-in Tectonic Alertmanager with the Prometheus OCS. Alertmanagers should be shared between Prometheus instances.
For Service discovery, the Prometheus Pod must have permission to access the Kubernetes API in the tectonic-system namespace. Follow the instructions in Monitoring Applications to create a ClusterRoleBinding to bind the available ClusterRole to an appropriate ServiceAccount. Using Tectonic Console to create a Prometheus instance will automatically generate the required ClusterRoleBinding.
Prometheus must have sufficient RBAC permissions to access the Kubernetes cluster.
The app must be instrumented, and expose an HTTP endpoint. Use the Client Library appropriate to your app to expose metrics through an HTTP endpoint.
Then, configure Prometheus to discover these targets.
For more information, see Application Monitoring.