-
Bug
-
Resolution: Done
-
Major
-
None
When the client is not ready to send (eg. when there's no machine ID file) we should get a debug message with with the insights configuration explaining that.
Instead we get
DEBUG [org.jboss.eap.insights.report] (ServerService Thread Pool -- 1) Scheduled send failed: com.redhat.insights.InsightsException: I4ASR0018: The identification name has not been defined at com.redhat.insights.config.EnvAndSysPropsInsightsConfiguration.getIdentificationName(EnvAndSysPropsInsightsConfiguration.java:53) at org.jboss.eap.insights.report.JBossInsightsConfiguration.toString(JBossInsightsConfiguration.java:53) at java.lang.String.valueOf(String.java:2994) at java.lang.StringBuilder.append(StringBuilder.java:131) at com.redhat.insights.InsightsReportController.lambda$generate$0(InsightsReportController.java:123) at org.jboss.eap.insights.report.JBossInsightsScheduler.lambda$scheduleAtFixedRate$0(JBossInsightsScheduler.java:59) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) at org.jboss.threads.JBossThread.run(JBossThread.java:513)
This is because we never actually set the identificationName in the configuration in the integration code, only in the top level report. So trying to log the config will fail