Skip to content
This repository has been archived by the owner on Feb 16, 2019. It is now read-only.

Istio Mixer help needed - how to scrape application metrics? #344

Open
darrenhaken opened this issue May 17, 2018 · 0 comments
Open

Istio Mixer help needed - how to scrape application metrics? #344

darrenhaken opened this issue May 17, 2018 · 0 comments
Assignees
Milestone

Comments

@darrenhaken
Copy link

Background
I have a K8 cluster deployed with Istio which is collecting pod metrics from services which are pushed into Prometheus and rendered in Grafana.

We are running a suite of Java services using Spring Boot which can expose metrics in a Prometheus format and covers metrics like JMX, response time etc.

We are using Micrometer with Prometheus as the backend. This exposes a set of the metrics on {application}/actuator/prometheus.

We want to monitor our services and get a holistic view of how they are performing.
I can imagine we will also emit custom metrics from our applications based on the domain.

Problem
I can see two approaches and I'd like some advice on the best approach:

  • Envoy scrapes {application}/actuator/prometheus, push the metrics to Mixer which is then scraped by Prometheus. If this is the right way to go how do we do this? Does this matter that not all pods running on the cluster will be JVM and emit these additional metrics?

  • Prometheus scrapes the application pods directly. This will result in a duplication of metrics from Envoy/Mixer and the application e.g. response time.

@douglas-reid douglas-reid added this to the 1.0 milestone Jun 13, 2018
@douglas-reid douglas-reid self-assigned this Jun 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants