Knative 事件度量¶
管理员可以查看Knative事件组件的度量。
Broker - Ingress¶
使用以下度量来调试代理入接口的执行方式以及通过入接口组件分派的事件。
通过在http代码上聚合度量,可以将事件分为两类:成功事件(2xx)和失败事件(5xx)。
Metric Name | Description | Type | Tags | Unit | Status |
---|---|---|---|---|---|
event_count | Number of events received by a Broker | Counter | broker_name event_type namespace_name response_code response_code_class unique_name |
Dimensionless | Stable |
event_dispatch_latencies | The time spent dispatching an event to a Channel | Histogram | broker_name event_type namespace_name response_code response_code_class unique_name |
Milliseconds | Stable |
Broker - Filter¶
使用以下指标来调试代理筛选器如何执行以及通过筛选器组件分派什么事件。 此外,用户还可以测量事件上实际过滤操作的延迟时间。 通过在http代码上聚合度量,可以将事件分为两类:成功事件(2xx)和失败事件(5xx)。
Metric Name | Description | Type | Tags | Unit | Status |
---|---|---|---|---|---|
event_count | Number of events received by a Broker | Counter | broker_name container_name= filter_type namespace_name response_code response_code_class trigger_name unique_name |
Dimensionless | Stable |
event_dispatch_latencies | The time spent dispatching an event to a Channel | Histogram | broker_name container_name filter_type namespace_name response_code response_code_class trigger_name unique_name |
Milliseconds | Stable |
event_processing_latencies | The time spent processing an event before it is dispatched to a Trigger subscriber | Histogram | broker_name container_name filter_type namespace_name trigger_name unique_name |
Milliseconds | Stable |
In-memory Dispatcher¶
内存通道可以通过以下指标进行评估。 通过在http代码上聚合度量,可以将事件分为两类:成功事件(2xx)和失败事件(5xx)。
Metric Name | Description | Type | Tags | Unit | Status |
---|---|---|---|---|---|
event_count | Number of events dispatched by the in-memory channel | Counter | container_name event_type= namespace_name= response_code response_code_class unique_name |
Dimensionless | Stable |
event_dispatch_latencies | The time spent dispatching an event from a in-memory Channel | Histogram | container_name event_type namespace_name= response_code response_code_class unique_name |
Milliseconds | Stable |
Note
A number of metrics eg. controller, Go runtime and others are omitted here as they are common across most components. For more about these metrics check the Serving metrics API section.
事件源¶
事件源由拥有相关系统的用户创建,因此它们可以用事件触发应用程序。 每个源在默认情况下都公开了一些度量,以帮助用户监视分派的事件。 使用以下度量来验证事件已经从源端交付,从而验证源和与源的任何连接是否正常工作。
Metric Name | Description | Type | Tags | Unit | Status |
---|---|---|---|---|---|
event_count | Number of events sent by the source | Counter | event_source event_type name namespace_name resource_group response_code response_code_class response_error response_timeout |
Dimensionless | Stable |
retry_event_count | Number of events sent by the source in retries | Counter | event_source event_type name namespace_name resource_group response_code response_code_class response_error response_timeout |
Dimensionless | Stable |