istio VS Telegraf

Istio is a popular open-source service mesh framework that provides a comprehensive solution for managing, securing, and observing microservices-based applications running on Kubernetes.

Leverage a service mesh like Istio or Linkerd to manage communication between microservices within the Kubernetes cluster. These service meshes can be configured to intercept JMX traffic and enforce access control policies. Benefits:

Open Source and Cloud Computing: A Match Made in Heaven The cloud is accelerating OSS adoption. Cloud-native technologies like Kubernetes [https://kubernetes.io/] and Istio [https://istio.io/], both open-source projects, are revolutionizing how applications are built and deployed across cloud platforms.

Consider the case of Bookinfo, a sample application provided by Istio, rewritten using CloudWeGo's Kitex for superior performance and extensibility.

It is a dedicated infrastructure layer that manages service-to-service communication, providing features like load balancing, encryption, authentication, and monitoring. Istio deploys sidecar proxies alongside each microservice instance. These proxies handle communication, providing features like load balancing, service discovery, encryption, monitoring and authentication.

5Y old post that sounds like they've done similar here: Caddy Issue Istio Issue but doesn't cover much of the implementation

In a production environment there will be a load balancer setup with an Ingress Controller, Service Mesh or some type of Custom Router. This allows all traffic to be sent to the single load balancer IP address and then route the traffic to a service based on the Domain name or subpath. We are using a NGINX ingress controller but service meshes like Istio have been becoming the most popular solution to use as they offer more segmentation, security and granular control.

Flagger is a progressive delivery tool that enables a Kubernetes operator to automate the promotion or rollback of deployments based on metrics analysis. It supports a variety of metrics including Prometheus, Datadog, and New Relic to name a few. It also works well with Istio service mesh, and can implement progressive traffic splitting between primary and canary releases.

End-to-end data encryption with a service mesh: Using an end-to-end data encryption mechanism with a service mesh like Istio, TLS can secure communication between different microservices within a Kubernetes cluster. This is a popular approach for modern, distributed microservice architectures.

The Telegraf (v1.27.3) Net Input Plugin only reports total numbers - i.e., total bytes received by an interface.

I need some help with Filestat - https://github.com/influxdata/telegraf/tree/master/plugins/inputs/filestat

Telegraf’s Secretstores Plugin implementation on GitHub

That's the thing, I do need network_mode: host on telegraf in order to get host network statistics. See here or here

After screwing around with it for a while, I was able to get inputs.smart working... but I'm not thrilled with the answer. According to this in order for you to get the SMART data inside a container you need to edit the sudoers file inside the container.

I’ve been using the Jolokia agent with telegraf to push JVM metrics into InfluxDB (among other things). I think it can be used with Prometheus too.

Do you mean Telegraf?

I have two devices; both are connected to a Raspberry Pi using a USB converter as Slave 1 and 2. I want to get some readings using Telegraf software https://github.com/influxdata/telegraf/tree/release-1.26/plugins/inputs/modbus (happy to try any other linux software), but I'm having trouble (I'm seriously confused to be honest) with byte_order, data_type, and input register addresses.

Yeah i think you can use the grok processor, docs found here: https://github.com/influxdata/telegraf/tree/master/plugins/parsers/grok