-
Type: Task
-
Resolution: Unresolved
-
Priority: Unknown
-
None
-
Component/s: SDAM
-
Needed
-
Summary
There is no consistency among drivers on when heartbeat started event is emitted.
Some drivers (Rust, Node) emit the event before monitoring connection is established, some like (Java, .Net) emit the event after connection establishment, just before the 'hello'.
In the case _heartbeat started event should be emitted after connection establishment, SDAM logging tests should be updated to include serverConnectionId._
Motivation
Who is the affected end user?
Drivers, tech debt.
How does this affect the end user?
No considerable impact. Consistency of heartbeat event duration.
How likely is it that this problem or use case will occur?
Main path.
If the problem does occur, what are the consequences and how severe are they?
Inconsistency of events emission among drivers.
Is this issue urgent?
No.
Is this ticket required by a downstream team?
No.
Is this ticket only for tests?
No.
Acceptance Criteria
What specific requirements must be met to consider the design phase complete?
- is depended on by
-
GODRIVER-2966 ServerHeartbeatStartedEvent does not publish correctly
- Closed
-
DRIVERS-1670 Add log messages to SDAM spec
- Implementing
-
DRIVERS-2578 Switch to polling monitoring when running within a FaaS environment
- Implementing
- is related to
-
GODRIVER-2966 ServerHeartbeatStartedEvent does not publish correctly
- Closed
-
NODE-5840 Heartbeat durations are measured incorrectly
- Closed
- split to
-
CDRIVER-4758 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Backlog
-
CXX-2781 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Backlog
-
JAVA-5230 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Backlog
-
RUBY-3345 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Backlog
-
PHPLIB-1301 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Blocked
-
RUST-1792 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Blocked
-
CSHARP-4831 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Closed
-
GODRIVER-3036 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Closed
-
MOTOR-1206 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Closed
-
NODE-5724 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Closed
-
PYTHON-4022 Clarify whether heartbeat started event should be emitted before connection establishment in ServerMonitor
- Closed