You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Ivan Daschinsky (Jira)" <ji...@apache.org> on 2023/02/06 10:11:00 UTC
[jira] [Updated] (IGNITE-18615) Implement events in java thin client
[ https://issues.apache.org/jira/browse/IGNITE-18615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ivan Daschinsky updated IGNITE-18615:
-------------------------------------
Summary: Implement events in java thin client (was: Implement monitoring in java thin client)
> Implement events in java thin client
> ------------------------------------
>
> Key: IGNITE-18615
> URL: https://issues.apache.org/jira/browse/IGNITE-18615
> Project: Ignite
> Issue Type: Improvement
> Reporter: Ivan Daschinsky
> Assignee: Ivan Daschinsky
> Priority: Major
> Labels: ise
> Time Spent: 10m
> Remaining Estimate: 0h
>
> I suggest to add monitoring capabilities similar to [java mongo client|https://www.mongodb.com/docs/drivers/java/sync/current/fundamentals/monitoring]
> I suggests to add listeners to:
> # *Connection events* connect or disconnect to specific ignite server, connection errors
> # *Topology events* when partition awareness is enabled, log new topology versions
> # *Operations events* start,success or failure with request_id, server (address, port and uuid), operation_id, error string if presents
> This approach can implement custom metrics, tracing and other useful client-side stuff in order to make client more observable
--
This message was sent by Atlassian Jira
(v8.20.10#820010)