Support Center

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here
Icon Right Icon Right Icon Right

To better serve you during these uncertain times, we will be hosting a weekly support webinar. We’ll cover topics like LogicMonitor admin basics as well as ways to monitor a remote work environment. Tune in every Wednesday at 11:00am PST.

Sign up here
Support_category > Containers

Istio Monitoring (Kubernetes)

Overview

​Istio is a service mesh that provides traffic management, policy enforcement, and telemetry collection for microservices. Using LogicMonitor’s Istio package for Kubernetes, you can gather metrics from the backing Prometheus time-series database (TSDB) that comes bundled with Istio. LogicMonitor’s Istio Kubernetes package supports Kubernetes only.

​The LogicModules in the Istio Kubernetes package utilize the “/metrics” endpoint from the Prometheus pod on port 9090. By default, these LogicModules apply to the pod in the “istio-system” namespace labeled with “app=prometheus”.

Compatibility

LogicMonitor’s Istio Kubernetes package supports Kubernetes only. As Istio releases support for other platforms, LogicMonitor will test and extend coverage as necessary.

Setup Requirements

Import LogicModules

From the LogicMonitor Repository, import all Istio Kubernetes LogicModules, which are listed in the LogicModules in Package section of this support article.

Add Devices Into Monitoring

It is recommended that your Kubernetes cluster already be added into LogicMonitor for monitoring, as many of the AppliesTo properties set by Argus, LogicMonitor’s open-source Kubernetes monitoring solution, are necessary for seamless operation. For instructions on adding your Kubernetes cluster into monitoring, see Adding your Kubernetes Cluster into Monitoring.

Port Access

The Istio Kubernetes package gathers metrics from the backing Prometheus TSDB that comes bundled with Istio. Istio must be installed on the Kubernetes cluster and port 9090, which is used to access the Prometheus “/metrics” endpoint, must be open to the Collector.​

LogicModules in Package

​LogicMonitor’s Istio Kubernetes package consists of the following LogicModules. For full coverage, please ensure that all of these LogicModules are imported into your LogicMonitor platform.

Display Name

Type

Description
Istio Kubernetes Connections DataSource Collects net_conntrack_dialer_con* Istio metrics from Prometheus such as attempted, closed, established, refused and failed connections.
Istio Kubernetes Go Performance DataSource Collects go_* Istio metrics from Prometheus such as Go memory, cpu, routines, threads, etc.
Istio Kubernetes Process Performance DataSource Collects process_* Istio metrics from Prometheus such as CPU time usage, file descriptors, memory, flaps, etc.
Istio Kubernetes Prometheus Performance DataSource Collects prometheustsdb* Istio metrics from Prometheus such as transactions, blocks, checkpoints, compactions, fsync, garbage collection, etc.
Istio Kubernetes Prometheus Queries DataSource Collects prometheus_engine* and Istio metrics from Prometheus such as query counts and latencies across for API, engine, prepare, queue, etc.
Istio Kubernetes Prometheus Scrape Performance DataSource Collects prometheus_target* Istio metrics from Prometheus such as scrape attempts, failures, reloads, etc.
Istio Kubernetes Prometheus Scrape Pools DataSource Collects prometheus_target* Istio metrics from Prometheus such as scrape counts and latency.
Istio Kubernetes Prometheus Service Discovery DataSource Collects prometheus_sd* Istio metrics from Prometheus such as latency and failures for Azure, Consul, EC2, GCE, Kubernetes, etc.
Istio Kubernetes Prometheus Traffic DataSource Collects promhttp_metric_handler_requests_* Istio metrics such as HTTP responses, response status codes, size, health and InFlight requests.

When setting static datapoint thresholds on the various metrics tracked by this integration package, LogicMonitor follows the technology owner’s best practice KPI recommendations. If necessary, we encourage you to adjust these predefined thresholds to meet the unique needs of your environment. For more information on tuning datapoint thresholds, see Tuning Static Thresholds for Datapoints.

In this Article: