Menu
Prometheus is a time-series database that stores our metric data by pulling it (using a built-in data scraper) periodically over HTTP. The intervals between pulls can be configured, of course, and we have to provide the URL to pull from. It also has a simple user interface where we can visualize/query on all of the collected metrics. Mac OS Many computers today come with support for 'hardware virtualization' (called VT-x by Intel and AMD-V by AMD ), which improves performance of virtual machines. On Macs, itâs enabled by default, in which case thereâs no need to read further! We are going to deploy mikrotik-exporter to visualise Prometheus monitoring data for Mikrotik. A Mikrotik router. Iâve been using Mikrotik for many years, and itâs done the job really well. In my honest opinion, the best thing you can do with your ISP-provided router is to recycle it. An open-source monitoring system with a dimensional data model, flexible query language, efficient time series database and modern alerting approach.
In this getting started guide you will install Ververica Platform and integrate it with MinIO for Universal Blob Storage.Optionally, we also show you how to link the platform to a metrics and logging system.
Ververica Platform runs on top of Kubernetes. In order to get started locally we recommend using minikube,but any other Kubernetes Cluster will do, too.
Minikube relies on either virtualization support by your operating system and a hypervisor (e.g. Virtualbox), or a container runtime (e.g. Docker).Please check the official installation guide for details.
Note
Though the Ververica Platform itself runs on any Kubernetes cluster version 1.11+, other parts of the Playgroundrequire version 1.16+.
Minikube on Mac OS (homebrew)¶Minikube on Windows (Chocolatey)¶Minikube on Linux¶
There are packages available for most distros and package managers.Please check the kubectl installation guide as well as the minikube installation guide for details.
Spinning up a Kubernetes Cluster¶
First, you start
minikube . The platform (including a small Apache Flink® application) requires at least 8G of memory and 4 CPUs.
If this went well, you can continue and check if all system pods are ready.
Depending on your exact version of minikube, the output should look more or less similar to
If all pods are running, you are good to go.
âHelm helps you manage Kubernetes applications â Helm charts help you define, install, and upgrade even the most complex Kubernetes application.â - helm.sh
Prometheus (nathandimmer) Mac Os Catalina
We distribute Ververica Platform as a Helm chart. To install Helm please follow the instructions on the official installation guide or use one of the one-liners below.
Note
Please ensure that you install Helm v3+. This can be verified by running
helmversion after installation.
Helm on Mac OS (homebrew)¶Helm on Windows (Chocolatey)¶Helm on Linux¶
As before, there is a package available for most distros and package managers. For details check the official installation guide.
This guide is based on the Ververica Platform playground repository which contains scripts and Helm values files to make for a smooth getting-started experience.Please clone the repository before continuing; all commands below are meant to be executed from the repository root directory.
For this playground, you will create two Kubernetes namespaces:
vvp and vvp-jobs .vvp will host the control plane of Ververica Platform and other services, while the Apache Flink® jobs managed by the platform will run in the vvp-jobs namespace.
In addition to Ververica Platform, we will set up MinIO in the
vvp namespace, which will be used for artifact storage and Apache Flink® checkpoints & savepoints (see Universal Blob Storage).
TL;DR¶
You can skip all of the installation steps outlined below by running:
Kubernetes Namespaces¶
Before installing any of the components you need to create the Kubernetes namespaces vvp and vvp-jobs.
MinIO¶
Install MinIO with Helm, using the official Helm chart from the
stable repository.
If you have never added the
stable Helm repository, do this now:
Then install MinIO with:
Ververica Platform¶
Then, install Ververica Platform using
helm .The required configurations slightly differ based on the product edition you would like to install.
Ververica Platform Community Edition
When running the command above you will be asked to accept the Ververica Platform Community Edition license agreement.Please read it carefully and except it by setting
acceptCommunityEditionLicense to true :
Before you can run Ververica Platform Stream Edition, you must add your license to a values file
values-license.yaml under vvp.license.data .If you do not have a license yet, you can request a 30 day free trial license from the Ververica website.
The
values-license.yaml file should look similar to:
In order to access the web user interface or the REST API set up a port forward to the Ververica Platform Kubernetes service:
The web interface and API are both now available under localhost:8080.The UI will show that you do not have any Deployments yet.
Ververica Platform can be integrated with logging and metrics collection and querying/visualization systems to help monitor and debug your Flink applications.
The
setup.sh script included in the playground repository accepts flags --with-logging and --with-metrics that enable additional demo components for logging and metrics respectively.
Note
The
--with-logging and --with-metrics flags can be used separately or together, and can be applied after the initial installation simply by running setup.sh again.
This setup uses Global Deployment Defaults to ensure each Flink job is configured to use the built-in Prometheus metrics reporter and that each Kubernetes pod running Flink gets an annotation that makes it discoverable by the Prometheus server.
Viewing Application Metrics¶
After installing or upgrading the platform using
./setup.sh--with-metrics , run the following command to port-forward Grafanato your local network:
The web interface should now be available under localhost:3000.
When viewing one of your Deployments in the web UI, click the
Metrics button to be linked to a sample monitoring dashboard in Grafana for that Deployment.It may take a few minutes for metrics to appear.
Exploring the Configuration¶
To understand this setup, check out the following files:
Viewing Application Logs¶
After installing or upgrading the platform using
./setup.sh--with-logging , run the following command to port-forward Kibanato your local network:
The web interface should now be available under localhost:5601.
When viewing one of your Deployments in the web UI, click the
Logs button to be linked to Kibana with a pre-filled query to only show logs from that Deployment.
Exploring the Configuration¶
To understand this setup, check out the following files:
Now, you can either continue with Getting Started - Flink SQL or Getting Started - Flink Operations.
![]()
Run the script
./teardown.sh to clean up all applications deployed with Helm created in this tutorial and delete the namespaces created in the first step.
Alternately, do this manually with the following command:
ON THIS PAGEOverview
The proNX Optical Director supports the use of Prometheus to monitor the Kubernetespods used in the proNX Optical Director application. Prometheus is an open source systemsmonitoring toolkit that collects and displays metrics from monitoredtargets. Advanced users can use Prometheus to check on the healthof the proNX Optical Director installation and look at various indicators to confirmthat the proNX Optical Director is running normally.
The proNX Optical Director supports two types of metrics:
The proNX Optical Director software package includes a Prometheus configurationfile that is preconfigured to monitor the Device, Network, and Operationspods used in the proNX Optical Director. The Prometheus configuration file is locatedat
/var/data/conf/prometheus-conf.yml on the master node. You do not need to make any changes to the configurationfile, but you are required to download the Prometheus docker imagebecause the image is not included in the proNX Optical Director software package.
Prometheus (nathandimmer) Mac Os X
You can use the procedures in the following sections to getstarted with Prometheus. However, a detailed explanation of Prometheusand the supported metrics is beyond the scope of this document. Forinformation on Prometheus, see https://prometheus.io/docs/.
Downloading and Installing Prometheus
Prerequisites
Use this procedure to download and install Prometheuson the master node in your proNX Optical Director server cluster.
Using Prometheus
Use this procedure to monitor the proNX Optical Director using Prometheus.
Note
This procedure provides a cursory look at Prometheus.For more detailed information on Prometheus, see the official documentationat https://prometheus.io/docs/.
Uninstalling PrometheusPrometheus (nathandimmer) Mac Os Update
Use this procedure to uninstall Prometheus on the masternode in your proNX Optical Director server cluster.
Prometheus (nathandimmer) Mac Os Download
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |