Results

          2022/03/05 03:29:12.368742 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/05 03:29:12.368791 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:29:12.368875 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:29:12.368926 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:29:12.368960 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:29:12.369071 publish.go:295: INFO Publisher name: onap-vfc-vnfmgr-8594ffd488-42vc2
2022/03/05 03:29:12.369303 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:29:12.369332 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:29:12.369909 beat.go:221: INFO filebeat start running.
2022/03/05 03:29:12.370002 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:29:12.372957 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:29:12.373006 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:29:12.373036 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:29:12.373220 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:29:12.373323 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:29:12.373345 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:29:12.373355 registrar.go:236: INFO Starting Registrar
2022/03/05 03:29:12.373383 sync.go:41: INFO Start sending events to output
2022/03/05 03:29:12.373417 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:29:12.374010 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/05 03:29:42.369384 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/05 03:30:12.369651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:42.369326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:12.369334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:42.369480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:12.369451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:42.369311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:12.369288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:42.369303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:12.369399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:17.386602 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:34:42.369651 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/05 03:35:12.369327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:42.369269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:12.369236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:42.369407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:12.369251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:42.369290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:12.369209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:42.369268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:12.369341 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:42.369393 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:12.369267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:42.369261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:12.369280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:42.369282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:12.369280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:42.369225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:12.369265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:42.369424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:12.369273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:42.369263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:12.369493 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:42.369239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:12.369275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:42.369451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:12.369249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:42.369241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:12.369406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:42.369300 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:12.369292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:42.369303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:12.369285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:42.369296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:12.369318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:42.369242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:12.369211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:42.369660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:12.369415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:42.369323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:12.369457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:42.369250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:12.369343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:42.369220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:12.369211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:42.369262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:12.369490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:42.369266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:12.369478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:32.555799 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log
2022/03/05 03:58:32.604293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:32.604334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:33.608480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:33.608564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:35.613179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:35.613225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:39.616710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:39.616748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:42.369351 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/05 03:58:47.625373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:47.625460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:03.643227 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:03.643305 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:12.369389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:35.665947 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:35.665998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:42.369269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:12.369196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:35.686119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:35.686158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:42.369229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:12.375221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:35.713542 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:35.713604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:42.369245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:12.369430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:35.738906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:35.738949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:42.369365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:12.369389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:35.762409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:35.762464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:37.569453 log.go:116: INFO File is inactive: /var/log/onap/vfc/gvnfm-vnfmgr/runtime_mgr.log. Closing because close_inactive of 5m0s reached.
2022/03/05 04:03:42.369275 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/05 04:04:12.369251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:35.780250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:35.780292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:42.369234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:12.369262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:35.797892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:35.797949 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:42.369251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:12.369219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:35.819961 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:35.820012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:42.369246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:12.369464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:35.838544 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:35.838583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:42.369305 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:12.369280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:35.857585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:35.857623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:42.369230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:12.369218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:35.880159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:35.880214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:42.369299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:12.369268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:35.898658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:35.898694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:42.369206 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:12.369261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:35.916475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:35.916514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:42.369387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:12.369357 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:35.935087 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:35.935195 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:42.369255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:12.369427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:35.955613 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:35.955705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:42.369281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:12.369266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:35.975605 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:35.975650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:42.369692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:12.369266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:36.001378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:36.001506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:42.369336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:12.369451 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:36.021792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:36.021845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:42.369260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:12.369285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:36.040331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:36.040387 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:42.369277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:12.369340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:36.061230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:36.061337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:42.369271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:12.369225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:36.099488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:36.099533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:42.369491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:12.369299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:36.118874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:36.118915 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:42.369322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:12.369292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:36.136194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:36.136278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:42.369246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:12.369311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:36.163210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:36.163525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:42.369323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:12.369260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:36.181789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:36.181832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:42.369280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:12.369325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:36.198339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:36.198382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:42.369354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:12.369301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:36.217229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:36.217269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:42.369247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:12.369269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:36.236454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:36.236495 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:42.369321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:12.369381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:36.256794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:36.256839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:42.369276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:12.369310 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:36.291719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:36.291776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:42.369485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:12.369395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:36.309937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:36.309976 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:42.369218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:12.369236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:36.329707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:36.329750 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:42.369316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:12.369323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:36.359673 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:36.359711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:42.369292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:12.369280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:36.382412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:36.382453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:42.369241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:12.369260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:36.402411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:36.402448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:42.369245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:12.369235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:36.423349 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:36.423401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:42.369301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:12.369252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:36.442350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:36.442843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:42.369232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:12.369375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:36.471042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:36.471100 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:42.369340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:12.369368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:36.495208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:36.495251 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:42.369336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:12.369246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:36.516964 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:36.517022 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:42.369265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:12.369267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:36.535385 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:36.535429 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:42.369438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:12.369609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:36.561887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:36.561943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:42.369356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:12.369298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:36.581237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:36.581278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:42.369352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:12.369405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:36.605315 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:36.605353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:42.369281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:12.369316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:36.636454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:36.636497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:42.369285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:12.369269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:36.657863 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:36.658115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:42.369281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:12.369736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:36.678483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:36.678662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:42.369319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:12.369236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:36.696639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:36.696683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:42.369326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:12.369496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:36.721090 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:36.721169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:42.369266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:12.369256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:36.741825 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:36.741880 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:42.369201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:12.369255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:36.763512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:36.763553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:42.369227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:12.369210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:36.782520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:36.782564 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:42.369295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:12.369352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:36.803220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:36.803262 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:42.369728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:12.369251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:36.829079 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:36.829182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:42.369227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:12.369259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:36.851965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:36.852052 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:42.369344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:12.369286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:36.877092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:36.877165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:42.369268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:55:12.369318 metrics.go:34: INFO No non-zero metrics in the last 30s