update donate docs: we have metrics now authored by anarcat's avatar anarcat
Closes: tpo/web/donate-neo#75
...@@ -826,9 +826,6 @@ that will pop alerts on IRC if problems come up with the service. All ...@@ -826,9 +826,6 @@ that will pop alerts on IRC if problems come up with the service. All
of them have playbooks that link to the [pager playbook](#pager-playbook) section of them have playbooks that link to the [pager playbook](#pager-playbook) section
here. here.
We currently don't correctly cover for failed transactions, see
[tpo/web/donate-neo#116](https://gitlab.torproject.org/tpo/web/donate-neo/-/issues/116).
The [donate neo donations](https://grafana.torproject.org/d/f36842c2-af41-48c2-ab71-442307ba2f75/donate-neo-donations) dashboard is the main view of the The [donate neo donations](https://grafana.torproject.org/d/f36842c2-af41-48c2-ab71-442307ba2f75/donate-neo-donations) dashboard is the main view of the
service in Grafana. It shows the state of the CiviCRM kill switch, service in Grafana. It shows the state of the CiviCRM kill switch,
transaction rates, errors, the rate limiter, and exception counts. It transaction rates, errors, the rate limiter, and exception counts. It
...@@ -838,8 +835,6 @@ draw correlations if there are issues with the service. ...@@ -838,8 +835,6 @@ draw correlations if there are issues with the service.
There are also links, on the top-right, to Django-specific dashboards There are also links, on the top-right, to Django-specific dashboards
that can be used to diagnose performance issues. that can be used to diagnose performance issues.
See [tpo/web/donate-neo#75](https://gitlab.torproject.org/tpo/web/donate-neo/-/issues/75) for followup on missing metrics.
Also note that the CiviCRM side of things has its own metrics, see the Also note that the CiviCRM side of things has its own metrics, see the
[CiviCRM monitoring and metrics documentation](service/crm#monitoring-and-metrics). [CiviCRM monitoring and metrics documentation](service/crm#monitoring-and-metrics).
... ...
......