Difference between revisions of "Draft: PE-GPR/9.0.0/Deployment/ASCops"

From Genesys Documentation
Jump to: navigation, search
Line 123: Line 123:
 
{{!}}'''Text'''
 
{{!}}'''Text'''
 
{{!}} VALIDATE_DL_OPTIONS{{!}}validateDLOptions. The following Agent Groups are not found in Configuration Server. Please verify the correct names for these Agent Groups: <''agent_group_names''> in Data Loader option: <''option_name''>
 
{{!}} VALIDATE_DL_OPTIONS{{!}}validateDLOptions. The following Agent Groups are not found in Configuration Server. Please verify the correct names for these Agent Groups: <''agent_group_names''> in Data Loader option: <''option_name''>
or
+
or<br />
 
There are no agents present in Configuration Server with the following skills. Please verify the correct names for these skills: &lt;''skill_names''&gt; in Data Loader option: &lt;''option_name''&gt;
 
There are no agents present in Configuration Server with the following skills. Please verify the correct names for these skills: &lt;''skill_names''&gt; in Data Loader option: &lt;''option_name''&gt;
 
{{!}}-  
 
{{!}}-  
Line 150: Line 150:
 
{{!}}-  
 
{{!}}-  
 
{{!}}'''Text'''
 
{{!}}'''Text'''
{{!}} DATASET_UPLOAD_FAILURE{{!}}Datasets upload errors:%s
+
{{!}} DATASET_UPLOAD_FAILURE{{!}}Datasets upload errors: &lt;''error_code''&gt;
 
{{!}}-  
 
{{!}}-  
 
{{!}}'''Attributes'''
 
{{!}}'''Attributes'''
{{!}}[''%s'']&mdash;
+
{{!}}&lt;''error_code''&gt; - The code indicating the type of error.
 
{{!}}-  
 
{{!}}-  
 
{{!}}'''Description'''
 
{{!}}'''Description'''
{{!}}In case if DL failed to upload a dataset and raised alarm 107-60606 - Dataset upload errors:... and indicated an error on platform side (f.e 502, 503 error) - our team proposed next workaround:
+
{{!}}502, 503 - These error codes indicate a problem with the GPR Core Platform rather than with Data Loader.  
it is possible to rerun the dataset manually. For that turn off the particular dataset in data loader cfg configuration (set option "upload-dataset" to false) and turn it on again in 1 minute.
+
'''QUESTION''' - What other error codes might appear?
 
 
Or just wait for the next scheduled upload of the dataset data, it will be in time interval described in option "update-period" in cfg configuration. By default, it sets to 1 day.
 
 
{{!}}-  
 
{{!}}-  
 
{{!}}'''Alarm Advisory'''
 
{{!}}'''Alarm Advisory'''
Line 165: Line 163:
 
{{!}}-  
 
{{!}}-  
 
{{!}}'''Actions'''
 
{{!}}'''Actions'''
{{!}}''action''
+
{{!}}If a GPR Core Platform error caused the issue, rerun the data upload manually by setting the {{Optionslink|link=Options:DataLoader:dataset-zname-:upload-dataset}} option to <tt>false</tt>, waiting for one minute, then setting the option value back to <tt>true</tt>. Alternatively, you can wait for the next scheduled upload of the data, as configured in the {{Optionslink|link=Options:DataLoader:dataset-zname-:update-period}} option.
 +
<nowiki>{!}}}</nowiki>
 
{{!}}}
 
{{!}}}
 
|Status=No
 
|Status=No

Revision as of 20:38, January 15, 2020

This is a draft page; the published version of this page can be found at PE-GPR/9.0.0/Deployment/ASCops.

You can monitor Data Loader status using the log events that Message Server sends to Solution Control Interface.

Data Loader Log Events

Data Loader writes log data to Message Server using Genesys Management Framework centralized logging. The details of where logs are kept and what messages are sent are configured using the Data Loader log Section configuration options.

Data Loader provides the following Standard- and Trace-level log events:

107-60119 107-60120 107-60400 107-60401 107-60606 107-60607 107-60608
107-60609 107-60610 107-60620 107-60702 107-60706 107-60707  

107-60119

107-60120

107-60400

107-60401

107-60606

107-60607

107-60608

107-60609

107-60610

107-60620

107-60702

107-60706

107-60707