Results

          2022/01/05 02:56:16.912722 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/01/05 02:56:16.912754 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/01/05 02:56:16.912827 logstash.go:90: INFO Max Retries set to: 3
2022/01/05 02:56:16.912891 outputs.go:108: INFO Activated logstash as output plugin.
2022/01/05 02:56:16.912967 metrics.go:23: INFO Metrics logging every 30s
2022/01/05 02:56:16.913011 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-bttsf
2022/01/05 02:56:16.913174 async.go:63: INFO Flush Interval set to: 1s
2022/01/05 02:56:16.913196 async.go:64: INFO Max Bulk Size set to: 2048
2022/01/05 02:56:16.913615 beat.go:221: INFO filebeat start running.
2022/01/05 02:56:16.913703 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/01/05 02:56:17.247688 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/01/05 02:56:17.247756 registrar.go:123: INFO States Loaded from registrar: 0
2022/01/05 02:56:17.247838 crawler.go:38: INFO Loading Prospectors: 1
2022/01/05 02:56:17.247995 registrar.go:236: INFO Starting Registrar
2022/01/05 02:56:17.248059 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/01/05 02:56:17.248053 sync.go:41: INFO Start sending events to output
2022/01/05 02:56:17.248115 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/01/05 02:56:17.248439 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/01/05 02:56:17.248499 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/01/05 02:56:17.249264 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/01/05 02:56:17.249400 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/01/05 02:56:17.249514 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/01/05 02:56:17.249543 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/01/05 02:56:17.249405 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/01/05 02:56:17.298702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:17.298746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:18.305763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:18.305805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:20.310011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:20.310035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:24.326622 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:24.326696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:32.336892 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:32.337054 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:46.913488 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=2043 registrar.writes=1
2022/01/05 02:56:48.346386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:56:48.346460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:16.913500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:57:20.355723 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:20.355760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:57:46.913535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:58:16.913683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:58:20.365800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:58:20.365853 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:58:46.913671 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:59:16.913398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 02:59:20.376261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:59:20.376311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 02:59:46.913587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:00:16.913591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:00:20.386954 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:00:20.386988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:00:46.913419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:01:16.913501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:01:20.397126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:01:20.397181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:01:22.261844 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/01/05 03:01:46.913500 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/01/05 03:02:16.913448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:02:20.406660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:02:20.406716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:02:46.913505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:03:16.913782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:03:20.417069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:03:20.417124 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:03:46.914858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:04:16.913454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:04:20.429604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:04:20.429652 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:04:46.913333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:05:16.913499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:05:20.438427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:05:20.438480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:05:46.913540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:06:16.913520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:06:20.455214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:06:20.455273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:06:46.913419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:07:16.913360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:07:20.464233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:07:20.464273 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:07:46.913516 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:08:16.913552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:08:20.474526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:08:20.474568 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:08:46.913430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:09:16.913518 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:09:20.483614 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:09:20.483655 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:09:46.913427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:10:16.913413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:10:20.494133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:10:20.494190 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:10:46.913552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:11:16.913403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:11:20.504362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:11:20.504554 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:11:46.913350 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:12:16.913506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:12:20.520013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:12:20.520057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:12:46.913525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:13:16.913453 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:13:20.528525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:13:20.528573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:13:46.913328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:14:16.913435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:14:20.542603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:14:20.542651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:14:46.913477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:15:16.913376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:15:20.550137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:15:20.550159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:15:46.913404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:16:16.913369 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:16:20.570762 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:16:20.570796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:16:46.913271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:17:16.913439 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:17:20.579076 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:17:20.579127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:17:46.913427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:18:16.913640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:18:20.589177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:18:20.589203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:18:46.913538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:19:16.913487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:19:20.598387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:19:20.598441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:19:46.913497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:20:16.913565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:20:20.611452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:20:20.611500 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:20:46.913373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:21:16.913477 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:21:20.625801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:21:20.625862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:21:46.913483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:22:16.913464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:22:20.636194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:22:20.636241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:22:46.913513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:23:16.913481 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:23:20.646061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:23:20.646096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:23:46.913510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:24:16.913682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:24:20.658278 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:24:20.658331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:24:46.913507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:25:16.913433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:25:20.665890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:25:20.665924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:25:46.913511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:26:16.913464 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:26:20.674146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:26:20.674191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:26:46.913428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:27:16.913504 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:27:20.683563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:27:20.683593 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:27:46.913428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:28:16.913282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:28:20.694433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:28:20.694484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:28:46.913387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:29:16.913463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:29:20.700556 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:29:20.700588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:29:46.913490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:30:16.913358 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:30:20.710004 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:30:20.710035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:30:46.913273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:31:16.913485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:31:20.721039 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:31:20.721088 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:31:46.913930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:32:16.913514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:32:20.742033 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:32:20.742067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:32:46.913404 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:33:16.913501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:33:20.750790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:33:20.750850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:33:46.913491 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:34:16.913591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:34:20.760387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:34:20.760406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:34:46.913607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:35:16.913442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:35:20.767665 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:35:20.767749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:35:46.913347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:36:16.913598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:36:20.781948 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:36:20.781988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:36:46.913409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:37:16.913519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:37:20.789796 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:37:20.789830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:37:46.913469 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:38:16.913441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:38:20.802108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:38:20.802142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:38:46.913553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:39:16.913502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:39:20.812759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:39:20.812810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:39:46.913557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:40:16.913407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:40:20.832345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:40:20.832440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:40:46.913457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:41:16.913452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:41:20.840388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:41:20.840411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:41:46.913655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:42:16.913485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:42:20.849411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:42:20.849441 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:42:46.913423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:43:16.913428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:43:20.857730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:43:20.857764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:43:46.913486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:44:16.913368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:44:20.868001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:44:20.868028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:44:46.913486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:45:16.913448 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:45:20.876299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:45:20.876400 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:45:46.913349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:46:16.913431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:46:20.887364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:46:20.887422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:46:46.913510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:47:16.913406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:47:20.897390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:47:20.897458 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:47:46.913740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:48:16.913389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:48:20.909357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:48:20.909411 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:48:46.913456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:49:16.913522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:49:20.923363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:49:20.923420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:49:46.913550 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:50:16.913729 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:50:20.932839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:50:20.932870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:50:46.913549 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:51:16.913555 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:51:20.940953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:51:20.940990 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:51:46.913446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:52:16.913445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:52:20.951398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:52:20.951525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:52:46.913321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:53:16.913270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:53:20.959526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:53:20.959565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:53:46.913422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:54:16.913408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:54:20.970075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:54:20.970215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:54:46.913400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:55:16.913471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:55:20.979913 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:55:20.979974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:55:46.913391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:56:16.913470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:56:20.996728 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:56:20.996774 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:56:46.913449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:57:16.913525 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:57:21.006902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:57:21.006948 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:57:46.913548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:58:16.913474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:58:21.019043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:58:21.019073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:58:46.913426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:59:16.913585 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 03:59:21.027802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:59:21.027851 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 03:59:46.913402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:00:16.913370 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:00:21.041587 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:00:21.041630 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:00:46.913512 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:01:16.913415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:01:21.049968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:01:21.049998 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:01:46.913527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:02:16.913445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:02:21.060779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:02:21.060830 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:02:46.913407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:03:16.913483 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:03:21.069642 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:03:21.069688 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:03:46.913379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:04:16.913457 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:04:21.081445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:04:21.081507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:04:46.913445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:05:16.913521 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:05:21.089451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:05:21.089492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:05:46.913423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:06:16.913478 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:06:21.099248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:06:21.099296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:06:46.913500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:07:16.913486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:07:21.108716 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:07:21.108762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:07:46.913335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:08:16.913511 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:08:21.119264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:08:21.119361 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:08:46.913385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:09:16.913520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:09:21.136791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:09:21.136844 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:09:46.913425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:10:16.913440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:10:21.155976 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:10:21.156008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:10:46.913420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:11:16.913435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:11:21.163231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:11:21.163263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:11:46.913679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:12:16.913545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:12:21.173231 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:12:21.173263 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:12:46.913381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:13:16.913479 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/01/05 04:13:21.182868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/01/05 04:13:21.182919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host