+
+ 
-
- 
+
+ 
-
- 
+
+ 
## Backstage icon
diff --git a/docs/overview/stability-index.md b/docs/overview/stability-index.md
index 4172e4d1b7..6882f3d6c2 100644
--- a/docs/overview/stability-index.md
+++ b/docs/overview/stability-index.md
@@ -153,6 +153,13 @@ re-exported from @backstage/core, and this package should not be used directly.
Stability: See @backstage/core
+### `cost-insights` [GitHub](https://github.com/backstage/backstage/tree/master/plugins/cost-insights)
+
+A frontend plugin that allows users to visualize, understand and optimize your
+team's cloud costs.
+
+Stability: `1`
+
### `create-app` [GitHub](https://github.com/backstage/backstage/tree/master/packages/create-app/)
The CLI used to scaffold new Backstage projects.
@@ -359,7 +366,7 @@ https://github.com/backstage/backstage/issues/2771.
### `tech-radar` [GitHub](https://github.com/backstage/backstage/tree/master/plugins/tech-radar/)
-Visualize the your company's official guidelines of different areas of software
+Visualize your company's official guidelines of different areas of software
development.
Stability: `0`
diff --git a/docs/plugins/integrating-plugin-into-service-catalog.md b/docs/plugins/integrating-plugin-into-service-catalog.md
index 01de779635..047b6f14e6 100644
--- a/docs/plugins/integrating-plugin-into-service-catalog.md
+++ b/docs/plugins/integrating-plugin-into-service-catalog.md
@@ -1,7 +1,7 @@
---
id: integrating-plugin-into-service-catalog
title: Integrate into the Service Catalog
-description: Documentation on How to integrate plugin into service catalog
+description: How to integrate a plugin into service catalog
---
> This is an advanced use case and currently is an experimental feature. Expect
diff --git a/docs/plugins/observability.md b/docs/plugins/observability.md
index de6f4bf988..b5a6a0ba60 100644
--- a/docs/plugins/observability.md
+++ b/docs/plugins/observability.md
@@ -13,6 +13,11 @@ Backstage integrator.
See how to install Google Analytics in your app
[here](../integrations/google-analytics/installation.md)
+## Datadog RUM Events
+
+See how to install Datadog Events in your app
+[here](../integrations/datadog-rum/installation.md)
+
## Logging
The backend supplies a central [winston](https://github.com/winstonjs/winston)
diff --git a/docs/plugins/proxying.md b/docs/plugins/proxying.md
index 50c56af7a6..3e20e37cad 100644
--- a/docs/plugins/proxying.md
+++ b/docs/plugins/proxying.md
@@ -36,7 +36,7 @@ Example:
```yaml
# in app-config.yaml
proxy:
- '/simple-example': http://simple.example.com:8080
+ simple-example: http://simple.example.com:8080
'/larger-example/v1':
target: http://larger.example.com:8080/svc.v1
headers:
@@ -46,10 +46,11 @@ proxy:
```
Each key under the proxy configuration entry is a route to match, below the
-prefix that the proxy plugin is mounted on. It must start with a slash. For
-example, if the backend mounts the proxy plugin as `/proxy`, the above
-configuration will lead to the proxy acting on backend requests to
-`/api/proxy/simple-example/...` and `/api/proxy/larger-example/v1/...`.
+prefix that the proxy plugin is mounted on. If it does not start with a slash,
+one will be prefixed automatically. For example, if the backend mounts the proxy
+plugin as `/proxy`, the above configuration will lead to the proxy acting on
+backend requests to `/api/proxy/simple-example/...` and
+`/api/proxy/larger-example/v1/...`.
The value inside each route is either a simple URL string, or an object on the
format accepted by
diff --git a/docs/plugins/structure-of-a-plugin.md b/docs/plugins/structure-of-a-plugin.md
index 2aacd02cf2..f81e3794e5 100644
--- a/docs/plugins/structure-of-a-plugin.md
+++ b/docs/plugins/structure-of-a-plugin.md
@@ -100,8 +100,7 @@ There are three things needed for a Backstage app to start making use of a
plugin.
1. Add plugin as dependency in `app/package.json`
-2. `import` plugin in `app/src/plugins.ts`
-3. Import and use one or more plugin extensions, for example in
+2. Import and use one or more plugin extensions, for example in
`app/src/App.tsx`.
Luckily these three steps happen automatically when you create a plugin with the
diff --git a/docs/tutorials/switching-sqlite-postgres.md b/docs/tutorials/switching-sqlite-postgres.md
index a759b7dc49..fafd2ad586 100644
--- a/docs/tutorials/switching-sqlite-postgres.md
+++ b/docs/tutorials/switching-sqlite-postgres.md
@@ -17,11 +17,11 @@ switch between database backends.
## Install PostgreSQL
-First, swap out SQLite for PostgreSQL in your `backend` package:
+First, add PostgreSQL to your `backend` package:
```shell
+# From your Backstage root directory
cd packages/backend
-yarn remove sqlite3
yarn add pg
```
@@ -46,7 +46,6 @@ backend:
+ #ssl: require # see https://www.postgresql.org/docs/current/libpq-ssl.html Table 33.1. SSL Mode Descriptions (e.g. require)
+ #ca: # if you have a CA file and want to verify it you can uncomment this section
+ #$file: 
+ 
+ 
+ 
+ 