-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect displaying of stored_messages in statistics #267
Comments
Hi @materkov can you confirm some info?
The counters goes together, except for event_channel, since the messages stored there are not send by the user. For example, If a user connects to the push stream, send a message to channel "A" and disconnect, the channel "A" will have 1 stored message, the global counter for stored message will also be 1, but the events channel may have 3 messages, 1 saying that someone subscribe the channel, 1 saying that a message was sent, and another one saying that someone unsubscribe the channel. |
Ok, I don't know about the case that events channel messages were not counted. I've tried another expirement. I've downloaded detailed info about all channels (?id=ALL), and then summarize all channels. Even without events channel, there should be about ~3k of stored messages. But total stats shows really weird number (it even shows 0 sometimes). |
Here is another expirement. I've pulled /stats info every second, here is some result (with some detail cutted):
As you can see, published_messages grows, but stored_messages show weird number. TTL is 10 mintutes in config:
|
What is the limit you set for the message queue length? (if any) |
Hi, @wandenberg
It looks like that push stream module statistics can display wrong values for "stored_messages". For example, it now looks like this:
stored_messages always shows very low value (less than 20). If i look for stats for some specific channel (?id=CHANNEL_NAME):
So, here is 1039, but in general stats the value is too low.
Could you please check this?
The text was updated successfully, but these errors were encountered: