benchklion.blogg.se - Grafana timeslice not working

GRAFANA TIMESLICE NOT WORKING UPDATE
GRAFANA TIMESLICE NOT WORKING FULL
GRAFANA TIMESLICE NOT WORKING CODE

Oskar: Other metric is retention or stickiness DAU/MAU.

Jakub: Could be quite skewed by e2e test.

Oskar: Connected peers, makes sense given number?.

Iuri: Found it suprising given activity on channel.

Oskar: … Other reasons to doubt accuracy of data.

Jakub: Included in PR - need to talk to them.

Custom status-go version to detect nodes.

Jakub: Alternative, modify logs to include names of peers, use in queries to limit.

Might not have upgraded version of Status-go.

GRAFANA TIMESLICE NOT WORKING CODE

Not running PR’s of unrelated code against staging. Andrea: need to be more careful with process.Jakub: Last time suggested there were objections.Not doable with Kibana now, needs to be written Substract peers for timeslice for given query. Jakub: Have to have indices, hold data by peers of e2e.Eric: Easier, more feasible to run script on time (last 24h).Jakub: requires custom solution to query.Could we collect from e2e peer id, collect and remove from metrics Jakub: QA wants to use what’s on production, this should be staging.Oskar: Need to understand impact of e2e testing.

Oskar: Source of truth for DAU and retention.Jakub: count now, take peer-ID of nodes connecetd to ouur nodes.Iuri: different measures on what’s an active user.Andre: Yes we need to ship, if we need to do a bit of double work, better than waiting.Andrea: will keep working on notification service and will see what comes first.Working on shim, and discuss again after implementing and having learned more about shim. Library in nim can surface encryption messages, but would need to send back to status-go. Doesn’t seem like something we want to do. Roughly speaking, means fairly big changes to status-go. Iuri: For keys acceptable to sign in status-go.

Clarity will help, else will need to write code in status-go Either nim that implements ipfs, not feasible in timeline or some other way. Nimbus provides a way to not write status-go, but nim and somehow integrate.

Andrea: PN server, Ideally don’t right any new code in Status go if we move away from this.

Oskar: 14:12 PN could be written in nim when integration is done.

Iuri: For Stimbus we have a path, starting with shim.

Oskar: Is the conclusion that tomorrow it will be clear who this would be?.

Count on Iuri and see who to involve from Desktop

Iuri: Discuss during kick-off integration call of Stimbus tomorrow.

Oskar: Not much different from what is worked on.

Oskar: Someone who speaks on behalf of core when it comes to integration.

Iuri: Integrating Desktop and Mobile into nim.

Missing someone from core, desktop and Stimbus and have a kickoff call.

GRAFANA TIMESLICE NOT WORKING UPDATE

Notifications on iOS (progress, decisions that have been made) - update (~10’).Layer2 solutions to remove gas cost barrier for in-Status SNT transactions - intro (~10’) Stimbus Implementation proposal - feedback (~10’)Ĭ. Specs review > open PR’s for Discussion (~10’)Ī.Layer 2 solution for Status Pay is being discussed.

GRAFANA TIMESLICE NOT WORKING FULL

The full list of Core Dev meetings can be found on GitHub. Meeting Date/Time: Monday at 12:00 UTC.The Status Core Development team meets every two weeks, here is a summary of their latest call.