Files
backstage/plugins/periskop
Julio Zynger 7bb98ee655 Rename host -> url
Signed-off-by: Julio Zynger <julio.zynger@soundcloud.com>
2022-03-07 15:05:55 +01:00
..
2022-03-07 15:05:32 +01:00
2022-03-07 15:05:32 +01:00
2022-03-07 15:05:55 +01:00
2022-03-07 15:05:32 +01:00
2022-03-07 15:05:32 +01:00
2022-03-07 15:05:55 +01:00
2022-03-07 15:05:53 +01:00
2022-03-07 15:05:55 +01:00

periskop

Periskop is a pull-based, language agnostic exception aggregator for microservice environments.

periskop-logo

PeriskopErrorsTable

The Periskop Backstage Plugin exposes an entity tab component named PeriskopErrorsTable. Each of the entries in the table will direct you to the error details in your deployed Periskop instance location.

periskop-errors-card

Now your plugin should be visible as a tab at the top of the entity pages. However, it warns of a missing periskop.io/name annotation.

Add the annotation to your component descriptor file as shown in the highlighted example below:

annotations:
  periskop.io/name: '<THE NAME OF THE PERISKOP APP>'

Instances

The periskop plugin can be configured to fetch aggregated errors from multiple deployment instances.
This is especially useful if you have a multi-zone deployment, or a federated setup and would like to drill deeper into a single instance of the federation. Each of the configured instances will be included in the plugin's UI via a dropdown on the errors table.

The plugin requires to configure at least one Periskop API location in the app-config.yaml:

periskop:
  instances:
    - name: <name of the instance>
      url: <HTTP/S url for the Periskop instance's API>