added screen that shows transaction graph per hour, day and month

[woutslakhorst]

part of #36

this PR adds a page with three graphs showing transaction counts.

Next step is to show counts per type of transactions.
Then show a top 10 of DID controllers with the most transactions total.
Then connect Nats

[woutslakhorst]

I'm positioning this as a cheap stand-alone solution. A different approach would be exporting it as metric to a hosted tool like Datadog. That would involve more setup and would not make it available for everyone.

[reinkrul]

Intellectual exercise, but weren't there libraries we could simply drop in? (Prometheus-esque?)

[woutslakhorst]

Yes, but your deployment will also require 2 additional containers (prometheus and grafana), this requires additional devops work and costs for hosting.

This app is currently only for the foundation to track production network health. This is the quick and dirty solution for visualising something.

[reinkrul]

app has to be restarted to show new data?

[woutslakhorst]

As shown in the PR description, wip: Then connect Nats

[reinkrul]

I think using something like Prometheus will support future use cases better, e.g. it allows you to add labels (which can be a TX type, for example).

[gerardsn]

access not protected by the window.mutex, not sure if it matters here

[woutslakhorst]

yup, ran it with -race and it failed

[gerardsn]

still not protected?

[woutslakhorst]

Mutex has been placed on Public methods. This does not totally block things for the store (same package), it's more a convention. Otherwise you get lock-spaghetti or window needs its own package (overkill)

[woutslakhorst]

I think using something like Prometheus will support future use cases better, e.g. it allows you to add labels (which can be a TX type, for example).

There shouldn't be future use-cases.

• VC TXs are going to OID4C
• DID updates are going to did:web probably
• Assertions will feature a different mechanism probably

[reinkrul]

I think using something like Prometheus will support future use cases better, e.g. it allows you to add labels (which can be a TX type, for example).

There shouldn't be future use-cases.

• VC TXs are going to OID4C
• DID updates are going to did:web probably
• Assertions will feature a different mechanism probably

OK

[gerardsn]

From the time.Truncate docs

	t, _ := time.Parse("2006 Jan 02 15:04:05", "2012 Dec 07 12:15:30.918273645")
        ...
	// To round to the last midnight in the local timezone, create a new Date.
	midnight := time.Date(t.Year(), t.Month(), t.Day(), 0, 0, 0, 0, time.Local)

not sure if it is worth the extra complexity, but this seems to be the way to truncate the 24h resolution the 30 day graph

[reinkrul]

Didn't review custom sliding window.

[gerardsn]

still not protected?