envoyproxy/envoy

How to distinguish externally and locally originated errors for upstream clusters?

Open

#25,798 建立於 2023年2月27日

在 GitHub 查看
 (1 留言) (0 反應) (0 負責人)C++ (5,373 fork)batch import
area/clusterarea/statshelp wantedquestion

倉庫指標

Star
 (27,997 star)
PR 合併指標
 (平均合併 8天) (30 天內合併 378 個 PR)

描述

Title: How to distinguish externally and locally originated errors for upstream clusters? Description:

In order to setup proper alerting for Api Gateway based on Envoy I'm trying to find the opportunity to get metric that shows only the errors originated by Envoy. The idea was to calculate the difference between downstream_rq_xx and upstream_rq_<*xx> but as I understand the upstream_rq_<*xx> includes also, for example, timeouts originated by Envoy.

Is there any stats for upstream cluster's externally originated errors? If no, could you please suggest any workaround to get such statistics?

[optional Relevant Links:]

I have found out that externally and locally originated errors are calculated separately during outlier detection: https://www.envoyproxy.io/docs/envoy/latest/intro/arch_overview/upstream/outlier But I have found any related statistics for upstream errors.

貢獻者指南