Loading howto/cache.md +2 −2 Original line number Diff line number Diff line Loading @@ -124,7 +124,7 @@ Requests to the cache are logged to the disk in `/var/log/nginx/ssl.$hostname.access.log`, with IP address and user agent removed. Then [mtail](https://github.com/google/mtail) parses those log files and increments various counters and exposes those as metrics that are then scraped by [howto/prometheus](howto/prometheus). We use [howto/grafana](howto/grafana) to display that hit ratio which, at [Prometheus](service/prometheus). We use [Grafana](howto/grafana) to display that hit ratio which, at the time of writing, is about 88% for the blog. ### Puppet architecture Loading Loading @@ -316,7 +316,7 @@ contain accurate time records (granularity to the second) which might be exploited for correlation attacks. Nginx logs are fed into `mtail` to extract hit rate information, which is exported to [Prometheus](howto/prometheus), which, in turn, is used to create a is exported to [Prometheus](service/prometheus), which, in turn, is used to create a [Grafana](howto/grafana) [dashboard](https://grafana.torproject.org/d/p21-cvJWk/cache-health?orgId=1) which shows request and hit rates on the caching servers. Loading howto/grafana.md +4 −4 Original line number Diff line number Diff line [Grafana](https://grafana.com/) is a graphing engine and dashboard management tool that processes data from multiple data sources. We use it to trend various metrics collected from servers by [howto/Prometheus](howto/Prometheus). metrics collected from servers by [Prometheus](service/prometheus). Grafana is installed alongside Prometheus, on the same server. Those are the known instances: Loading @@ -8,7 +8,7 @@ are the known instances: * <https://grafana.torproject.org/> - internal server * <https://grafana2.torproject.org/> - external server See also the [Prometheus monitored services](howto/prometheus#monitored-services) to understand the See also the [Prometheus monitored services](service/prometheus#monitored-services) to understand the difference between the internal and external servers. [[_TOC_]] Loading Loading @@ -170,7 +170,7 @@ Grafana. ## Monitoring and testing Grafana itself is monitored by [Prometheus](howto/prometheus) and produces graphs for Grafana itself is monitored by [Prometheus](service/prometheus) and produces graphs for its own metrics. The test procedure is basically to login to the service and loading a Loading @@ -179,7 +179,7 @@ few dashboards. ## Logs and metrics Grafana doesn't hold metrics in itself, and delegates this task to external datasource. We use [Prometheus](howto/prometheus) for that purpose, but external datasource. We use [Prometheus](service/prometheus) for that purpose, but other backends could be used as well. Grafana logs incoming requests in `/var/log/grafana/grafana.log` and Loading howto/postgresql.md +1 −1 Original line number Diff line number Diff line Loading @@ -1755,7 +1755,7 @@ PostgreSQL keeps log files in `/var/log/postgresql/`, one per form of SQL queries. The log rotation policy is the one set by the Debian package and keeps logs for 10 weeks. [Prometheus](howto/prometheus) monitors the PosgreSQL servers through the [PostgreSQL [Prometheus](service/prometheus) monitors the PosgreSQL servers through the [PostgreSQL exporter][] deployed by Puppet through the `profile::prometheus::postgres_exporter` class. Loading howto/prometheus.md +1 −1 Original line number Diff line number Diff line Loading @@ -1086,7 +1086,7 @@ CONFIGURATION ERROR: The following notifications were sent via the default route that they had no team label matching one of the per-team routes. This should not be happening and it should be fixed. See: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/prometheus#reference https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/prometheus#reference Total firing alerts: 1 Loading meeting/2021-05-03.md +1 −1 Original line number Diff line number Diff line Loading @@ -28,7 +28,7 @@ contact us following this "how to get help" procedure: Yes, that's a terrible URL. Blame GitLab. :) [altering documentation]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/prometheus#alerting [altering documentation]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/prometheus#alerting [ticket 40347]: https://gitlab.torproject.org/tpo/core/tor/-/issues/40347 [ticket 32920]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32920 [ticket 40233]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40233 Loading Loading
howto/cache.md +2 −2 Original line number Diff line number Diff line Loading @@ -124,7 +124,7 @@ Requests to the cache are logged to the disk in `/var/log/nginx/ssl.$hostname.access.log`, with IP address and user agent removed. Then [mtail](https://github.com/google/mtail) parses those log files and increments various counters and exposes those as metrics that are then scraped by [howto/prometheus](howto/prometheus). We use [howto/grafana](howto/grafana) to display that hit ratio which, at [Prometheus](service/prometheus). We use [Grafana](howto/grafana) to display that hit ratio which, at the time of writing, is about 88% for the blog. ### Puppet architecture Loading Loading @@ -316,7 +316,7 @@ contain accurate time records (granularity to the second) which might be exploited for correlation attacks. Nginx logs are fed into `mtail` to extract hit rate information, which is exported to [Prometheus](howto/prometheus), which, in turn, is used to create a is exported to [Prometheus](service/prometheus), which, in turn, is used to create a [Grafana](howto/grafana) [dashboard](https://grafana.torproject.org/d/p21-cvJWk/cache-health?orgId=1) which shows request and hit rates on the caching servers. Loading
howto/grafana.md +4 −4 Original line number Diff line number Diff line [Grafana](https://grafana.com/) is a graphing engine and dashboard management tool that processes data from multiple data sources. We use it to trend various metrics collected from servers by [howto/Prometheus](howto/Prometheus). metrics collected from servers by [Prometheus](service/prometheus). Grafana is installed alongside Prometheus, on the same server. Those are the known instances: Loading @@ -8,7 +8,7 @@ are the known instances: * <https://grafana.torproject.org/> - internal server * <https://grafana2.torproject.org/> - external server See also the [Prometheus monitored services](howto/prometheus#monitored-services) to understand the See also the [Prometheus monitored services](service/prometheus#monitored-services) to understand the difference between the internal and external servers. [[_TOC_]] Loading Loading @@ -170,7 +170,7 @@ Grafana. ## Monitoring and testing Grafana itself is monitored by [Prometheus](howto/prometheus) and produces graphs for Grafana itself is monitored by [Prometheus](service/prometheus) and produces graphs for its own metrics. The test procedure is basically to login to the service and loading a Loading @@ -179,7 +179,7 @@ few dashboards. ## Logs and metrics Grafana doesn't hold metrics in itself, and delegates this task to external datasource. We use [Prometheus](howto/prometheus) for that purpose, but external datasource. We use [Prometheus](service/prometheus) for that purpose, but other backends could be used as well. Grafana logs incoming requests in `/var/log/grafana/grafana.log` and Loading
howto/postgresql.md +1 −1 Original line number Diff line number Diff line Loading @@ -1755,7 +1755,7 @@ PostgreSQL keeps log files in `/var/log/postgresql/`, one per form of SQL queries. The log rotation policy is the one set by the Debian package and keeps logs for 10 weeks. [Prometheus](howto/prometheus) monitors the PosgreSQL servers through the [PostgreSQL [Prometheus](service/prometheus) monitors the PosgreSQL servers through the [PostgreSQL exporter][] deployed by Puppet through the `profile::prometheus::postgres_exporter` class. Loading
howto/prometheus.md +1 −1 Original line number Diff line number Diff line Loading @@ -1086,7 +1086,7 @@ CONFIGURATION ERROR: The following notifications were sent via the default route that they had no team label matching one of the per-team routes. This should not be happening and it should be fixed. See: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/prometheus#reference https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/prometheus#reference Total firing alerts: 1 Loading
meeting/2021-05-03.md +1 −1 Original line number Diff line number Diff line Loading @@ -28,7 +28,7 @@ contact us following this "how to get help" procedure: Yes, that's a terrible URL. Blame GitLab. :) [altering documentation]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/prometheus#alerting [altering documentation]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/service/prometheus#alerting [ticket 40347]: https://gitlab.torproject.org/tpo/core/tor/-/issues/40347 [ticket 32920]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/32920 [ticket 40233]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40233 Loading