2022/03/15 14:38:12.824731 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/03/15 14:38:12.824806 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/15 14:38:12.824947 logstash.go:90: INFO Max Retries set to: 3
2022/03/15 14:38:12.825071 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/15 14:38:12.825227 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-v829x
2022/03/15 14:38:12.825530 async.go:63: INFO Flush Interval set to: 1s
2022/03/15 14:38:12.825572 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/15 14:38:12.826261 beat.go:221: INFO filebeat start running.
2022/03/15 14:38:12.826373 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/15 14:38:12.827780 metrics.go:23: INFO Metrics logging every 30s
2022/03/15 14:38:12.832813 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/15 14:38:12.832913 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/15 14:38:12.832968 crawler.go:38: INFO Loading Prospectors: 1
2022/03/15 14:38:12.832996 registrar.go:236: INFO Starting Registrar
2022/03/15 14:38:12.833075 sync.go:41: INFO Start sending events to output
2022/03/15 14:38:12.833172 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/15 14:38:12.833229 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/15 14:38:12.833316 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/15 14:38:12.833340 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/15 14:38:32.835737 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/15 14:38:32.836587 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/15 14:38:32.836690 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/15 14:38:32.836709 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/15 14:38:32.837154 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/15 14:38:37.856565 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:37.856613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:38.863185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:38.863258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:40.867974 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:40.868035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:42.831368 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=64 publish.events=3 registrar.states.current=3 registrar.states.update=3 registrar.writes=2
2022/03/15 14:38:44.877261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:44.877331 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:52.883389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:38:52.883436 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:39:08.908538 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:39:08.908604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:39:12.828083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:39:40.931547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:39:40.931631 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:39:42.828302 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:40:12.828165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:40:40.951960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:40:40.952019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:40:42.828104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:41:12.828149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:41:40.972678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:41:40.972871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:41:42.828094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:42:12.828072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:42:40.995014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:42:40.995066 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:42:42.828026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:43:12.828095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:43:37.849700 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/15 14:43:37.849779 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/15 14:43:37.849707 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/15 14:43:37.849869 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/15 14:43:41.021086 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:43:41.021138 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:43:42.830002 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=4 filebeat.harvester.open_files=-4 filebeat.harvester.running=-4
2022/03/15 14:43:52.854316 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/15 14:44:12.828123 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1
2022/03/15 14:44:41.048655 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:44:41.048726 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:44:42.828144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:45:12.828066 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:45:41.067646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:45:41.067696 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:45:42.828147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:46:12.828110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:46:41.090042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:46:41.090116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:46:42.828071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:47:12.828071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:47:41.112363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:47:41.112425 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:47:42.828120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:48:12.828889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:48:41.133249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:48:41.133306 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:48:42.828070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:49:12.828085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:49:41.153993 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:49:41.154041 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:49:42.828081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:50:12.828103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:50:41.174281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:50:41.174370 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:50:42.828113 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:51:12.828100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:51:41.193117 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:51:41.193191 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:51:42.828071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:52:12.828192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:52:41.212891 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:52:41.212932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:52:42.828056 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:53:12.828068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:53:41.233223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:53:41.233401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:53:42.828141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:54:12.828198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:54:41.256067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:54:41.256122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:54:42.828145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:55:12.828094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:55:41.280844 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:55:41.280898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:55:42.828041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:56:12.828090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:56:41.299216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:56:41.299255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:56:42.828096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:57:12.828077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:57:41.318915 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:57:41.318970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:57:42.828088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:58:12.829485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:58:41.338134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:58:41.338184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:58:42.828089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:59:12.828152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 14:59:41.356704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:59:41.356762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 14:59:42.828128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:00:12.828252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:00:41.376759 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:00:41.376803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:00:42.828149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:01:12.828196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:01:41.394874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:01:41.394942 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:01:42.828040 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:02:12.828084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:02:41.413713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:02:41.413770 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:02:42.828071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:03:12.828168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:03:41.441903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:03:41.441980 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:03:42.828094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:04:12.828161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:04:41.461495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:04:41.461541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:04:42.828089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:05:12.828542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:05:41.482092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:05:41.482238 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:05:42.828084 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:06:12.828059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:06:41.500996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:06:41.501183 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:06:42.828057 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:07:12.828053 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:07:41.532432 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:07:41.532497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:07:42.828147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:08:12.828110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:08:41.551541 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:08:41.551587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:08:42.828523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:09:12.828154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:09:41.573071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:09:41.573114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:09:42.828146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:10:12.828120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:10:41.594215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:10:41.594271 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:10:42.828063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:11:12.828098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:11:41.613295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:11:41.613339 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:11:42.828052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:12:12.828114 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:12:41.633051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:12:41.633122 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:12:42.828118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:13:12.828129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:13:41.655652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:13:41.655691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:13:42.828036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:14:12.828130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:14:41.676150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:14:41.676348 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:14:42.828077 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:15:12.828190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:15:41.695218 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:15:41.695277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:15:42.828161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:16:12.828063 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:16:41.715763 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:16:41.715832 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:16:42.828125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:17:12.828072 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:17:41.735429 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:17:41.735468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:17:42.828075 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:18:12.828141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:18:41.756850 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:18:41.757030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:18:42.828055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:19:12.828109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:19:41.777099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:19:41.777164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:19:42.828101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:20:12.828122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:20:41.796104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:20:41.796157 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:20:42.828098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:21:12.828145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:21:41.815380 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:21:41.815420 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:21:42.828061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:22:12.828120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:22:41.834401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:22:41.834467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:22:42.828096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:23:12.828122 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:23:41.866483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:23:41.866562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:23:42.828198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:24:12.828204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:24:41.885291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:24:41.885334 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:24:42.828051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:25:12.828149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:25:41.905495 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:25:41.905556 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:25:42.828051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:26:12.828109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:26:41.928196 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:26:41.928240 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:26:42.828119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:27:12.828153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:27:41.949140 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:27:41.949196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:27:42.828714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:28:12.828116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:28:41.971676 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:28:41.971722 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:28:42.828200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:29:12.828086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:29:41.990856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:29:41.990897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:29:42.828267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:30:12.828173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:30:42.010761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:30:42.010803 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:30:42.828050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:31:12.828153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:31:42.032376 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:31:42.032432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:31:42.828076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:32:12.828288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:32:42.052030 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:32:42.052072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:32:42.828140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:33:12.828073 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:33:42.073438 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:33:42.073507 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:33:42.828068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:34:12.828107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:34:42.097700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:34:42.097753 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:34:42.828101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:35:12.828168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:35:42.116856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:35:42.116908 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:35:42.828083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:36:12.828060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:36:42.135401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:36:42.135448 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/15 15:36:42.828088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/15 15:37:12.828075 metrics.go:34: INFO No non-zero metrics in the last 30s