Data Structure
This section covers information needed to understand Syntphony CAI's data structure and how to extract useful data. Data is split between distinct schemas: 2 in admin and 1 in environment.
Last updated
Was this helpful?
This section covers information needed to understand Syntphony CAI's data structure and how to extract useful data. Data is split between distinct schemas: 2 in admin and 1 in environment.
Last updated
Was this helpful?
Important:
The datebase access has to be given by your Syntphony CAI's deploy administrator.
How to start MySQL 5.7:
Important:
The database access can be concurrent with the virtual agent use. Check with the system administrator the best time to extract data.
Syntphony CAI's 4.0.0 data structure now features data granularization on a deeper level than our previous iterations. Our admin databases contain configurations and setup, while the environment database stores the virtual agent's configurations and usage data.
The Admin database is responsible for:
Admin schema: All user-related structures, bot indexing, information regarding organizations and environments, and file management.
Configurations schema: All config-server and environment data setup.
Keycloak schema: Used by keycloak, it contain it's default Structure.
Honeypot Schema: An empty mirror of the instance's schema data structure.
The Environment database is responsible for:
Environment schemas: The full information from all content registered under that given environment.
Different kinds of reports can be created from the information available in Syntphony CAI’s database, such as information on usage, volume, evolution in accesses and customer satisfaction.
All conversation and usage data are found in your environment database. If you desire to collect data from distinct environments, you will require multiple queries.
In order to extract data usage information from Syntphony CAI, three main tables must be understood:
They, along with all of Syntphony CAI's environment data may be found in the page.