3

Is there any way to capture metrics like query per seconds or latency of service call (between two services) in kubernetes environment without tool like Istio or any other enovy/mesh based architecture?

In other words, what are the metrics that are only possible by implementing a service mesh?

Pragmatic
  • 3,093
  • 4
  • 33
  • 62
  • 2
    that's just a tertiary meah feature; the observability. You can imstall Prometheus for these metrics. Or Opentracing Api for telemetry. – suren Jul 18 '20 at 12:13
  • @suren I believe these are metrics and not tracing features. Prometheus can only capture these metrics, but someone has to publish them. – Pragmatic Jul 18 '20 at 16:00
  • service call latency can easily be Tracing. Prometheus has the agent, if that's what you mean. – suren Jul 19 '20 at 19:04
  • 1
    Without a service mesh or proxy-based architecture, I would say it is up to your application to provide these metrics. There are prometheus exporters or modules for many popular frameworks. E.g. microprofile metrics, micrometer.io, etc. But envoy or service meshes would make it framework-agnostic. – Joel Jul 20 '20 at 07:18
  • Thanks @Joel, makes sense to me. If you can put it in answer, I will accept that. – Pragmatic Jul 24 '20 at 17:19

1 Answers1

0

I am posting this as a community wiki answer for better visibility.

as @Joel mentioned in comments.

Without a service mesh or proxy-based architecture, I would say it is up to your application to provide these metrics. There are prometheus exporters or modules for many popular frameworks. E.g. microprofile metrics, micrometer.io, etc. But envoy or service meshes would make it framework-agnostic.

Jakub
  • 8,189
  • 1
  • 17
  • 31