By type
2022/04/18 03:07:37.065392 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/18 03:07:37.065474 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/18 03:07:37.065770 logstash.go:90: INFO Max Retries set to: 3
2022/04/18 03:07:37.065831 metrics.go:23: INFO Metrics logging every 30s
2022/04/18 03:07:37.065950 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/18 03:07:37.066581 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-rt9rh
2022/04/18 03:07:37.067144 async.go:63: INFO Flush Interval set to: 1s
2022/04/18 03:07:37.067181 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/18 03:07:37.068121 beat.go:221: INFO filebeat start running.
2022/04/18 03:07:37.068278 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/18 03:07:37.074397 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/18 03:07:37.074546 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/18 03:07:37.074616 crawler.go:38: INFO Loading Prospectors: 1
2022/04/18 03:07:37.074852 registrar.go:236: INFO Starting Registrar
2022/04/18 03:07:37.074969 sync.go:41: INFO Start sending events to output
2022/04/18 03:07:37.074988 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/18 03:07:37.075199 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/18 03:07:37.075264 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/18 03:07:37.075339 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/18 03:08:07.070341 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/04/18 03:08:07.094001 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/18 03:08:07.094342 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/18 03:08:07.094776 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/18 03:08:07.094870 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/18 03:08:07.095040 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/18 03:08:07.113529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:07.113603 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:08.121060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:08.121395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:10.128917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:10.128980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:14.140238 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:14.140689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:22.150697 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:22.150778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:37.066914 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=61
2022/04/18 03:08:38.181373 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:08:38.181444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:09:07.067625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:09:10.187274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:09:10.187333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:09:37.066360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:10:07.066399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:10:10.191875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:10:10.191951 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:10:37.066179 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:11:07.066774 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:11:10.196884 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:11:10.196985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:11:37.066494 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:12:07.066298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:12:10.216454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:12:10.216515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:12:37.066985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:13:07.067407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:13:10.225891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:13:10.225941 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:13:12.111602 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/18 03:13:37.066293 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/18 03:14:07.066324 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:14:10.235371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:14:10.235434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:14:37.066205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:15:07.066250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:15:10.245629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:15:10.245937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:15:37.066178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:16:07.066383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:16:10.255362 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:16:10.255457 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:16:37.066183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:17:07.066381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:17:10.269846 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:17:10.269914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:17:37.066698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:18:07.066524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:18:10.281764 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:18:10.281843 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:18:37.066281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:19:07.066449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:19:10.292340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:19:10.292383 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:19:37.067741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:20:07.066327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:20:10.301720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:20:10.301780 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:20:37.066230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:21:07.067542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:21:10.314868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:21:10.314917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:21:37.066283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:22:07.066362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:22:10.331177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:22:10.331235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:22:37.066220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:23:07.066200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:23:10.339842 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:23:10.339898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:23:37.066360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:24:07.066430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:24:10.347989 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:24:10.348061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:24:37.066344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:25:07.066285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:25:10.358029 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:25:10.358091 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:25:37.066257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:26:07.066340 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:26:10.368220 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:26:10.368284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:26:37.066242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:27:07.066329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:27:10.378820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:27:10.378885 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:27:37.066389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:28:07.066406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:28:10.388632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:28:10.388701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:28:37.066224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:29:07.066381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:29:10.401390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:29:10.401506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:29:37.066365 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:30:07.066345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:30:10.410826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:30:10.410871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:30:37.066289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:31:07.066288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:31:10.419704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:31:10.419746 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:31:37.066263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:32:07.066459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:32:10.428415 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:32:10.428466 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:32:37.066199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:33:07.066649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:33:10.437340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:33:10.437431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:33:37.066313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:34:07.066187 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:34:10.445478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:34:10.445539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:34:37.066245 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:35:07.066413 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:35:10.455058 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:35:10.455101 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:35:37.066398 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:36:07.066509 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:36:10.466025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:36:10.466096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:36:37.066229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:37:07.066408 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:37:10.474150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:37:10.474216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:37:37.066247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:38:07.066235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:38:10.482840 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:38:10.482888 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:38:37.066270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:39:07.066425 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:39:10.493256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:39:10.493311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:39:37.066299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:40:07.066302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:40:10.501595 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:40:10.501654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:40:37.066703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:41:07.066423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:41:10.516811 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:41:10.516887 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:41:37.066342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:42:07.066243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:42:10.526590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:42:10.526681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:42:37.066403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:43:07.066313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:43:10.535332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:43:10.535424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:43:37.066196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:44:07.066302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:44:10.544411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:44:10.544470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:44:37.067613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:45:07.066371 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:45:10.553008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:45:10.553066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:45:37.066318 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:46:07.067624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:46:10.561572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:46:10.561639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:46:37.066307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:47:07.066279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:47:10.571469 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:47:10.571522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:47:37.066183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:48:07.066275 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:48:10.583592 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:48:10.583693 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:48:37.066330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:49:07.066248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:49:10.591883 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:49:10.591943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:49:37.066309 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:50:07.066255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:50:10.600729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:50:10.600786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:50:37.066539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:51:07.066432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:51:10.610886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:51:10.610944 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:51:37.066289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:52:07.066306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:52:10.622062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:52:10.622129 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:52:37.066320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:53:07.066335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:53:10.630657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:53:10.630708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:53:37.066654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:54:07.066497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/18 03:54:10.640837 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/18 03:54:10.640878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host