Differences

This shows you the differences between two versions of the page.

--- onboarding:elastic-replicator:start [2022/10/04 15:13] – 10.91.110.100
+++ onboarding:elastic-replicator:start [2024/08/29 11:28] (current) – 10.91.129.119
@@ Line 46: / Line 46: @@
 **Individual:**
-  - GET http://10.91.140.218:8100/bulk?routes=trap
+  - GET http://10.91.140.218:8100/elastic-replicator/bulk?routes=trap
-  - GET http://10.91.140.218:8100/bulk?routes=networkElement
+  - GET http://10.91.140.218:8100/elastic-replicator/bulk?routes=networkElement
-  - GET http://10.91.140.218:8100/bulk?routes=ticket
+  - GET http://10.91.140.218:8100/elastic-replicator/bulk?routes=ticket
-  - GET http://10.91.140.218:8100/bulk?routes=alarm
+  - GET http://10.91.140.218:8100/elastic-replicator/bulk?routes=activeAlarm
-  - GET http://10.91.140.218:8100/bulk?routes=uptime
+  - GET http://10.91.140.218:8100/elastic-replicator/bulk?routes=uptime
+**Limited individual**
+  - GET "http://10.91.140.218:8100/bulk?routes=uptime&start=1"
+to limit to 1 month back.
 **Bulk:**
@@ Line 78: / Line 83: @@
 /idms-proxy/api/v0/replicator
 </code>
+The SSE touchpoints for  processing are as follows(see also diagram below):
+  - Gorm listener events for ticket, alarm, element inserts or updates are pushed from Ticketer and SnmpManager onto rabbitmq.
+  - Elastic Replicator consumes messages from these queues, processes them using the sql queries and updates or inserts new records into elastic search. It also pushes the events onto a queue which is consumed by idms-proxy.
+  - idms-proxy consumes a queue which receives event messages from elastic-replicator.
+  - Nova front end is subscribed to proxies sse endpoint /replicator and receives messages for real time page updates.
 {{ :onboarding:elastic-replicator:eventnotificationprocess.drawio.png?600 |}}

Sidebar

Internal Errigal Collaboration Wiki

Differences

Sidebar

Internal Errigal Collaboration Wiki

User Tools

Site Tools

Differences

Page Tools