[−][src]Trait nakadion::api::MonitoringApi
Required methods
fn get_cursor_distances<T: Into<FlowId>>(
&self,
name: &EventTypeName,
query: &CursorDistanceQuery,
flow_id: T
) -> ApiFuture<CursorDistanceResult>
&self,
name: &EventTypeName,
query: &CursorDistanceQuery,
flow_id: T
) -> ApiFuture<CursorDistanceResult>
Deletes an EventType identified by its name.
See also Nakadi Manual
fn get_cursor_lag<T: Into<FlowId>>(
&self,
name: &EventTypeName,
cursors: &[Cursor],
flow_id: T
) -> ApiFuture<Vec<Partition>>
&self,
name: &EventTypeName,
cursors: &[Cursor],
flow_id: T
) -> ApiFuture<Vec<Partition>>
Used when a consumer wants to know how far behind in the stream its application is lagging.
See also Nakadi Manual
fn get_event_type_partitions<T: Into<FlowId>>(
&self,
name: &EventTypeName,
flow_id: T
) -> ApiFuture<Vec<Partition>>
&self,
name: &EventTypeName,
flow_id: T
) -> ApiFuture<Vec<Partition>>
Lists the Partitions for the given event-type.
This endpoint is mostly interesting for monitoring purposes or in cases when consumer wants to start consuming older messages. If per-EventType authorization is enabled, the caller must be authorized to read from the EventType.
See also Nakadi Manual
Implementors
impl MonitoringApi for ApiClient
[src]
fn get_cursor_distances<T: Into<FlowId>>(
&self,
name: &EventTypeName,
query: &CursorDistanceQuery,
flow_id: T
) -> ApiFuture<CursorDistanceResult>
[src]
&self,
name: &EventTypeName,
query: &CursorDistanceQuery,
flow_id: T
) -> ApiFuture<CursorDistanceResult>
fn get_cursor_lag<T: Into<FlowId>>(
&self,
name: &EventTypeName,
cursors: &[Cursor],
flow_id: T
) -> ApiFuture<Vec<Partition>>
[src]
&self,
name: &EventTypeName,
cursors: &[Cursor],
flow_id: T
) -> ApiFuture<Vec<Partition>>
fn get_event_type_partitions<T: Into<FlowId>>(
&self,
event_type: &EventTypeName,
flow_id: T
) -> ApiFuture<Vec<Partition>>
[src]
&self,
event_type: &EventTypeName,
flow_id: T
) -> ApiFuture<Vec<Partition>>