Excessive Syslog Errors Related to ClothoClientManager: RESTAnalyticsPublisher Failed to Publish Due to Unavailable ClientsIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } During the analysis of the syslog Table growth, a significant volume of log entries was identified for the following error: [RESTAnalyticsPublisher] failed to publish: Unavailable Clients: com.snc.clotho.config.ClothoClientManager.getClient(ClothoClientManager.java:326) These messages were being generated continuously at a high frequency, resulting in excessive growth of the syslog table and contributing to increased database storage consumption. Symptoms<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } 1. High volume of entries related to the following error:[RESTAnalyticsPublisher] failed to publish: Unavailable Clients: com.snc.clotho.config.ClothoClientManager.getClient(ClothoClientManager.java:326) +------+--------------------------------------------------------------------------------------------+----------------------+----------+ | Port | trimMessage | trimSource | ttlCount | +------+--------------------------------------------------------------------------------------------+----------------------+----------+ | 3310 | [RESTAnalyticsPublisher] failed to publish: Unavailable Clients: : com.snc.clotho.config. | com | 982,598 | +------+--------------------------------------------------------------------------------------------+----------------------+----------+ 2. Source for [RESTAnalyticsPublisher] failed to publish: Unavailable Clients +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ | | source_application_family | | | level | 2 | | source_package | | | source | com.glide.ui.ServletErrorListener | | message | [RESTAnalyticsPublisher] failed to publish: Unavailable Clients: : com.snc.clotho.config.ClothoClientManager.getClient(ClothoClientManager.java:326) | | | com.snc.clotho.config.ClothoClientManager.getClient(ClothoClientManager.java:215) | | | com.glide.api.analytics.metricbase.MetricBaseRepository.save(MetricBaseRepository.java:24) | | | com.glide.api.analytics.metricbase.rest.RESTAnalyticsPublisher.publish(RESTAnalyticsPublisher.java:33) | | | com.glide.api.analytics.metricbase.rest.RESTAnalyticsPublisher.publish(RESTAnalyticsPublisher.java:14) | | | com.glide.rest.analytics.metricbase.AnalyticsBucketCollector.lambda$publish$1(AnalyticsBucketCollector.java:48) | | | java.base/java.util.Optional.ifPresent(Optional.java:178) | | | com.glide.rest.analytics.metricbase.AnalyticsBucketCollector.lambda$publish$2(AnalyticsBucketCollector.java:47) | | | java.base/java.util.Iterator.forEachRemaining(Iterator.java:133) | | | com.glide.rest.analytics.metricbase.AnalyticsBucketCollector.publish(AnalyticsBucketCollector.java:45) | | | com.glide.api.analytics.metricbase.AnalyticsSweeperJob.run(AnalyticsSweeperJob.java:27) | | | com.glide.db.pool.DBPoolSweeperJobStatus.run(DBPoolSweeperJobStatus.java:36) | | | com.glide.db.pool.DBConnectionPoolSweeper$JobRunner.run(DBConnectionPoolSweeper.java:61) | | | java.base/java.lang.Thread.run(Thread.java:841) | | sys_class_name | syslog | | +---------------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------+ 3. Sample Transaction Logs: 2026-07-13 03:57:09 (198) AnalyticsSweeperJob@47b4bf5f SYSTEM txid=4400d035934e RESTAnalyticsPublisher *** ERROR *** [RESTAnalyticsPublisher] failed to publish Unavailable Clients: at com.snc.clotho.config.ClothoClientManager.getClient(ClothoClientManager.java:326) at com.snc.clotho.config.ClothoClientManager.getClient(ClothoClientManager.java:215) at com.glide.api.analytics.metricbase.MetricBaseRepository.save(MetricBaseRepository.java:24) at com.glide.api.analytics.metricbase.rest.RESTAnalyticsPublisher.publish(RESTAnalyticsPublisher.java:33) at com.glide.api.analytics.metricbase.rest.RESTAnalyticsPublisher.publish(RESTAnalyticsPublisher.java:14) at com.glide.rest.analytics.metricbase.AnalyticsBucketCollector.lambda$publish$1(AnalyticsBucketCollector.java:48) at java.base/java.util.Optional.ifPresent(Optional.java:178) at com.glide.rest.analytics.metricbase.AnalyticsBucketCollector.lambda$publish$2(AnalyticsBucketCollector.java:47) at java.base/java.util.Iterator.forEachRemaining(Iterator.java:133) at com.glide.rest.analytics.metricbase.AnalyticsBucketCollector.publish(AnalyticsBucketCollector.java:45) at com.glide.api.analytics.metricbase.AnalyticsSweeperJob.run(AnalyticsSweeperJob.java:27) at com.glide.db.pool.DBPoolSweeperJobStatus.run(DBPoolSweeperJobStatus.java:36) at com.glide.db.pool.DBConnectionPoolSweeper$JobRunner.run(DBConnectionPoolSweeper.java:61) at java.base/java.lang.Thread.run(Thread.java:841) Facts<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } About Clotho Clotho is an internal ServiceNow platform service used to support analytics and telemetry-related data collection and publishing. Platform components that rely on Clotho attempt to communicate with Clotho clients to publish analytics events and operational metrics. When the Clotho service is not properly provisioned or cannot be reached, these publishing attempts fail and generate error messages within the application logs and the syslog table. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } N/A Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Investigation determined that the Clotho service was not provisioned correctly for the instance, causing requests from the RESTAnalyticsPublisher component to fail when attempting to obtain a valid Clotho client. Further backend analysis identified a connectivity issue involving the TCP communication path required for the Clotho service. As a result, the platform was unable to establish communication with the Clotho backend, leading to repeated error messages. Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } span { font-size: 12pt; font-family: Lato; color: var(--now-color--text-primary, #000000); } h2 { font-size: 24pt; font-family: Lato; color: var(--now-color--text-primary, black); } h3 { font-size: 18pt; font-family: Lato; color: var(--now-color--text-primary, black); } h4 { font-size: 14pt; font-family: Lato; color: var(--now-color--text-primary, black); } a { font-size: 12pt; font-family: Lato; color: var(--now-color--link-primary, #00718F); } a:hover { font-size: 12pt; color: var(--now-color--link-primary, #024F69); } a:target { font-size: 12pt; color: var(--now-color--link-primary, #032D42); } a:visited { font-size: 12pt; color: var(--now-color--link-primary, #00718f); } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The ServiceNow Clotho Engineering team was engaged to investigate the provisioning and connectivity issue. The team successfully identified and resolved the underlying provisioning problem within the ServiceNow backend infrastructure. Following the fix, communication with the Clotho service was successfully restored, and the affected publisher processes were able to obtain valid Clotho clients. As a result, the repeated Clotho-related error messages should no longer be generated. If you continue to observe a high volume of syslog entries containing the following error: [RESTAnalyticsPublisher] failed to publish: Unavailable Clients If you need immediate assistance, please use one of the contact numbers from our support contact page:[code]<a href='http://www.servicenow.com/support/contact-support.html'>http://www.servicenow.com/support/contact-support.html</a>[/code] You will then be able to enter your Case or Change number over the phone to have your call routed to the Support Team. Our team will review the new occurrence and determine whether there are any underlying provisioning, connectivity, or platform-related issues contributing to the behaviour.Please raise a new ServiceNow Support case so the issue can be investigated further and any underlying causes can be properly addressed.