[*] mention pgwatch-contrib/rpc in docs (#922)

* add link to sinks options page in `index.md`

* mention usage of `--sink` in `sinks_options.md`

* add `How To: Implement your own gRPC Server` page to docs

* [*] mention `pgwatch-contrib/rpc` instead of `pgwatch_rpc_server`

Co-authored-by: Pavlo Golub <[email protected]>

* [*] mention `pgwatch-contrib/rpc`

Co-authored-by: Pavlo Golub <[email protected]>

* rename header to `pgwatch contrib RPC`

- substitute all mentions of pgwatch_rpc_server with pgwatch contrib

---------

Co-authored-by: Pavlo Golub <[email protected]>

Author: 0xgouda

docs/howto/implement_grpc_server.md

@@ -0,0 +1,21 @@
+---
+title: Implement your own gRPC Server
+---
+
+To use pgwatch’s [gRPC sink](../concept/components.md#grpc), you must 
+provide the URI of a custom gRPC server that integrates with pgwatch using its 
+[protobuf definition](https://github.com/cybertec-postgresql/pgwatch/blob/master/api/pb/pgwatch.proto).  
+See also [gRPC Sink URI Parameters](../reference/sinks_options.md#grpc).
+
+## pgwatch contrib RPC
+
+[pgwatch-contrib/rpc](https://github.com/cybertec-postgresql/pgwatch-contrib/tree/main/rpc) 
+is a **community-maintained** collection of gRPC server implementations for pgwatch.
+
+It provides servers for common data solutions but makes no guarantees about 
+their suitability for production use. Its main purpose is to provide 
+examples and building blocks that users can extend to integrate with pgwatch 
+and develop their own production-ready gRPC servers.
+
+For guidance on implementing a custom gRPC server sink, refer to this
+[tutorial](https://github.com/cybertec-postgresql/pgwatch-contrib/blob/main/rpc/TUTORIAL.md).

docs/index.md

@@ -40,7 +40,7 @@ In addition to the standard metrics, pgwatch can be easily extended to monitor *
 
 **Where are the measurements stored and where can users inspect the dashboards?**
 
-- pgwatch allows users to choose from a variety of **storage backends** aka **sinks** for storing monitoring data, such as JSON file, TimescaleDB, Prometheus, PostgreSQL, or a custom gRPC-based backend.
+- pgwatch allows users to choose from a variety of **storage backends** aka [**sinks**](./reference/sinks_options.md) for storing monitoring data, such as JSON file, TimescaleDB, Prometheus, PostgreSQL, or a custom gRPC-based backend.
 - The **user interface** for pgwatch is powered by **Grafana dashboards**, providing interactive and detailed visualization of the collected metrics. Users can easily view the performance and status of their databases in real-time, drill down into historical data, and configure custom dashboard views based on their preferences.
 
 For a detailed list of all features and capabilities, please refer to the [Features](intro/features.md) page.

docs/reference/sinks_options.md

@@ -1,5 +1,7 @@
 # Sinks Options & Parameters
 
+- Sinks URIs should be provided to pgwatch via the `--sink` flag, which can be used more than once, see [CLI & Envs](./cli_env.md#sinks).
+
 ## PostgreSQL
 
 The PostgreSQL sink URI format is the standard [PostgreSQL connection string](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNSTRING-URIS),
@@ -42,7 +44,7 @@ The gRPC sink URI format is
 
 The gRPC sink supports optional **authentication** and **TLS encryption** over the RPC channel.
 
-For authentication credentials can be provided using the `username:password` format in the URI string,
+For authentication, credentials can be provided using the `username:password` format in the URI string,
 e.g. `--sink=grpc://user:pwd@localhost:5000/`.
 If omitted, defaults to empty string for both username and password.
 The values are then forwarded to the gRPC server under the `"username"` and `"password"` fields in the metadata.

mkdocs.yml

@@ -67,6 +67,7 @@ nav:
     - Bootstrapping the Configuration Database: howto/config_db_bootstrap.md
     - Bootstraping the Measurements Database (Sink): howto/metrics_db_bootstrap.md
     - Migration from pgwatch v2: howto/migrate_v2_to_v3.md
+    - Implement Сustom gRPC Sink: howto/implement_grpc_server.md
   - Reference:
     - CLI & Environment Variables: reference/cli_env.md
     - REST API: reference/rest.md