ems Section
- dc.default.logfilter
- dc.default.metricsfilter
- logconfig.DATAC
- logconfig.MFSINK
- metricsconfig.DATAC
- metricsconfig.MFSINK
- ors.reportinginterval
- rc.amq_connection_send_timeout
- rc.batch_size
- rc.cdr.batch_size
- rc.cdr.local_queue_max
- rc.cdr.local_queue_path
- rc.cdr.max_throughput
- rc.certificate
- rc.local_queue_max
- rc.local_queue_path
- rc.max_throughput
- rc.ors.local_queue_max
- rc.ors.local_queue_path
dc.default.logfilter
Default Value: 0-2|
Valid Values: Pipe delimited ranges for log levels, module IDs and specifier IDs. Ranges can be comma separated integers or range of integers or '*'.
Changes Take Effect: At start/restart
Specifies the filter for logs to be delivered "upstream" to the Reporting Server for Call Events reporting. The format is 'levels|moduleIDs|specifierIDs' (repeated if necessary). The values between the pipes can be in the format: 'm-n,o,p' (ie "0-4, 5,6"). The wildcard character '*' can also be used to indicate all valid numbers. Example: '*|*|*' indicates that all log messages should be sent to the sink. Alternatively, '0,1|0-10|*|4|*|*' inidcates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 wil be sent to the sink; and all INFO(4) level messages will be sent as well.
dc.default.metricsfilter
Default Value: 1001,1009,1012-1013,1031,1050,1052,1058-1059
Valid Values: Comma separated list of metric values or ranges. A metric value must be between 0 and 141 inclusive. The values '*' and blank are also allowed.
Changes Take Effect: At start/restart
Specifies the default filter for metrics to be delivered "upstream" to the Reporting Server for Call Events reporting. '*' indicates that all metrics will be sent to the sink. Alternatively, '5-10,50-55,70,71' indicates that metrics with IDs 5,6,7,8,9,10,50,51,52,53,54,55,70 and 71 will be sent to the MF sink. This filter will be used unless the default has been overridden in the tenant or IVR Application profile to which the given call has been associated.
logconfig.DATAC
Default Value: 0-2|
Valid Values: Pipe delimited ranges for log levels, module IDs and specifier IDs. Ranges can be comma separated integers or range of integers or '*'.
Changes Take Effect: immediately
Controls the log messages that are sent to the MF sink. The format is 'levels|moduleIDs|specifierIDs' (repeated if necessary). The values between the pipes can be in the format: 'm-n,o,p' (ie "0-4, 5,6"). The wildcard character '*' can also be used to indicate all valid numbers. Example: '*|*|*' indicates that all log messages should be sent to the sink. Alternatively, '0,1|0-10|*|4|*|*' inidcates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 wil be sent to the sink; and all INFO(4) level messages will be sent as well.
logconfig.MFSINK
Default Value:
- |
*| *
Valid Values: Pipe delimited ranges for log levels, module IDs and specifier IDs. Ranges can be comma separated integers or range of integers or '*'.
Changes Take Effect: immediately
Controls the log messages that are sent to the MF sink. The format is 'levels|moduleIDs|specifierIDs' (repeated if necessary). The values between the pipes can be in the format: 'm-n,o,p' (ie "0-4, 5,6"). The wildcard character '*' can also be used to indicate all valid numbers. Example: '*|*|*' indicates that all log messages should be sent to the sink. Alternatively, '0,1|0-10|*|4|*|*' inidcates that CRITICAL(0) and ERROR(1) level messages with module IDs in the range 0-10 wil be sent to the sink; and all INFO(4) level messages will be sent as well.
metricsconfig.DATAC
Default Value:
Valid Values: Comma separated list of metric values or ranges. A metric value must be between 0 and 141 inclusive. The values '*' and blank are also allowed.
Changes Take Effect: immediately
Specifies the metrics that are delivered to the Data Collection Sink. '*' indicates that all metrics will be sent to the sink. Alternatively, '5-10,50-55,70,71' indicates that metrics with IDs 5,6,7,8,9,10,50,51,52,53,54,55,70 and 71 will be sent to the MF sink.
metricsconfig.MFSINK
Default Value: 1000-1001,1003-1005,1007-1016,1019-1021,1024,1027-1036,1039-1045,1048-1050,1052-1054,1056,1058-1062
Valid Values: Comma separated list of metric values or ranges. A CCP metric value must be between 1000 and 1063 inclusive. The values '*' and blank are also allowed.
Changes Take Effect: immediately
Specifies the metrics that are delivered to the MF Sink. '*' indicates that all metrics will be sent to the sink. Alternatively, '5-10,50-55,70,71' indicates that metrics with IDs 5,6,7,8,9,10,50,51,52,53,54,55,70 and 71 will be sent to the MF sink.
ors.reportinginterval
Default Value: 60
Valid Values: An integer between 1-299 inclusive.
Changes Take Effect: At start/restart
Interval (seconds) accumulated operational reports are submitted to the Reporting Server
rc.amq_connection_send_timeout
Default Value: 60
Valid Values: An integer greater than or equal to 45.
Changes Take Effect: At start/restart
This option specifies the maximum time in seconds to wait for ActiveMQ Producer Send Message response.
rc.batch_size
Default Value: 500
Valid Values: An integer between 1-5000 inclusive.
Changes Take Effect: At start/restart
The number of upstream messages queued up by the reporting client before sending them up to the reporting server. A higher batch size (e.g. 50 records) will lessen bandwidth constraints, at the cost of making sending data at larger intervals.
rc.cdr.batch_size
Default Value: 500
Valid Values: An integer between 1-5000 inclusive.
Changes Take Effect: At start/restart
The number of CDR messages queued up by the reporting client before sending them up to the reporting server. A higher batch size (e.g. 50 records) will lessen bandwidth constraints, at the cost of making sending CDR data at larger intervals.
rc.cdr.local_queue_max
Default Value: 1000000
Valid Values: An integer greater or equal to -1.
Changes Take Effect: At start/restart
This option specifies the maximum number of data items to the local database for CDR reporting. Queuing to the local database will occur either when the Reporting Server is unavailable, or when data is being provided to the Client faster than the Server can consume it. A value of -1 indicates an "unlimited" number of records will be allowed. A value of 0 indicates that no records will be persisted locally and data will be discarded if the RS is unavailable.
rc.cdr.local_queue_path
Default Value: $InstallationRoot$/config/cdrQueue_ccp.db
Valid Values: Path to the DB file.
Changes Take Effect: At start/restart
The full path of the local database file used to locally persist data for CDRs.
rc.cdr.max_throughput
Default Value: 0
Valid Values: An integer greater or equal to 0.
Changes Take Effect: At start/restart
This option specifies the maximum rate at which CDR data, in bytes per second, is sent to the Reporting Server. A value of 0 (default) indicates that CDR data will be sent as quickly as possible.
rc.certificate
Default Value:
Valid Values: File path
Changes Take Effect: at start/restart
The file name of the TLS certificate in "PEM" format. Required to connect to the Reporting Server (ActiveMQ) over TLS.
rc.local_queue_max
Default Value: 5000000
Valid Values: An integer greater or equal to -1.
Changes Take Effect: At start/restart
This option specifies the maximum number of data items to the local database for Upstream Logging. Queuing to the local database will occur either when the Reporting Server is unavailable, or when data is being provided to the Client faster than the Server can consume it. A value of -1 indicates an "unlimited" number of records will be allowed. A value of 0 indicates that no records will be persisted locally and data will be discarded if the RS is unavailable.
rc.local_queue_path
Default Value: $InstallationRoot$/config/upstreamQueue_CCP.db
Valid Values: Path to the DB file.
Changes Take Effect: At start/restart
The full path of the local database file used to locally persist data for upstream logging to the GVP Reporting Client.
rc.max_throughput
Default Value: 0
Valid Values: An integer greater or equal to 0.
Changes Take Effect: At start/restart
This option specifies the maximum rate at which Upstream Logging data, in bytes per second, is sent to the Reporting Server. A value of 0 (default) indicates that Upstream Logging data will be sent as quickly as possible.
rc.ors.local_queue_max
Default Value: 1000000
Valid Values: An integer greater or equal to -1.
Changes Take Effect: At start/restart
This option specifies the maximum number of data items to the local database for Operational Reporting. Queuing to the local database will occur either when the Reporting Server is unavailable, or when data is being provided to the Client fdaster than the Server can consume it. A value of -1 indicates an "unlimited" number of records will be allowed. A value of 0 indicates that no records will be persisted locally and data will be discarded if the RS is unavailable.
rc.ors.local_queue_path
Default Value: $InstallationRoot$/config/orsQueue_ccp.db
Valid Values: Path to the DB file.
Changes Take Effect: At start/restart
The full path of the local database file used to locally persist data for Operational Reporting.