[Fix] remove references from old services

Author: MattDodsonEnglish

content/latest/how-to/bpmn/bpmn-elements.md

@@ -122,7 +122,7 @@ The parameters for a timer start event are as follows:
 
 ### Intermediate message events
 
-Intermediate message events throw a message to the Rhize NATS broker.
+Intermediate message events throw a message to the Rhize broker.
 This may provide info for a subscribing third-party client, or initiate another BPMN workflow.
 
 The parameters for an intermediate message event are as follows:

content/latest/how-to/bpmn/create-workflow.md

@@ -92,7 +92,7 @@ width="60%"
 
 The strategy you choose to send and receive message data depends on your architectural setup. 
 Generally, data-source messages come from level-1 and level-2 devices on the edge,
-and messages published to the Rhize broker come from any NATS, MQTT, or OPC UA client.
+and messages published to the Rhize broker come from any MQTT or OPC UA client.
 The following diagram shows some common ways to interact with messages through BPMN.
 
 {{< bigFigure

content/latest/how-to/bpmn/naming-conventions.md

@@ -36,14 +36,11 @@ Where:
 
 | InvocationTypes | Description                                                                                    |
 |-----------------|------------------------------------------------------------------------------------------------|
-| `NATS`          | Invoked when a message is received in the Rhize NATS broker                                    |
 | `API`           | Expects to be called from the API using `createAndRunBPMNSync` or `createAndRunBPMN` mutations |
 | `RULE`          | Invocation is expected from the [rule engine]({{< relref "../publish-subscribe/create-equipment-class-rule" >}})          |
 | `FUNC`          | Internal functions to be invoked as helpers                                                    |
 
 Examples:
-- `NATS_ProcessOrderV1TransformAndPersist`
-- `NATS_PLMMaterialMasterV2TransformPersistAndPublish`
 - `RULE_ChangeOEEStatusOfCNCEquipment`
 - `API_WST04_GetNextLibreBatchNumber`
 - `API_WAT01_CloseOpenJobOrders`

content/latest/how-to/bpmn/trigger-workflows.md

@@ -120,7 +120,7 @@ If the `version` property is empty, Rhize runs the active version of the workflo
 
 The [message start event]({{< relref "./bpmn-elements#message-start-event" >}}) subscribes to a topic on the Rhize broker.
 Whenever a message is published to this topic, the workflow is triggered.
-The Rhize broker can receive messages published over MQTT, NATS, and OPC UA.
+The Rhize broker can receive messages published over MQTT and OPC UA.
 
 For example, this workflow subscribes to the topic `material/stuff`.
 Whenever a message is published to the topic, it evaluates whether the quantity is in the correct threshold.

content/latest/how-to/bpmn/tune-performance.md

@@ -17,11 +17,6 @@ So an inefficient BPMN process can introduce performance degradations.
 
 ## Manage the process context size
 
-{{< callout type="info" >}}
-The max size of the process variable context comes from the default max payload size of NATS Jetstreams.
-To increase this size, change your NATS configuration.
-{{< /callout >}}
-
 By default, the size of the {{< abbr "process variable context" >}} is 1MB.
 If the sum size of all variables exceeds this limit, the BPMN process fails to execute.
 
@@ -67,7 +62,6 @@ If a process seems slow, look for these places to refactor performance.
 ### Avoid parallel joins
 
 Running processes in [parallel]({{< relref "./bpmn-elements#parallel-gateway" >}}) can increase the workflow's complexity.
-Parallel joins in particular can also increase memory usage of the NATS service.
 
 Where possible, prefer exclusive branching and sequential execution.
 When a task requires concurrency, keep the amount of data processed and the complexity of the tasks to the minimum necessary.

content/latest/how-to/model/master-definitions.md

@@ -80,7 +80,7 @@ Each topic has the following fields:
 | Topic field       | Description                                                                   |
 |-------------------|-------------------------------------------------------------------------------|
 | Data type         | The data type Rhize expects to find when it receives data from that topic     |
-| Deduplication key | The field that NATS uses to de-duplicate messages from multiple data sources. |
+| Deduplication key | The field to de-duplicate messages from multiple data sources. |
 | Label             | The name of the topic on the side of the data source                          |
 | Description       | A freeform text field to add context                                          |
 

content/latest/how-to/publish-subscribe/track-changes.md

@@ -10,7 +10,7 @@ aliases:
 You can use _change data capture_ (CDC) to track data changes over time, including
 a {{< abbr "mutation" >}} or drop in your database.
 Rhize's CDC implementation can use
-Kafka, NATS, or a local file as a *{{< abbr "sink" >}}* to store CDC updates streamed by Rhize's Alpha
+Kafka or a local file as a *{{< abbr "sink" >}}* to store CDC updates streamed by Rhize's Alpha
 leader nodes.
 
 When CDC is enabled, Rhize streams events for:
@@ -55,16 +55,6 @@ with the `--cdc` command and the sub-option shown below, as follows:
 dgraph alpha --cdc "file=local-file-path"
 ```
 
-## Enable CDC with NATS JetStream KV store sink
-
-To enable CDC and sink results to a NATS JetStream KV store, start Dgraph Alpha
-with the `--cdc` command and the sub-option shown below, as follows:
-
-```bash
-dgraph alpha --cdc "nats=nats://system:system@localhost:4222"
-```
-
-
 ## CDC command reference
 
 The `--cdc` option includes several sub-options that you can use to configure
@@ -78,7 +68,6 @@ CDC when running the `dgraph alpha` command:
 | `client-cert`    | `--cdc "client-cert=/c-certs/client.crt"`                                | Path and filename of the client certificate used for TLS encryption                                              |
 | `client-key`     | `--cdc "client-cert=/c-certs/client.key"`                                | Path and filename of the client certificate private key                                                          |
 | `file`           | `--cdc "file=/sink-dir/cdc-file"`                                        | Path and filename of a local file sink (alternative to Kafka sink)                                               |
-| `nats`           | `--cdc "nats=nats://user:password@localhost:4222"`                       | URL connection string to nats sink (alternative to Kafka sink)                                                   |
 | `kafka`          | `--cdc "kafka=kafka-hostname; sasl-user=tstark; sasl-password=m3Ta11ic"` | Hostname(s) of the Kafka hosts. May require authentication using the `sasl-user` and `sasl-password` sub-options |
 | `sasl-user`      | `--cdc "kafka=kafka-hostname; sasl-user=tstark; sasl-password=m3Ta11ic"` | SASL username for Kafka. Requires the `kafka` and `sasl-password` sub-options                                    |
 | `sasl-password`  | `--cdc "kafka=kafka-hostname; sasl-user=tstark; sasl-password=m3Ta11ic"` | SASL password for Kafka. Requires the `kafka` and `sasl-username` sub-options                                    |

content/latest/reference/nats-configuration.md

@@ -21,13 +21,9 @@ The service metrics have endpoints at the following ports:
 |---------|-----------|---------|------|
 | Audit   | Y         | Y       | 8084 |
 | BAAS    | Y         | Y       | 8080 |
-| BPMN    | Y         | Y       | 8081 |
-| Core    | Y         | Y       | 8080 |
-| NATS    |           | Y       | 7777 |
 | Router  | Y         |         | 9090 |
 | Tempo   | Y         | Y       | 3100 |
 
-NATS has an available endpoint through an exporter that is present on the cluster.
 Router has an available endpoint that is disabled by default.
 
 ## Metrics configuration
@@ -46,42 +42,9 @@ For example:
   metrics_path: /metrics
   scheme: http
   static_configs:
-    - targets: ['audit-demo.demo.svc.cluster.local:8084', 'baas-alpha.demo.svc.cluster.local:8080', 'bpmn-demo.demo.svc.cluster.local:8081', 'core-demo.demo.svc.cluster.local:8080', 'grafana-demo.demo.svc.cluster.local:3000', 'tempo.demo.svc.cluster.local:3100', 'nats-demo-headless.demo.svc.cluster.local:7777', 'router-demo.demo.svc.cluster.local:9090']
+    - targets: ['audit-demo.demo.svc.cluster.local:8084', 'baas-alpha.demo.svc.cluster.local:8080', 'grafana-demo.demo.svc.cluster.local:3000', 'tempo.demo.svc.cluster.local:3100', 'router-demo.demo.svc.cluster.local:9090']
 ```
 
-### NATS
-
-While NATS has no available metrics endpoint, the cluster includes a [NATS Prometheus exporter](https://github.com/nats-io/prometheus-nats-exporter).
-NATS metrics are exposed through port `7777`.
-
-
-#### Cluster
-
-Since the cluster already includes the exporter, no further configuration is required.
-This endpoint should be connected through the NATS headless pod. For example:
-
-`nats-demo-headless.demo.svc.cluster.local:7777`
-
-#### Docker
-
-To get NATS metrics in Docker, use the exporter mentioned in the preceding section.
-The following is a sample docker-compose configuration for the exporter.
-
-```yaml
-services:
-	# -- Other services
-	nats-exporter:
-    image: natsio/prometheus-nats-exporter:latest
-    container_name: nats-exporter
-    command: "-varz 'http://nats:5555'"
-    depends_on:
-      - nats
-    ports:
-      - 7777:7777
-```
-
-Access NATS metrics at `localhost:7777/metrics`
-
 ### Router
 
 #### Cluster
@@ -138,6 +101,7 @@ This opens the metrics endpoint on port `9090`.
 To view it externally, you must expose the port in docker-compose.
 Once the port is exposed, view the metrics at `localhost:9090/metrics`
 
+
 ## Available Rhize microservice metrics
 
 Several common metrics appear between Rhize microservices:
@@ -150,17 +114,14 @@ Several common metrics appear between Rhize microservices:
 |---------|---------------------------------------------------|-----------------|---------------|------------|
 | Audit   | Y                                                 | Y               | Y             |            |
 | BAAS    | Y                                                 | Y               |               | Y          |
-| BPMN    | Y                                                 | Y               | Y             | Y          |
-| Core    | Y                                                 |                 | Y             |            |
-| NATS    | Y                                                 | Y               | Y             | Y          |
 | Router  |                                                   |                 |               | Y          |
 | Tempo   | Y                                                 |                 |               | Y          |
 
 {{< callout type="info" >}}
 HTTP metrics are noted as `promhttp`.
 {{< /callout >}}
 
-### BAAS
+
 
 Additional metrics on BAAS are from [dgraph](https://dgraph.io/docs/deploy/admin/metrics/). These include two categories: Badger and Dgraph.
 
@@ -194,66 +155,6 @@ dgraph_disk_free_bytes{dir="postings_fs"} 1.0153562112e+10
 dgraph_disk_total_bytes{dir="postings_fs"} 1.0447245312e+10
 ```
 
-### BPMN
-
-BPMN has four metrics unique to it, shown in full in the sample below.
-
-#### Sample
-
-```
-# HELP bpmn_execution_commands The number of BPMN commands that have started executing
-# TYPE bpmn_execution_commands counter
-bpmn_execution_commands 1162
-
-# HELP bpmn_instances_started BPMN Instances started but not necessarily completed
-# TYPE bpmn_instances_started counter
-bpmn_instances_started 166
-
-# HELP bpmn_queue_CommandConsumerQueue Number of BPMN Commands currently waiting to be executed
-# TYPE bpmn_queue_CommandConsumerQueue gauge
-bpmn_queue_CommandConsumerQueue 0
-
-# HELP bpmn_queue_StartOnNatsMessages Number of BPMN trigger messages received from NATS
-# TYPE bpmn_queue_StartOnNatsMessages gauge
-bpmn_queue_StartOnNatsMessages 0
-```
-
-### NATS
-
-NATS has two categories of metrics:
-- `gnatsd`
-- `jetstream`
-
-#### Sample
-
-```
-# HELP gnatsd_connz_in_bytes in_bytes
-# TYPE gnatsd_connz_in_bytes counter
-gnatsd_connz_in_bytes{server_id="nats-demo-0"} 0
-
-# HELP gnatsd_connz_in_msgs in_msgs
-# TYPE gnatsd_connz_in_msgs counter
-gnatsd_connz_in_msgs{server_id="nats-demo-0"} 0
-
-# HELP gnatsd_connz_limit limit
-# TYPE gnatsd_connz_limit gauge
-gnatsd_connz_limit{server_id="nats-demo-0"} 1024
-```
-
-```
-# HELP jetstream_server_jetstream_disabled JetStream disabled or not
-# TYPE jetstream_server_jetstream_disabled gauge
-jetstream_server_jetstream_disabled{cluster="nats-demo",domain="",is_meta_leader="false",meta_leader="nats-demo-1",server_id="nats-demo-0",server_name="nats-demo-0"} 0
-
-# HELP jetstream_server_max_memory JetStream Max Memory
-# TYPE jetstream_server_max_memory gauge
-jetstream_server_max_memory{cluster="nats-demo",domain="",is_meta_leader="false",meta_leader="nats-demo-1",server_id="nats-demo-0",server_name="nats-demo-0"} 2.147483648e+09
-
-# HELP jetstream_server_max_storage JetStream Max Storage
-# TYPE jetstream_server_max_storage gauge
-jetstream_server_max_storage{cluster="nats-demo",domain="",is_meta_leader="false",meta_leader="nats-demo-1",server_id="nats-demo-0",server_name="nats-demo-0"} 5.36870912e+10
-```
-
 ### Router
 
 All metrics provided by Router are unique to Apollo Router.

content/latest/reference/observability-metrics.md

@@ -13,7 +13,7 @@ The Rhize agent collects data that is emitted in the manufacturing process and m
 It works by connecting to equipment or groups of equipment that run over protocols such as OPC UA.
 
 As the communication bridge between the Rhize Data Hub and your plant, the agent has multiple functions:
-- It subscribes to tags and republishes the changes in NATS.
+- It subscribes to tags and republishes the changes in the messsage broker.
 - It creates an interface for the BPMN engine to send reads and writes to a data source and its associated equipment.
 
 
@@ -42,12 +42,6 @@ As the communication bridge between the Rhize Data Hub and your plant, the agent
 |---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `GRAPHQL_URL`         | The URL of the GraphQL endpoint to use for interacting with Rhize services. <br />(Default: `http://localhost:8080/graphql`) |
 
-## `NATS`
-
-| Attribute | Description |
-|---------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| `SERVER_URL`         | The URL for connecting to the NATS server. <br />(Default: `nats://system:system@localhost:4222`) | 
-
 ## `OIDC`
 
  Configurations for Keycloak authentication and connection with OpenID Connect.