While the basic cluster-overview monitoring is useful for monitoring overall cluster health, there is still a lot of important information about each service within PostHog that isn't available. Our Grafana dashboard should now be available at localhost:8080, and we can log in using the username admin along with the password we just retrieved.įor information on exposing Grafana through an Nginx ingress, take a look at the configuration options for the upstream Grafana chart.įinally, if we now go to the list of Dashboards and navigate to PostHog > Kubernetes (cluster overview), you should see a pre-configured dashboard with a number of metrics related to our cluster!įor more information on configuring and using Grafana, check out the official docs Setting up service-specific monitoring Kubectl -n posthog port-forward svc/posthog-grafana 8080 :80 Which can be done by adding the following lines to our values.yaml To set up basic monitoring, we will need to enable the following two charts: This section covers setting up basic monitoring for the entire Kubernetes cluster, and provides basic metrics such as CPU usage, memory usage, and disk IOs. If you are running an older version, take a look at our guide on how to upgrade PostHog Setting up cluster monitoring Note: This guide requires you to be running a Helm chart version of at least 26.0.6. Getting startedīy default, the PostHog Helm chart does not come with Grafana enabled, so we will need to update our config values in order to install it. If you are targeting a production use-case, we highly recommend setting up all of these options. This guide covers how to configure monitoring of your self-hosted deployment through Grafana. Instructions for deploying can be found here. Juju relate grafana-agent prometheus-receive-remote-writeĪfter this is complete, Grafana will show the new dashboards: Kafka Exporter and allows access for Charmed Kafka logs on Loki.We still maintain our Open-source Docker Compose deployment. Juju relate grafana-agent grafana-dashboards Juju relate kafka:cos-agent grafana-agent Now, deploy grafana-agent (subordinate charm) and relate it with Charmed Kafka, later relate grafana-agent with consumed COS offers: juju deploy grafana-agent Juju consume k8s:admin/cos.grafana-dashboards K8s admin/cos.prometheus-receive-remote-write admin prometheus-receive-remote-write:receive-remote-writeĬonsume offers to be reachable in the current model: juju consume k8s:admin/cos.prometheus-receive-remote-write K8s admin/cos.loki-logging admin loki_push_api:logging K8s admin/cos.grafana-dashboards admin grafana_dashboard:grafana-dashboard Switch to mysql modelĪ similar output should appear, if k8s is the k8s controller name and cos the model where cos-lite has been deployed: Store URL Access Interfaces Switch to Charmed Kafka VM model, find offers and relate with them: # We are on the Kubernetes controller, for the cos model. Juju offer prometheus:receive-remote-write prometheus-receive-remote-write Juju offer grafana:grafana-dashboard grafana-dashboards Switch to COS K8s environment and offer COS interfaces to be cross-model related with Charmed Kafka VM model: # Switch to Kubernetes controller, for the cos model. Since the Charmed Kafka Operator is deployed on a machine environment, it is needed to offer the endpointsĬan be used, and this step is shown in the COS tutorial. The metrics can be queried by accessing the endpoints.Īdditionally, the charm provides integration with the Canonical Observability Stack.ĭeploy cos-lite bundle in a Kubernetes environment. The Charmed Kafka Operator comes with the JMX exporter.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |