By type
2022/03/11 03:18:44.751741 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/03/11 03:18:44.751839 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/11 03:18:44.751962 logstash.go:90: INFO Max Retries set to: 3
2022/03/11 03:18:44.752086 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/11 03:18:44.752695 metrics.go:23: INFO Metrics logging every 30s
2022/03/11 03:18:44.753805 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-wxzj6
2022/03/11 03:18:44.760693 async.go:63: INFO Flush Interval set to: 1s
2022/03/11 03:18:44.760745 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/11 03:18:44.762041 beat.go:221: INFO filebeat start running.
2022/03/11 03:18:44.762158 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/11 03:18:44.770744 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/11 03:18:44.770956 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/11 03:18:44.771027 crawler.go:38: INFO Loading Prospectors: 1
2022/03/11 03:18:44.771555 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/11 03:18:44.772062 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/11 03:18:44.772117 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/11 03:18:44.772144 registrar.go:236: INFO Starting Registrar
2022/03/11 03:18:44.772571 sync.go:41: INFO Start sending events to output
2022/03/11 03:18:44.772642 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/11 03:18:44.774169 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/11 03:19:14.753303 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/11 03:19:44.754206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:14.753316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:20:44.759704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:14.753203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:21:44.758173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:14.753424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:22:44.754506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:14.753220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:44.753193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:23:49.796214 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:24:14.753194 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/11 03:24:44.754379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:14.753150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:25:44.753124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:14.753136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:26:44.753163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:14.753264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:27:44.753490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:14.753776 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:28:44.755476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:14.753245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:29:44.753250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:14.753137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:30:44.753400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:14.753140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:31:44.753110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:14.753079 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:32:44.753269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:14.753134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:33:44.755961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:14.753223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:34:44.753443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:14.753157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:35:44.753462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:14.754097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:36:44.754394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:14.753084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:37:44.753276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:14.753302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:38:44.753460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:14.753173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:39:44.753135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:14.753584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:40:44.753336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:14.753203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:41:44.753275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:14.753170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:42:44.753068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:14.753112 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:43:44.753040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:14.753132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:44:44.753170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:14.753107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:45:44.753467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:14.753429 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:46:44.753145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:14.755882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:44.753235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:47:55.074431 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/11 03:48:00.060551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:00.060585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:01.064426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:01.064470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:03.068511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:03.068549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:07.080118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:07.080229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:14.755039 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/11 03:48:15.183480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:15.183543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:31.209261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:31.209353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:48:44.753245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:03.248722 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:03.248776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:49:14.753096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:49:44.753514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:03.265400 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:03.265458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:50:14.753357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:50:44.753346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:03.279130 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:03.279173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:51:14.753279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:51:44.753040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:03.296110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:03.296445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:52:14.764069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:52:44.753118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:53:00.098432 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/11 03:53:03.307307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:03.307362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:53:14.754238 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/03/11 03:53:44.753279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:03.331405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:03.331442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:54:14.755000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:54:44.753366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:03.359003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:03.359118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:55:14.753986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:55:44.753321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:03.373380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:03.373431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:56:14.753195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:56:44.753173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:03.395306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:03.395362 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:57:14.753090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:57:44.753156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:03.404834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:03.404881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:58:14.754455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:58:44.753164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:03.430657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:03.430709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 03:59:14.753135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 03:59:44.753453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:03.440985 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:03.441031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:00:14.753245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:00:44.753467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:03.453067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:03.453167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:01:14.754533 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:01:44.753173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:03.476391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:03.476438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:02:14.753336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:02:44.755166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:03.493111 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:03.493157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:03:14.753215 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:03:44.753169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:03.504683 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:03.504786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:04:14.753393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:04:44.753509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:03.522766 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:03.522907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:05:14.753114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:05:44.753105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:03.532171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:03.532211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:06:14.753794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:06:44.753455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:03.546371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:03.546422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:07:14.753088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:07:44.755162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:03.565649 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:03.565711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:08:14.757331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:08:44.753269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:03.573563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:03.573627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:09:14.753154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:09:44.753281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:03.595146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:03.595210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:10:14.753174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:10:44.760528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:03.604776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:03.604828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:11:14.753390 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:11:44.753476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:03.636657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:03.636720 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:12:14.753105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:12:44.753296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:03.644751 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:03.644956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:13:14.753154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:13:44.753638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:03.656794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:03.656844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:14:14.753375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:14:44.753358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:03.665797 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:03.665858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:15:14.753077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:15:44.753539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:03.684967 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:03.685019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:16:14.753147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:16:44.753299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:03.732345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:03.735382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:17:14.753232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:17:44.753235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:03.751871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:03.751908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:18:14.753268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:18:44.764703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:03.762524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:03.762579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:19:14.753205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:19:44.753680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:03.772318 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:03.772367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:20:14.753362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:20:44.762465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:03.785080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:03.785328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:21:14.753164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:21:44.753196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:03.828526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:03.828586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:22:14.753265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:22:44.754418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:03.837979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:03.838066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:23:14.753267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:23:44.754881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:03.868821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:03.868881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:24:14.755181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:24:44.753121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:03.895240 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:03.895383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:25:14.753155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:25:44.753209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:03.906118 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:03.906278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:26:14.753125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:26:44.756265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:03.927221 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:03.927324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:27:14.753070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:27:44.760433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:03.948821 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:03.948901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:28:14.753230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:28:44.753110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:03.962225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:03.962279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:29:14.753438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:29:44.753311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:03.989168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:03.989247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:30:14.753104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:30:44.754660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:04.000795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:04.000860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:31:14.753211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:31:44.753158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:04.019008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:04.019061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:32:14.753280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:32:44.753087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/11 04:33:04.040802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:33:04.040857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/11 04:33:14.753184 metrics.go:34: INFO No non-zero metrics in the last 30s