By type
2022/04/13 03:31:54.865210 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/13 03:31:54.865298 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/13 03:31:54.865423 logstash.go:90: INFO Max Retries set to: 3
2022/04/13 03:31:54.865595 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/13 03:31:54.866064 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-czhld
2022/04/13 03:31:54.866399 async.go:63: INFO Flush Interval set to: 1s
2022/04/13 03:31:54.866436 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/13 03:31:54.867311 metrics.go:23: INFO Metrics logging every 30s
2022/04/13 03:31:54.867357 beat.go:221: INFO filebeat start running.
2022/04/13 03:31:54.867645 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/13 03:31:54.907791 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/13 03:31:54.907930 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/13 03:31:54.908034 crawler.go:38: INFO Loading Prospectors: 1
2022/04/13 03:31:54.908243 sync.go:41: INFO Start sending events to output
2022/04/13 03:31:54.908340 registrar.go:236: INFO Starting Registrar
2022/04/13 03:31:54.908366 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/13 03:31:54.909115 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/13 03:31:54.909155 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/13 03:31:54.908399 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/13 03:32:24.867737 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/04/13 03:32:24.916774 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/13 03:32:24.916880 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/13 03:32:24.918282 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/13 03:32:24.935946 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/13 03:32:24.936081 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/13 03:32:24.950200 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:24.950301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:25.963710 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:25.963760 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:27.972229 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:27.972283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:31.980655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:31.980709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:39.996097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:39.996165 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:54.867878 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=63
2022/04/13 03:32:56.012589 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:32:56.013499 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:24.867871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:33:28.035395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:28.035434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:33:54.867857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:34:24.867766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:34:28.052668 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:34:28.052714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:34:54.867807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:35:24.867816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:35:28.064528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:35:28.064579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:35:54.867899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:24.867703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:36:28.077519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:36:28.077597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:36:54.867852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:37:24.867945 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:37:28.092410 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:37:28.092468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:37:29.970510 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/13 03:37:54.867760 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/13 03:38:24.867814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:38:28.103356 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:38:28.103418 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:38:54.867709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:39:24.867837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:39:28.123548 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:39:28.123623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:39:54.867787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:40:24.867847 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:40:28.147162 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:40:28.147210 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:40:54.867831 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:41:24.867884 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:41:28.183672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:41:28.183710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:41:54.867855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:42:24.867796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:42:28.196982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:42:28.197199 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:42:54.868372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:43:24.873293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:43:28.218946 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:43:28.219003 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:43:54.868002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:44:24.867822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:44:28.247562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:44:28.248890 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:44:54.867801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:45:24.868239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:45:28.281793 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:45:28.281867 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:45:54.867846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:46:24.867734 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:46:28.300159 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:46:28.300212 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:46:54.867874 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:47:24.867816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:47:28.318050 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:47:28.318109 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:47:54.868169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:48:24.868230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:48:28.354190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:48:28.354239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:48:54.867778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:49:24.871976 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:49:28.370958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:49:28.371007 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:49:54.869266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:50:24.867777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:50:28.391430 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:50:28.391506 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:50:54.867937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:51:24.867790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:51:28.426460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:51:28.426533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:51:54.867733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:52:24.867925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:52:28.452586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:52:28.452662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:52:54.867861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:53:24.867706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:53:28.487787 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:53:28.487999 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:53:54.867787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:54:24.868556 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:54:28.511065 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:54:28.511119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:54:54.867875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:55:24.868071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:55:28.528643 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:55:28.528698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:55:54.867848 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:56:24.867817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:56:28.556549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:56:28.556604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:56:54.868102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:57:24.867994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:57:28.573754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:57:28.573813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:57:54.867859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:58:24.867720 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:58:28.588885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:58:28.588942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:58:54.867935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:59:24.867974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 03:59:28.605209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:59:28.605260 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 03:59:54.867788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:00:24.867823 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:00:28.616135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:00:28.616186 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:00:54.867786 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:01:24.867800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:01:28.634472 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:01:28.634523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:01:54.867719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:02:24.867683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:02:28.662980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:02:28.663028 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:02:54.872749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:03:24.867698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:03:28.678155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:03:28.678219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:03:54.867640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:04:24.867728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:04:28.688069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:04:28.688119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:04:54.868107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:05:24.867919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:05:28.710777 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:05:28.710842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:05:54.867842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:06:24.867986 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:06:28.732232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:06:28.732302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:06:54.867857 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:07:24.867767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:07:28.756311 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:07:28.756366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:07:54.867893 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:08:24.868574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:08:28.773707 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:08:28.773758 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:08:54.867817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:09:24.867709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:09:28.789347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:09:28.789505 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:09:54.867816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:10:24.867713 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:10:28.799332 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:10:28.799538 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:10:54.867922 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:11:24.868545 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:11:28.816061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:11:28.816422 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:11:54.867773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:12:24.867852 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:12:28.845585 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:12:28.846194 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:12:54.869220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:13:24.868636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:13:28.858112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:13:28.858160 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:13:54.867880 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:14:24.867995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:14:28.876956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:14:28.877020 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:14:54.867767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:15:24.867766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:15:28.890177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:15:28.890241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:15:54.867787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:16:24.867723 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:16:28.902185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:16:28.902237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:16:54.867824 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:17:24.867773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:17:28.919428 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:17:28.919543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:17:54.867821 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:18:24.867705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:18:28.933473 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:18:28.933515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:18:54.867707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:19:24.867782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:19:28.951927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:19:28.951968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:19:54.867768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:20:24.867744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:20:28.962459 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:20:28.962509 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:20:54.867758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:21:24.867676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:21:28.973343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:21:28.973395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:21:54.867752 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:22:24.867639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/13 04:22:28.987784 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:22:28.987817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/13 04:22:54.867831 metrics.go:34: INFO No non-zero metrics in the last 30s