You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The PR of #119 implements the multiple subscription protocol.
However implementing metrics for the new protocol have been neglected, and one of the old metric endpoints is re-used and do not capture the semantic significance.
When a new client creates a multi-subscription connection, icepeak counts it as a subscriber, whereas in reality it can create more than one subscription.
The metrics that icepeak records can be found here:
"Duration of HTTP requests since starting Icepeak.")
defaultBuckets
syncBuckets = exponentialBuckets 0.001212
We should create a new set of metric endpoints which capture data in accordance to how the new protocol functions. This could include:
Number of subscriptions made on MultiSub protocol
Number of connections on the MultiSub protocol
Number of subscription deadline timeouts
Payload failures
We also want to disambiguate the existing icepeak_subscriber_count to be explicitly SingleSub protocol connection count. Luckily icepeak_subscriber_count is the only metric that is fully tied to the SingleSub semantics.
The text was updated successfully, but these errors were encountered:
The PR of #119 implements the multiple subscription protocol.
However implementing metrics for the new protocol have been neglected, and one of the old metric endpoints is re-used and do not capture the semantic significance.
i.e:
icepeak/server/src/Icepeak/Server/WebsocketServer/MultiSubscription.hs
Lines 283 to 285 in 1e991b2
When a new client creates a multi-subscription connection, icepeak counts it as a subscriber, whereas in reality it can create more than one subscription.
The metrics that icepeak records can be found here:
icepeak/server/src/Icepeak/Server/Metrics.hs
Lines 40 to 73 in 1e991b2
We should create a new set of metric endpoints which capture data in accordance to how the new protocol functions. This could include:
We also want to disambiguate the existing
icepeak_subscriber_count
to be explicitly SingleSub protocol connection count. Luckilyicepeak_subscriber_count
is the only metric that is fully tied to the SingleSub semantics.The text was updated successfully, but these errors were encountered: