Results

          2022/04/05 02:56:13.888881 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/05 02:56:13.888932 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/05 02:56:13.889098 metrics.go:23: INFO Metrics logging every 30s
2022/04/05 02:56:13.889121 logstash.go:90: INFO Max Retries set to: 3
2022/04/05 02:56:13.889264 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/05 02:56:13.889503 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-pwgzx
2022/04/05 02:56:13.889718 async.go:63: INFO Flush Interval set to: 1s
2022/04/05 02:56:13.889736 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/05 02:56:13.890205 beat.go:221: INFO filebeat start running.
2022/04/05 02:56:13.890311 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/05 02:56:13.894924 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/05 02:56:13.895017 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/05 02:56:13.895101 crawler.go:38: INFO Loading Prospectors: 1
2022/04/05 02:56:13.895137 registrar.go:236: INFO Starting Registrar
2022/04/05 02:56:13.895297 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/05 02:56:13.895309 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/05 02:56:13.895266 sync.go:41: INFO Start sending events to output
2022/04/05 02:56:13.895450 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/04/05 02:56:13.895475 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/05 02:56:33.897661 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/04/05 02:56:33.897866 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/04/05 02:56:33.898069 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/04/05 02:56:33.898220 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/04/05 02:56:33.898352 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/04/05 02:56:38.923837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:38.923886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:39.929861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:39.929901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:41.942167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:41.942201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:43.897605 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=64 publish.events=4 registrar.states.current=4 registrar.states.update=4 registrar.writes=2
2022/04/05 02:56:45.949448 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:45.949523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:53.956883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:56:53.956923 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:09.973003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:09.973075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:13.889411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:57:41.990681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:41.990719 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:57:43.889545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:58:13.889545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:58:42.013924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:42.013982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:58:43.889571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:59:13.889573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 02:59:42.032783 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:59:42.032828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 02:59:43.889478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:00:13.889395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:00:42.052903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:00:42.052945 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:00:43.889538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:01:13.889569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:01:38.910409 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:01:38.910399 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:01:38.910423 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:01:38.910768 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:01:42.070784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:01:42.070831 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:01:43.889465 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/05 03:01:46.922804 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/04/05 03:02:13.889450 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/05 03:02:42.093776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:02:42.093823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:02:43.889414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:03:13.889422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:03:42.112981 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:03:42.113079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:03:43.889474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:04:13.889439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:04:42.136076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:04:42.136127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:04:43.889421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:05:13.889438 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:05:42.155811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:05:42.155898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:05:43.889532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:06:13.889487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:06:42.176635 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:06:42.176692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:06:43.889593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:07:13.889515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:07:42.194746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:07:42.194782 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:07:43.889915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:08:13.889421 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:08:42.211942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:08:42.211982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:08:43.889434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:09:13.889411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:09:42.230165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:09:42.230202 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:09:43.889453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:10:13.889609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:10:42.259094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:10:42.259153 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:10:43.889482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:11:13.889475 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:11:42.278326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:11:42.278367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:11:43.889733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:13.889597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:12:42.297691 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:12:42.297736 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:12:43.889574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:13.889514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:13:42.319903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:13:42.319957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:13:43.889415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:13.889443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:14:42.341970 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:14:42.342021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:14:43.889431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:13.889459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:15:42.359950 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:15:42.360001 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:15:43.889456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:13.889439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:16:42.377230 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:16:42.377276 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:16:43.889469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:13.889454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:17:42.393406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:17:42.393462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:17:43.889434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:13.889396 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:18:42.412629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:18:42.412734 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:18:43.889686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:13.889501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:19:42.432460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:19:42.432498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:19:43.889691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:13.889444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:20:42.451288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:20:42.451331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:20:43.889561 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:13.889467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:21:42.470033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:21:42.470075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:21:43.889448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:13.889442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:22:42.488143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:22:42.488187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:22:43.889530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:13.889409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:23:42.505480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:23:42.505517 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:23:43.889417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:13.889437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:24:42.523131 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:24:42.523191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:24:43.889483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:13.889465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:25:42.543373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:25:42.543428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:25:43.889449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:13.889465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:26:42.559891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:26:42.559943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:26:43.889444 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:13.889625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:27:42.577657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:27:42.577705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:27:43.889463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:13.889563 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:28:42.595866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:28:42.595933 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:28:43.889492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:13.900086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:29:42.616458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:29:42.616521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:29:43.889512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:13.889460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:30:42.634154 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:30:42.634193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:30:43.889470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:13.889392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:31:42.651695 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:31:42.651751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:31:43.889669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:13.889437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:32:42.668664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:32:42.668709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:32:43.889425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:13.889399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:33:42.685993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:33:42.686030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:33:43.893583 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:13.889389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:34:42.706561 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:34:42.706625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:34:43.889523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:13.889482 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:35:42.725378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:35:42.725653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:35:43.890337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:13.889524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:36:42.744594 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:36:42.744904 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:36:43.889411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:13.889445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:37:42.763539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:37:42.763595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:37:43.889459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:13.889437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:38:42.784579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:38:42.784622 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:38:43.889476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:13.889515 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:39:42.803124 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:39:42.803175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:39:43.889496 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:13.889404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:40:42.821804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:42.821858 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:40:43.889453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:41:13.889604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:41:42.839399 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:42.839447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:41:43.889378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:13.889452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:42:42.857882 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:42:42.857924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:42:43.889376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:13.889466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:43:42.875276 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:43:42.875422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:43:43.889455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:13.889656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:44:42.894178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:44:42.894247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:44:43.889554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:13.889368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:45:42.911892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:45:42.912237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:45:43.889446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:46:13.889454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:46:42.930697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:46:42.930735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:46:43.889565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:13.889427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:47:42.947624 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:47:42.947675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:47:43.889476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:13.889455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:48:42.968142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:48:42.968178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:48:43.893584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:13.889474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:49:42.986236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:49:42.986281 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:49:43.892209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:13.889453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:50:43.005568 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:50:43.005608 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:50:43.889472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:13.889446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:51:43.023551 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:51:43.023602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:51:43.889513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:13.889461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:52:43.043549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:52:43.043598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:52:43.889588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:13.889455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:53:43.061739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:53:43.061786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:53:43.889486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:13.889620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:54:43.080619 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:54:43.080677 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:54:43.889514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:13.889432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:55:43.101943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:55:43.102156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:55:43.889479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:13.889507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:56:43.121616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:56:43.121664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:56:43.889473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:13.890781 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:57:43.144689 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:57:43.144749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:57:43.889418 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:13.889498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:58:43.163918 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:58:43.163991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:58:43.889452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:13.889459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 03:59:43.181737 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:59:43.181770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 03:59:43.889514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:13.889788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:00:43.207997 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:00:43.208059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:00:43.889591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:13.889590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:01:43.226322 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:01:43.226378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:01:43.889593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:13.889692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:02:43.246468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:02:43.246524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:02:43.889410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:13.889347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:03:43.289758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:03:43.289827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:03:43.889915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:13.889409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:04:43.309794 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:04:43.309848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:04:43.889457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:13.889461 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:05:43.326488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:05:43.326523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:05:43.892250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:13.889578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:06:43.344663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:06:43.344851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:06:43.889439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:13.889437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:07:43.363441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:07:43.363490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:07:43.889465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:13.889468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:08:43.402366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:08:43.402406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:08:43.893498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:13.890090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:09:43.420503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:09:43.420557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:09:43.889432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:13.889690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:10:43.441049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:10:43.441123 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:10:43.889485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:13.889465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:11:43.461243 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:11:43.461309 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:11:43.889501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:13.889527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:12:43.483408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:12:43.483449 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:12:43.889436 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:13.889571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:13:43.500900 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:13:43.500938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:13:43.889430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:13.889510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:14:43.519151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:14:43.519198 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:14:43.889426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:13.889488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:15:43.541579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:15:43.541634 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:15:43.889430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:13.889435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:16:43.568558 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:16:43.568606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:16:43.889453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:13.889449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:17:43.589207 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:17:43.589249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:17:43.889433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:13.889470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:18:43.609119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:18:43.609289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:18:43.889399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:13.889644 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:19:43.630943 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:19:43.631046 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/05 04:19:43.889501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/05 04:20:13.889554 metrics.go:34: INFO No non-zero metrics in the last 30s