matrix-org / matrix-org/matrix-viewer

Add traffic metrics

Open
#162 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-metrics T-Enhancement
Dominant language
JavaScript
Stars
84
Forks
10
PR merge metrics
No merged PRs in 30d

Description

Add traffic metrics to see how many people are using it.

Do we need to add anything special to make this happen? Can we already derive this information from some existing metrics we get from K8s? Perhaps the `nginx/nginx-ingress-controller` dashboards ([example](https://grafana.infra.element.io/d/nginx/nginx-ingress-controller?orgId=1&refresh=5s&var-DS_PROMETHEUS=VictoriaMetrics&var-namespace=All&var-controller_class=k8s.io%2Fpublic-ingress-nginx&var-controller=All&var-ingress=gitter-im))

Should we derive this info from the response metrics? https://github.com/matrix-org/matrix-public-archive/issues/45 (also see that issue for Prometheus notes)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing Kubernetes and response metrics, the nginx ingress dashboard example, and the Prometheus notes in matrix-public-archive issue 45. Clarify which traffic measurement is required and what existing data can support it; done should include an agreed metric and a way to verify its values.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes, nginx, prometheus
Domain
infrastructure, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.