Results

          2022/04/22 03:22:14.890221 beat.go:285: INFO Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2022/04/22 03:22:14.890309 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/22 03:22:14.890438 logstash.go:90: INFO Max Retries set to: 3
2022/04/22 03:22:14.890572 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/22 03:22:14.890705 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-hkj5c
2022/04/22 03:22:14.890924 async.go:63: INFO Flush Interval set to: 1s
2022/04/22 03:22:14.890948 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/22 03:22:14.891782 metrics.go:23: INFO Metrics logging every 30s
2022/04/22 03:22:14.891965 beat.go:221: INFO filebeat start running.
2022/04/22 03:22:14.892036 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/22 03:22:14.900152 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/22 03:22:14.900219 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/22 03:22:14.900253 crawler.go:38: INFO Loading Prospectors: 1
2022/04/22 03:22:14.900433 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/22 03:22:14.900525 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/22 03:22:14.900539 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/22 03:22:14.900549 registrar.go:236: INFO Starting Registrar
2022/04/22 03:22:14.900598 sync.go:41: INFO Start sending events to output
2022/04/22 03:22:14.900629 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/22 03:22:24.902645 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/22 03:22:24.902771 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/22 03:22:24.903053 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/22 03:22:24.903291 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/22 03:22:24.903390 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/22 03:22:29.938258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:29.938303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:30.945010 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:30.945047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:32.956052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:32.958099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:36.968435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:36.968505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:44.892380 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=59 registrar.writes=1
2022/04/22 03:22:44.979983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:22:44.980118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:00.997256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:00.997337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:23:33.018504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:33.018546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:23:44.892524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:24:14.892204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:24:33.038872 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:24:33.038916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:24:44.892359 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:25:14.892526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:25:33.060099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:25:33.060145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:25:44.892629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:26:14.892640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:26:33.086331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:26:33.086405 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:26:44.892464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:27:14.892511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:27:29.919683 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:33.106254 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:27:33.106463 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:27:36.918195 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:36.918195 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:36.918194 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:27:44.892618 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/04/22 03:27:47.934042 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/22 03:28:14.892474 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/04/22 03:28:33.124688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:28:33.124750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:28:44.892083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:29:14.892094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:29:33.152541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:29:33.152593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:29:44.892063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:30:14.892296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:30:33.172886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:30:33.172940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:30:44.892125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:31:14.892002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:31:33.191738 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:31:33.191783 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:31:44.892042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:32:14.892081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:32:33.212261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:32:33.212421 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:32:44.892186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:33:14.892076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:33:33.230961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:33:33.231133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:33:44.892133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:34:14.892136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:34:33.251520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:34:33.251559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:34:44.892427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:35:14.892124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:35:33.271999 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:35:33.272066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:35:44.892205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:36:14.892098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:36:33.292074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:36:33.292111 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:36:44.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:37:14.892179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:37:33.321640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:37:33.321687 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:37:44.892046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:38:14.892041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:38:33.341915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:38:33.341955 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:38:44.892141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:39:14.892102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:39:33.373590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:39:33.373629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:39:44.892274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:40:14.892123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:40:33.390707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:40:33.390750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:40:44.893196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:41:14.892193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:41:33.408891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:41:33.408929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:41:44.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:42:14.892264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:42:33.426758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:42:33.426796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:42:44.892045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:43:14.892108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:43:33.443841 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:43:33.443883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:43:44.892115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:44:14.892141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:44:33.462450 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:44:33.462490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:44:44.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:45:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:45:33.479172 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:45:33.479222 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:45:44.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:46:14.892160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:46:33.502047 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:46:33.502092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:46:44.892108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:47:14.892589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:47:33.524817 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:47:33.524870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:47:44.892158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:48:14.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:48:33.541769 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:48:33.541818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:48:44.892165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:49:14.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:49:33.560435 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:49:33.560599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:49:44.892307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:50:14.892150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:50:33.576407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:50:33.576450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:50:44.892118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:51:14.892104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:51:33.595146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:51:33.595208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:51:44.892191 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:52:14.892220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:52:33.611224 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:52:33.611262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:52:44.892155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:53:14.892122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:53:33.629315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:53:33.629362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:53:44.892061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:54:14.892189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:54:33.648150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:54:33.648206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:54:44.892059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:55:14.892143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:55:33.675971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:55:33.676040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:55:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:56:14.892457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:56:33.693670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:56:33.693709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:56:44.892057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:57:14.892082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:57:33.711950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:57:33.712003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:57:44.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:58:14.892121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:58:33.732653 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:58:33.732702 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:58:44.892078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:59:14.892152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 03:59:33.752449 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:59:33.752487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 03:59:44.892065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:00:14.892125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:00:33.770988 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:00:33.771041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:00:44.892144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:01:14.892213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:01:33.788669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:01:33.788725 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:01:44.892048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:02:14.892099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:02:33.806692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:02:33.806748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:02:44.892156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:03:14.892091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:03:33.833542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:03:33.833594 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:03:44.892290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:04:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:04:33.856154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:04:33.856208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:04:44.892168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:05:14.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:05:33.874767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:05:33.874812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:05:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:06:14.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:06:33.897215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:06:33.897264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:06:44.892055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:07:14.892079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:07:33.918958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:07:33.919007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:07:44.892038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:08:14.892338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:08:33.935239 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:08:33.935276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:08:44.892021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:09:14.892117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:09:33.960346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:09:33.960392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:09:44.892097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:10:14.892112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:10:33.980990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:10:33.981143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:10:44.892181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:11:14.892118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:11:33.998260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:11:33.998303 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:11:44.892087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:12:14.892134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:12:34.016816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:12:34.016871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:12:44.892124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:13:14.892066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:13:36.035164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:13:36.035232 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:13:44.892142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:14:14.892211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:14:36.063745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:14:36.063809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:14:44.892104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:15:14.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:15:36.080181 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:15:36.080234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:15:44.892069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:16:14.892186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:16:36.098836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:16:36.098893 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:16:44.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:17:14.892166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:17:36.116755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:17:36.116798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:17:44.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:18:14.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:18:36.137226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:18:36.137263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:18:44.892105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:19:14.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:19:36.155594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:19:36.155636 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:19:44.892199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:20:14.892071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:20:36.174330 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:20:36.174378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:20:44.892065 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:21:14.892045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:21:36.192704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:21:36.192738 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:21:44.892151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:22:14.892092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:22:36.211857 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:22:36.211898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:22:44.892089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:23:14.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:23:36.229784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:23:36.229962 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:23:44.892137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:24:14.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:24:36.249758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:24:36.249798 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:24:44.892074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:25:14.892294 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:25:36.270124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:25:36.270163 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:25:44.892086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:26:14.892178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:26:36.289625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:26:36.289663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:26:44.892095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:27:14.892085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:27:36.306647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:27:36.306681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:27:44.892050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:28:14.892265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:28:36.323394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:28:36.323591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:28:44.892033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:29:14.892061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:29:36.342854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:29:36.342899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:29:44.892173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:30:14.892109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:30:36.360714 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:30:36.360769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:30:44.892061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:31:14.892096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:31:36.378580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:31:36.378615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:31:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:32:14.892146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:32:36.395309 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:32:36.395345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:32:44.892072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:33:14.892129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:33:36.415670 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:33:36.415709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:33:44.892059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:34:14.892296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:34:36.434304 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:34:36.434338 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:34:44.892121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:35:14.892131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:35:36.455097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:35:36.455138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:35:44.892068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:36:14.892064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:36:36.480859 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:36:36.480900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:36:44.892115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:37:14.892235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:37:36.501391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:37:36.501464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:37:44.892241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:38:14.892067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:38:36.519201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:38:36.519247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:38:44.892109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:39:14.892100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/22 04:39:36.537037 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:39:36.537083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/22 04:39:44.892043 metrics.go:34: INFO No non-zero metrics in the last 30s