integration service description

content/en/docs/features/monitoring-and-diagnostics/disaster-recovery.md

@@ -74,7 +74,7 @@ To back up the database, two approaches can be used:
 
      ![active-backup-replica-set](/docs/features/monitoring-and-diagnostics/static/disaster-recovery-active-replica-set-backup.drawio.svg)
 
-     The primary and standby cluster MongoDB members are in the same MongoDB replica set. The standby cluster members are configured as [hidden](https://www.mongodb.com/docs/manual/core/replica-set-hidden-member), [delayed](https://www.mongodb.com/docs/manual/core/replica-set-delayed-member/), and with [zero priority](https://www.mongodb.com/docs/manual/core/replica-set-priority-0-member/). When the primary cluster goes down, the standby cluster MongoDB members are promoted to standby state—one of them will become primary. After the primary is back online, the primary cluster members will be demoted to hidden. For switching back, the primary cluster members will be promoted to standby MongoDB members and standby cluster members will be demoted. **This approach is supported by the plgd hub helm chart because it complies with the MongoDB Community Server license.** For setup instructions, please refer to this [tutorial]().
+     The primary and standby cluster MongoDB members are in the same MongoDB replica set. The standby cluster members are configured as [hidden](https://www.mongodb.com/docs/manual/core/replica-set-hidden-member), [delayed](https://www.mongodb.com/docs/manual/core/replica-set-delayed-member/), and with [zero priority](https://www.mongodb.com/docs/manual/core/replica-set-priority-0-member/). When the primary cluster goes down, the standby cluster MongoDB members are promoted to standby state—one of them will become primary by administrator. After the primary is back online, the primary cluster members will be demoted to hidden. For switching back, the primary cluster members will be promoted to secondary MongoDB members and standby cluster members will be demoted. **This approach is supported by the plgd hub helm chart because it complies with the MongoDB Community Server license.** For setup instructions, please refer to this [tutorial]().
 
    * **Cluster to cluster synchronization**
 

content/en/docs/services/integration-service/_index.md

@@ -0,0 +1,4 @@
+---
+title: 'Integration Service'
+weight: 60
+---

content/en/docs/services/integration-service/features.md

@@ -0,0 +1,25 @@
+---
+title: 'Features'
+description: 'What features does the Integration Service provide?'
+date: '2024-06-14'
+categories: [events, iot, integration]
+keywords: [event streaming, integration service, plgd hub]
+weight: 3
+---
+
+### Planned Features
+
+- **☐ Event Stream Management:** Seamlessly stream events from the plgd hub to a wide range of external services. Configure rules to control which events are transmitted and where they are sent.
+
+- **☐ Advanced Filtration Mechanism:** Enhance event filtering with options including:
+   - **Device ID:** Filter events based on the unique identifier of the originating device.
+   - **Href:** Utilize the href attribute for event selection.
+   - **Resource Types:** Specify resource types to target events relevant to particular data types.
+   - **Event Type:** Differentiate events based on their type.
+   - **Content Filtering:** Apply jq expressions for advanced content-based filtering.
+
+- **☐ Supported Target Services:**
+   - **HTTP:** Integrate with web services and APIs via HTTP endpoints.
+   - **NATS:** Use the NATS messaging system for distributed event streaming.
+
+- **☐ Dynamic Target Parameters:** Define target parameters using templates with placeholders to dynamically populate values from event content, ensuring accurate data delivery to external services.

content/en/docs/services/integration-service/integration-service.md

@@ -0,0 +1,27 @@
+---
+title: 'Integration Service'
+description: 'What is Integration service?'
+date: '2024-06-14'
+lastmod: '2024-06-14'
+categories: [events, iot, integration]
+keywords: [event streaming, integration service]
+weight: 1
+isMainSectionPage: true
+---
+
+{{< note >}}
+
+Planned feature.
+
+{{< /note >}}
+
+The Integration Service is a key component of the plgd hub, designed to streamline the flow of event data to various external services. This service enhances connectivity and interoperability by allowing users to define and manage the transmission of events based on specific content and criteria.
+
+#### Benefits
+
+- **Customizable Event Routing:** Tailor the event routing rules to meet specific application needs, ensuring only relevant data reaches the target services.
+- **Scalability:** Integrate with multiple external services and scale event handling as your system grows.
+- **Enhanced Data Control:** Maintain granular control over data flow with robust filtering options, enhancing both security and efficiency.
+- **Flexibility:** The template-based approach for target parameters ensures flexibility and adaptability to various external service requirements.
+
+The Integration Service is an essential tool for developers and system integrators looking to enhance their event-driven architectures with precise, rule-based event streaming capabilities.