[IGNITE-15102] Implement monitoring of various pyignite's events

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: python-0.5.1
• Component/s: python, thin client
• Labels: python thin

Release Note

* Implemented event listeners to connection events and query events
* Fixed request to failed node when querying replicated cache
* Fixed excessive partition mapping requests

• Ignite Flags: Docs Required, Release Notes Required
• Assignee: Ivan Daschinsky
• Reporter: Ivan Daschinsky
• Created: 12/Jul/21 09:50
• Updated: 14/Feb/23 07:43
• Resolved: 20/Jul/21 05:25

Description

I suggest to add monitoring capabilities to pyignite similar to pymongo's

Suggested api:

from pyignite.monitoring import OpEventListener, ConnectionEventListener, TopologyEventListener
from pyignite import Client

client = Client(event_listeners=[OpEventListener, ConnectionEventListener, TopologyEventListener])
with client.connect(...):
     ......

I suggests to add listeners to:

1. Connection events connect or disconnect to specific ignite server, connection errors
2. Topology events when partition awareness is enabled, log new topology versions
3. 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

Issue Links

• is related to: IGNITE-18788 Query listener in python thin client fire events only if a debug logging level enabled
• is related to: IGNITE-18615 Implement events in java thin client
• links to: dev-list discussion
• links to: GitHub Pull Request #46
• links to: TC build