Difference between revisions of "Draft: PEC-REP/Current/RAAPEGuide/Planning"

From Genesys Documentation
Jump to: navigation, search
m (undefined (Saved using "Save and continue" button in form))
m (undefined (Saved using "Save and continue" button in form) (Saved using "Save and continue" button in form))
Line 361: Line 361:
 
     ...</source>
 
     ...</source>
 
An ephemeral storage could be also mapped.  
 
An ephemeral storage could be also mapped.  
|NetworkText=RAA interacts with GIM database only. Additionally it can expose prometheus metrics via netcat.  
+
|NetworkText=RAA interacts only with the Genesys Info Mart database.
  
Aggregation pod has own IP address. The pod can run up to two running containers as described above.  
+
RAA can expose Prometheus metrics by way of Netcat.  
  
Additional IP address is needed for running test pods one by one (via helm test). Each test pod runs one container.
+
The aggregation pod has it's own IP address, and can run wither one or two running containers. For Helm test, additional IP address are required -- each test pod runs one container.  
  
It is recommended to have RAA located in the same region with GIM database since RAA works mostly with this database.
+
Genesys recommends that RAA be located in the same region as the Genesys Info Mart database.
 
|BrowserText=Not applicable.
 
|BrowserText=Not applicable.
 
|DependenciesText=RAA interacts with Genesys Info Mart database only.
 
|DependenciesText=RAA interacts with Genesys Info Mart database only.

Revision as of 17:52, June 16, 2021

This is a draft page; it has not yet been published.


Find out what to do before deploying Reporting and Analytics Aggregates (RAA).

Related documentation: