Aurélien Rainone

Currently statsviz creates a new connection for each client/browser that connects to it. For each connection there's a once per second timer that gets the stats. The orignal use case...

Bugs, features... That's just different point of views 😅😅 But yes I think that statsviz should be restructured so that there's a single timer for N client connections. Shouldn't be...

We should switch to SSE and not keep an option websockets/SSE. Has no use for the user

> I've noticed no movement for a week. Is there something wrong with this pr? Hi. just haven't got the time yet

@zsy619 Did you find the problem? I'm sorry I don't know the beego library. However the examples directory shows how to configure statsviz with many other libraries/frameworks. Maybe there's one...

I don't know beego myself, some examples have been added by the community. If you know how to fix that please don't hesitate to open a PR

> > ```go > > web.Any(defaultStatsvizPrefix+":path([\\w]+)", func(ctx *context.Context) { > > statsviz.Index.ServeHTTP(ctx.ResponseWriter, ctx.Request) > > }) > > ``` > > `defaultStatsvizPrefix+":path([\\w]+)"` It looks like it doesn't match the multi-level...

Hi @zsy619 No there's no example to use statsviz with beego. I've never used it personally. I'm happy to review and merge any pull-request, that's a good issue for anyone...

Thanks for reporting. However this project was developed at a time where python3 was not the norm, so it's probably not compatible, though I'm sure this would be a quick...

Oh that's nice.I'd gladly accept a PR, if you confirm it works on your Mac ;-)