Pull based, language agnostic exception aggregator for microservice environments.
Periskop scales well with the number of exceptions and application instances:
- Exceptions are pre-aggregated in client libraries and stored efficiently in memory, while keeping a sample of concrete occurrences for inspection.
- Exceptions are scraped and aggregated across instances by the server component.
- More application instances result in longer refresh cycles but the memory usage remains constant.
A UI component is provided for convenience.
Scraping
Errors are scraped and aggregated using a configured endpoint from each of the instances discovered via service discovery.
Periskop supports all service discovery mechanisms supported by Prometheus. The configuration format for service discovery mirrors the one from Prometheus. See Prometheus's official documentation for reference.
A full example of service configuration for Periskop can be found in the sample configuration.
Format
The format for scraped errors is defined in a proto3 IDL. Currently the only supported protocol is snake_cased JSON over HTTP (example).
UI
The UI allows navigating and inspecting exceptions as they occur.
Run project locally
Please see CONTRIBUTING.md
Building & Running
We are looking into distributing Periskop via Docker Hub. In the meantime, you can build and run Periskop from source:
docker build --tag periskop .
docker run -v path/to/config.yaml:/etc/periskop/periskop.yaml -p 8080:8080 periskop
Enable persistance storage
By default Periskop stores all the scrapped errors in memory repository. You can configure your Periskop deployment to use persistent storage. Currently the supported persistance storages are SQLite, MySQL and PostgreSQL.
For SQLite, add these lines to your config.yaml file:
repository:
type: sqlite
path: periskop.dbFor MySQL:
repository:
type: mysql
dsn: user:pass@tcp(127.0.0.1:3306)/dbname?charset=utf8mb4&parseTime=True&loc=LocalFor PostgreSQL:
repository:
type: postgres
dsn: host=localhost user=gorm password=gorm dbname=gorm port=9920 sslmode=disableAlert reported exceptions
All reported errors are instrumented with Prometheus which provides alerting capabilities using Alertmanager. You can configure an alert when you reach some threshold of errors. Here's an example:
groups:
- name: periskop
rules:
- alert: TooManyErrors
expr: periskop_error_occurrences{severity="error"} > 1000
for: 5m
labels:
severity: critical
annotations:
summary: "Too many errors on {{ $labels.service_name }}"
description: "Errors for {{ $labels.service_name }}({{ $labels.aggregation_key }}) is {{ $value }}"
dashboard: "https://periskop.example.com/#/{{ $labels.service_name }}/errors/{{ $labels.aggregation_key }}"Pushgateway
See periskop-pushgateway if you want to use Periskop as push based metric system.
Client Libraries
Integrations
