Internal Errigal Collaboration Wiki

User Tools

Site Tools

Trace:
onboarding:elastic-replicator:start

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
onboarding:elastic-replicator:start [2022/10/04 15:18] – 10.91.110.100onboarding:elastic-replicator:start [2024/08/29 11:28] (current) – 10.91.129.119
Line 46: Line 46:
  
 **Individual:** **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:** **Bulk:**
Line 81: Line 86:
 The SSE touchpoints for  processing are as follows(see also diagram below): 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.   - 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 ort inserts new records into elastic search. It also pushes the events onto a queue which is consumed by idms-proxy. +  - 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.+  - 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.   - Nova front end is subscribed to proxies sse endpoint /replicator and receives messages for real time page updates.
  
onboarding/elastic-replicator/start.1664893087.txt.gz · Last modified: 2022/10/04 15:18 by 10.91.110.100

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki