paulononato/backstage
1
0
Fork 0
Code Issues Pull Requests Actions 36 Packages Projects Releases Wiki Activity

Rename locations -> instances

Browse Source 
Signed-off-by: Julio Zynger <julio.zynger@soundcloud.com>
This commit is contained in:
Julio Zynger
2022-03-01 10:28:53 +01:00
committed by Fredrik Adelöw
parent f6e22fb230
commit 171be275ae
8 changed files with 54 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugins/periskop/README.md
+6 -5
View File
@@ -20,15 +20,16 @@ annotations:
periskop.io/name: '<THE NAME OF THE PERISKOP APP>'
```
### Locations
### Instances
The periskop plugin can be configured to fetch aggregated errors from multiple deployment locations. 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 locations will be included in the plugin's UI via a dropdown on the errors table.
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](https://github.com/backstage/backstage/blob/master/app-config.yaml):
```yaml
periskop:
locations:
- name: <name of the location>
host: <HTTP/S host for the Periskop API location>
instances:
- name: <name of the instance>
host: <HTTP/S host for the Periskop API instance>
```