Filter istio metrics related to telemetry component communication

[a-thaler]

Description

Users are interested in the Istio metrics of the business related communication and will accept the cost for storing them. The communication to the telemetry module is not really crucial for the users and will cause a higher volume of data, think of the telemetry-metric-agent scraping a bigger amount of pods.

To be consistent with the trace gateway implementation, all metrics related to telemetry system related communication should be filtered out by default.

Criteria

• As a user I will not see any Istio metrics related to communication from/to telemetry components
• As a telemetry module maintainer, I want to avoid unneeded code, so orphaned rules should be removed

Reasons

Attachments

Release Notes

When using the Istio input of a MetricPipeline, communication with the telemetry gateways gets excluded by default

[rakesh-garimella]

Filters have been implemented in metric agent. Currently following is dropped:

• Metric with source telemetry-metric-agent
• Metric with destination telemetry-metric-gateway
• Metric with destination telemetry-trace-collector
  Obsolete filter ruless have been dropped in trace collector