By type
2022/02/06 02:55:11.524431 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/02/06 02:55:11.524480 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/02/06 02:55:11.524565 metrics.go:23: INFO Metrics logging every 30s
2022/02/06 02:55:11.524583 logstash.go:90: INFO Max Retries set to: 3
2022/02/06 02:55:11.524652 outputs.go:108: INFO Activated logstash as output plugin.
2022/02/06 02:55:11.524754 publish.go:295: INFO Publisher name: onap-portal-app-9c5c78dc6-djbbb
2022/02/06 02:55:11.524935 async.go:63: INFO Flush Interval set to: 1s
2022/02/06 02:55:11.524952 async.go:64: INFO Max Bulk Size set to: 2048
2022/02/06 02:55:11.525307 beat.go:221: INFO filebeat start running.
2022/02/06 02:55:11.525373 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/02/06 02:55:11.571601 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/02/06 02:55:11.571690 registrar.go:123: INFO States Loaded from registrar: 0
2022/02/06 02:55:11.571744 crawler.go:38: INFO Loading Prospectors: 1
2022/02/06 02:55:11.571860 registrar.go:236: INFO Starting Registrar
2022/02/06 02:55:11.571914 sync.go:41: INFO Start sending events to output
2022/02/06 02:55:11.572059 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/02/06 02:55:11.572113 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/02/06 02:55:11.572235 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/02/06 02:55:11.572283 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/02/06 02:55:31.574138 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/02/06 02:55:31.574256 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/02/06 02:55:31.574526 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/02/06 02:55:31.574668 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/02/06 02:55:31.574749 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/02/06 02:55:36.603359 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:36.603391 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:37.607482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:37.607544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:39.610333 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:39.610374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:41.524972 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=76 registrar.writes=1
2022/02/06 02:55:43.620367 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:43.620409 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:51.629654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:55:51.629711 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:56:07.640801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:56:07.640863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:56:11.525092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:56:39.651692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:56:39.651752 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:56:41.524958 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:57:11.525010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:57:39.661502 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:39.661541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:57:41.525089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:58:11.525108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:58:39.685112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:39.685171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:58:41.524894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:59:11.525004 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 02:59:39.767510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:59:39.767572 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 02:59:41.525048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:00:11.525049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:00:36.586204 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/02/06 03:00:39.846465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:00:39.846511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:00:41.524989 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/02/06 03:01:11.525049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:01:39.871393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:01:39.871438 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:01:41.524894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:02:11.524962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:02:40.056014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:02:40.056057 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:02:41.525085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:03:11.524900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:03:40.198718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:03:40.198764 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:03:41.524980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:04:11.525008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:04:40.346167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:04:40.346213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:04:41.525017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:05:11.525140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:05:40.362470 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:05:40.362546 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:05:41.524955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:06:11.525153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:06:40.370259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:06:40.370342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:06:41.525061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:07:11.525115 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:07:40.380065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:07:40.380091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:07:41.525021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:08:11.525073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:08:40.390054 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:08:40.390098 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:08:41.525038 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:09:11.524977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:09:40.399432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:09:40.399492 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:09:41.524947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:10:11.525015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:10:40.408057 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:10:40.408091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:10:41.524923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:11:11.524923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:11:40.417146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:11:40.417178 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:11:41.524996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:12:11.524830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:12:40.425050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:12:40.425078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:12:41.525002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:13:11.524973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:13:40.435927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:13:40.435960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:13:41.524995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:14:11.525011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:14:40.444890 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:14:40.444925 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:14:41.525033 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:15:11.524918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:15:40.455151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:15:40.455194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:15:41.524887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:16:11.524969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:16:40.464928 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:16:40.464975 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:16:41.524947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:17:11.524927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:17:40.474165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:17:40.474193 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:17:41.525044 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:18:11.524940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:18:40.483508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:18:40.483540 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:18:41.524931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:19:11.524926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:19:40.493365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:19:40.493807 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:19:41.524873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:20:11.525022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:20:40.503879 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:20:40.503987 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:20:41.525045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:21:11.524979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:21:40.514088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:21:40.514133 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:21:41.524926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:22:11.525036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:22:40.523688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:22:40.523733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:22:41.524959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:23:11.525186 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:23:40.535529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:23:40.535577 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:23:41.525042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:24:11.524960 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:24:40.546643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:24:40.546678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:24:41.524964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:25:11.524866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:25:40.557465 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:25:40.557498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:25:41.525008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:26:11.525046 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:26:40.568109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:26:40.568160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:26:41.524929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:27:11.524979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:27:40.578553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:27:40.578595 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:27:41.524906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:28:11.524982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:28:40.588375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:28:40.588403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:28:41.525010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:29:11.524895 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:29:40.599496 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:29:40.599545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:29:41.525007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:30:11.524956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:30:40.610609 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:30:40.610663 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:30:41.524973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:31:11.524951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:31:40.620596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:31:40.620627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:31:41.525092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:32:11.524991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:32:40.630136 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:32:40.630182 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:32:41.524948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:33:11.524929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:33:40.642899 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:33:40.642940 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:33:41.524957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:34:11.524926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:34:40.652425 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:34:40.652482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:34:41.524949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:35:11.525003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:35:40.663498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:35:40.663541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:35:41.525023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:36:11.524965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:36:40.674144 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:36:40.674211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:36:41.525021 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:37:11.524972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:37:40.682962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:37:40.683008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:37:41.524987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:38:11.525011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:38:40.691589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:38:40.691617 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:38:41.524915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:39:11.524939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:39:40.700089 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:39:40.700144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:39:41.525071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:40:11.524887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:40:40.709527 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:40:40.709562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:40:41.524976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:41:11.524888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:41:40.721112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:41:40.721154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:41:41.524921 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:42:11.524968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:42:40.730790 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:42:40.730835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:42:41.524881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:43:11.524900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:43:40.738725 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:43:40.738762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:43:41.524974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:44:11.524922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:44:40.750086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:44:40.750130 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:44:41.525039 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:45:11.524986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:45:40.759407 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:45:40.759455 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:45:41.525026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:46:11.524948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:46:40.768992 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:46:40.769040 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:46:41.525029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:47:11.524942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:47:40.779189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:47:40.779253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:47:41.524978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:48:11.525011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:48:40.789343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:48:40.789489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:48:41.524919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:49:11.524955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:49:40.800632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:49:40.800699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:49:41.524957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:50:11.524978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:50:40.811546 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:50:40.811571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:50:41.524967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:51:11.524963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:51:40.821701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:51:40.821747 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:51:41.524952 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:52:11.525000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:52:40.832101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:52:40.832141 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:52:41.524947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:53:11.524908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:53:40.844161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:53:40.844194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:53:41.524951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:54:11.524959 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:54:40.855520 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:54:40.855566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:54:41.524888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:55:11.524983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:55:40.866260 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:55:40.866322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:55:41.524992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:56:11.525036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:56:40.876139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:56:40.876176 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:56:41.524975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:57:11.525137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:57:40.887463 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:57:40.887508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:57:41.525051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:58:11.524987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:58:40.935623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:58:40.935672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:58:41.525185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:59:11.524988 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 03:59:40.947838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:59:40.947898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 03:59:41.525132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:00:11.524963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:00:40.959627 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:00:40.959666 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:00:41.524993 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:01:11.525029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:01:40.971432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:01:40.971461 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:01:41.524962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:02:11.524978 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:02:40.982621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:02:40.982664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:02:41.524976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:03:11.525020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:03:40.993549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:03:40.993585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:03:41.525056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:04:11.525067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:04:41.002485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:04:41.002553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:04:41.524897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:05:11.525060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/02/06 04:05:41.012592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:05:41.012631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/02/06 04:05:41.525111 metrics.go:34: INFO No non-zero metrics in the last 30s