Data Loader monitoring and logging

From Genesys Documentation
Revision as of 18:04, March 6, 2020 by Vivian (talk | contribs) (Published)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

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

Related documentation:

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

Level Standard
Text <data_loader_name> terminated, <reason>
Attributes <data_loader_name> - The name of the Data Loader Application and other relevant information.

<reason> - An explanation for the termination.

Description Data Loader has quit unexpectedly on account of a critical configuration issue. The <reason> information should direct you to the source of the problem.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message.
Actions Review the reason for the termination and correct the issue before trying to upload data.

107-60120

Level Standard
Text Failed to connect to authenticate <endpoint>, response: <message>
Attributes <endpoint> - The endpoint for the GPR Core Platform authentication service.

<response> - An informational message indicating the reason the authentication attempt failed.

Description Data Loader authentication to the GPR Core Platform has failed.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message.
Actions Verify that you have correctly configured the URL for Data Loader to connect to the Platform and that the Data Loader account is correctly configured with a valid password.

107-60400

Level Standard
Text error... <error_message>
Attributes <error_message> - An informational message.
Description Data Loader was unable to push an Agent Profile batch update. If you receive this error message, Data Loader continues to operate normally.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message.
Actions action

107-60401

Level Standard
Text The log event text is one of the following:
  • 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>
  • There are no agents present in Configuration Server with the following skills. Please verify the correct names for these skills: <skill_names> in Data Loader option: <option_name>
Attributes <agent_group_names> or <skill_names> - The name of the Agent Group or skill you entered.

<option_name> - The option where you entered the Agent Group or skill name.

Description This log number has two possible messages indicating that a value for the include-skills or include-groups configuration option does not correspond to a configured skill or Agent Group. This log event is informational and does not indicate any issue with Data Loader.
Alarm Advisory advisory
Actions Verify the names of the Agent Groups or skills and make corrections as necessary.

107-60606

Level Standard
Text DATASET_UPLOAD_FAILURE: Datasets upload errors: <error_code>
Attributes <error_code> - An error message or list of error messages indicating an issue with dataset processing.
Description This log event could provide any of a number of issues related to dataset processing: configuration issues, Data Loader issues, and GPR Core Platform issues. The error message indicates the nature of the problem.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message. The cancel event for this condition is 107-60607.
Actions If a GPR Core Platform error caused the issue, rerun the data upload manually by setting the upload-dataset option to false, waiting for one minute, then setting the option value back to true. Alternatively, you can wait for the next scheduled upload of the data, as configured in the update-period option.

107-60607

Level Standard
Text Datasets upload errors resolved!
Attributes none
Description An informational message generated when a data upload is successful after an unsuccessful attempt. Confirms that whatever issue caused the previous upload failure has been resolved.
Alarm Advisory This is the cancel event for 107-60606.
Actions No action required

107-60608

Level Standard
Text Platform service account password is about to expire in <number_of_days> days.
Attributes <number_of_days> - The number of days the current password remains valid.
Description An informational message.
Alarm Advisory No alarm required.
Actions Change your password within the specified period.

107-60609

Level Standard
Text Platform service account password updated successfully
Attributes none
Description An informational message indicating that the password for the Data Loader SERVICE account was successfully updated.
Alarm Advisory None recommended
Actions No action required

107-60610

Level Standard
Text Platform service account password update failed.
Attributes None
Description A notification that the password for the Data Loader SERVICE account was not correctly updated.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message.
Actions action

107-60620

Level Standard
Text <agent/customer_profile_name> profile schema doesn't match the schema defined in your schema configuration; <problem_description>
Attributes <agent/customer_profile_name> - The name of the Agent Profile dataset or Customer Profile dataset that has inconsistencies.

<problem_description> - Explains what the inconsistencies are.

Description The data you are uploading to the Agent Profile dataset or Customer Profile dataset does not correspond with the configuration specified for that dataset in the Data Loader Application object options.
Alarm Advisory advisory
Actions Make the Profile schema consistent with the configuration specified on the Options tab of the Data Loader Application object.

107-60702

Level Standard
Text CONFSERV_REPEATABLE_SWITCHOVER_EVENTS: <error_message>
Attributes <error_message> - A message explaining the nature of the issue with Configuration Server.
Description Configuration Server has experienced multiple switchovers between the primary and backup instances during the period specified in the confserv-monitoring-reconnect-min option.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message.
Actions Check whether Configuration Server is experiencing some issue causing the repeated switchovers.

107-60706

Level Standard
Text CONFSERV_DISCONNECTING_EVENT: <error_message>
Attributes <error_message> - A message explaining the nature of the issue with Configuration Server.
Description Configuration Server is losing connection with Data Loader. The number of times the connection is lost before this alarm is triggered is set in the confserv-monitoring-reconnect-count option.
Alarm Advisory Genesys recommends that you configure an alarm to notify you when Data Loader generates this error message. The cancel event for this error condition is 107-60707.
Actions Check Configuration Server to determine the reason for this issue.

107-60707

Level Standard
Text CONFSERV_CONNECTING_EVENT: <informational_message>
Attributes <informational_message> - A message updating the Configuration Server status.
Description The Configuration Server connection with Data Loader has been restored.
Alarm Advisory This is the cancel event for 107-60706.
Actions No action required.
Retrieved from "https://all.docs.genesys.com/PE-GPR/9.0.0/Deployment/ASCops (2025-06-21 18:02:20)"
Comments or questions about this documentation? Contact us for support!