By type
2022/03/22 03:24:15.031279 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/22 03:24:15.031379 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/22 03:24:15.031524 logstash.go:90: INFO Max Retries set to: 3
2022/03/22 03:24:15.031689 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/22 03:24:15.031912 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-dphh4
2022/03/22 03:24:15.032241 async.go:63: INFO Flush Interval set to: 1s
2022/03/22 03:24:15.032265 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/22 03:24:15.033259 metrics.go:23: INFO Metrics logging every 30s
2022/03/22 03:24:15.033416 beat.go:221: INFO filebeat start running.
2022/03/22 03:24:15.033528 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/22 03:24:15.049721 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/22 03:24:15.049866 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/22 03:24:15.049955 crawler.go:38: INFO Loading Prospectors: 1
2022/03/22 03:24:15.050332 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/22 03:24:15.050491 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/22 03:24:15.050535 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/22 03:24:15.050560 registrar.go:236: INFO Starting Registrar
2022/03/22 03:24:15.050636 sync.go:41: INFO Start sending events to output
2022/03/22 03:24:15.050692 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/22 03:24:35.062404 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/22 03:24:35.062602 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/22 03:24:35.065010 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/22 03:24:35.065371 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/22 03:24:35.066972 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/22 03:24:35.274980 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:35.275089 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:36.293945 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:36.293991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:38.319574 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:38.319625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:42.349547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:42.349658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:45.033612 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=55 registrar.writes=1
2022/03/22 03:24:50.393265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:24:50.393320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:06.435408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:06.435483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:15.033725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:25:38.465334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:38.465395 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:25:45.033653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:26:15.033951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:26:38.522647 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:26:38.522737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:26:45.039285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:27:15.036005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:27:38.549394 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:27:38.549453 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:27:45.033624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:28:15.034402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:28:38.586813 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:28:38.586870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:28:45.036677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:29:15.044289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:29:38.647773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:29:38.648249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:29:40.124538 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/22 03:29:45.033818 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/22 03:29:47.153915 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/22 03:29:47.154066 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/22 03:29:47.154944 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/22 03:30:15.048379 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-3
2022/03/22 03:30:38.772336 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:30:38.772417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:30:45.039841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:31:15.062903 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:31:38.826366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:31:38.826462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:31:45.033661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:32:15.036894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:32:38.990815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:32:38.990900 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:32:45.063777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:33:15.036927 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:33:39.048848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:33:39.048894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:33:45.033743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:34:15.035992 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:34:39.079868 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:34:39.079950 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:34:45.034326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:35:15.050460 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:35:39.155194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:35:39.155681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:35:45.033663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:36:15.033725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:36:39.234205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:36:39.234265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:36:45.045002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:37:15.033881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:37:39.306893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:37:39.306957 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:37:45.033706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:38:15.033599 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:38:39.487785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:38:39.487871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:38:45.066334 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:39:15.033632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:39:39.538685 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:39:39.538740 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:39:45.039980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:40:15.033597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:40:39.593167 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:40:39.593230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:40:45.033637 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:41:15.033899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:41:39.645490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:41:39.645550 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:41:45.035373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:42:15.034214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:42:39.674331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:42:39.674382 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:42:45.033629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:43:15.037925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:43:39.714178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:43:39.714234 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:43:45.033581 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:44:15.033891 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:44:39.756259 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:44:39.756318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:44:45.033606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:45:15.033753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:45:39.891734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:45:39.891842 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:45:45.033803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:46:15.037002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:46:39.924193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:46:39.924265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:46:45.033660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:47:15.033794 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:47:39.949539 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:47:39.949597 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:47:45.033864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:48:15.033732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:48:39.973036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:48:39.973318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:48:45.033686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:49:15.033601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:49:40.000567 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:49:40.000637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:49:45.034654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:50:15.033658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:50:40.039822 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:50:40.039903 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:50:45.033715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:51:15.033722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:51:40.074679 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:51:40.074745 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:51:45.033683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:52:15.033633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:52:40.112773 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:52:40.112989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:52:45.033783 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:53:15.033775 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:53:40.163244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:53:40.163299 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:53:45.033624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:54:15.033862 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:54:40.192734 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:54:40.192795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:54:45.033806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:55:15.033603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:55:40.217409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:55:40.217489 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:55:45.034888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:56:15.033665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:56:40.274261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:56:40.274332 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:56:45.034335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:57:15.033881 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:57:40.310059 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:57:40.310171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:57:45.036227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:58:15.033638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:58:40.384749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:58:40.384800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:58:45.034353 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:59:15.036534 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 03:59:40.422099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:59:40.422236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 03:59:45.033759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:00:15.033835 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:00:40.454506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:00:40.454565 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:00:45.033660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:01:15.033538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:01:40.491439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:01:40.491494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:01:45.033714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:02:15.033896 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:02:40.566524 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:02:40.566592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:02:45.033695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:03:15.033916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:03:40.645986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:03:40.646062 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:03:45.033777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:04:15.035430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:04:40.677743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:04:40.677815 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:04:45.038537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:05:15.035020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:05:40.722088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:05:40.722247 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:05:45.033691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:06:15.033705 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:06:40.775074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:06:40.775145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:06:45.042765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:07:15.033664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:07:40.823749 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:07:40.823827 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:07:45.037368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:08:15.033806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:08:40.903102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:08:40.903181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:08:45.033973 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:09:15.033803 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:09:40.951804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:09:40.951874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:09:45.034858 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:10:15.034343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:10:41.012475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:10:41.012583 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:10:45.033657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:11:15.033536 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:11:41.103826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:11:41.103897 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:11:45.033767 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:12:15.033663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:12:41.190300 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:12:41.190403 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:12:45.033757 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:13:15.033836 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:13:41.245250 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:13:41.245692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:13:45.033955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:14:15.033879 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:14:41.303045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:14:41.303154 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:14:45.033650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:15:15.037751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:15:41.343572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:15:41.343640 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:15:45.033768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:16:15.033687 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:16:41.365042 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:16:41.365118 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:16:45.038391 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:17:15.033758 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:17:41.390442 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:17:41.390525 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:17:45.033801 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:18:15.035003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:18:41.418654 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:18:41.418778 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:18:45.033737 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:19:15.037818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:19:41.452686 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:19:41.452748 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:19:45.033785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:20:15.033798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:20:41.495501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:20:41.495562 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:20:45.033685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:21:15.033753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:21:41.616145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:21:41.616208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:21:45.044805 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:22:15.048626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:22:41.648550 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:22:41.648641 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:22:45.033787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:23:15.033707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:23:41.710718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:23:41.710834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:23:45.037580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:24:15.033946 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:24:41.743701 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:24:41.743927 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:24:45.033860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:25:15.039433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:25:41.777256 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:25:41.777344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:25:45.033738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:26:15.033817 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:26:41.854454 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:26:41.854547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:26:45.044618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:27:15.043925 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:27:41.918501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:27:41.918571 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:27:45.033820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:28:15.045753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:28:41.947864 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:28:41.947929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:28:45.033844 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:29:15.033708 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:29:42.007959 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:29:42.008023 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:29:45.038565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:30:15.042098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:30:42.057374 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:30:42.057471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:30:45.033779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:31:15.033665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:31:42.095506 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:31:42.095592 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:31:45.033689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:32:15.033739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:32:42.136958 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:32:42.137030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:32:45.033860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:33:15.033707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:33:42.267192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:33:42.267296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:33:45.034510 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:34:15.033664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:34:42.292848 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:34:42.292895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:34:45.033667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:35:15.034035 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:35:42.379971 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:35:42.380038 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:35:45.033798 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:36:15.033761 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:36:42.423781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:36:42.423883 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:36:45.033682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:37:15.033607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:37:42.476249 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:37:42.476317 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:37:45.033714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:38:15.033709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:38:42.513137 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:38:42.513231 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:38:45.041176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:39:15.033693 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:39:42.578732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:39:42.578813 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:39:45.038617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:40:15.042446 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:40:42.647070 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:40:42.647167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:40:45.033779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:41:15.033855 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:41:42.686458 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:41:42.686530 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:41:45.033660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:42:15.033651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:42:42.724603 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:42:42.724664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:42:45.033658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:43:15.033722 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:43:42.853657 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:43:42.853707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:43:45.038514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:44:15.034991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:44:42.907248 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:44:42.907330 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:44:45.033715 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:45:15.033714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:45:43.077195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:45:43.077284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:45:45.038505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:46:15.033624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:46:43.151795 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:46:43.151856 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:46:45.033654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:47:15.035607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:47:43.179487 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:47:43.184266 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:47:45.033716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:48:15.033923 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:48:43.247020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:48:43.247069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:48:45.033864 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:49:15.033867 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:49:43.302909 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:49:43.302994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:49:45.033584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:50:15.033799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:50:43.336802 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:50:43.336899 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:50:45.033859 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:51:15.033598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:51:43.386816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:51:43.387069 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:51:45.033576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:52:15.033963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:52:43.436998 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:52:43.437079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:52:45.033655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:53:15.034303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:53:43.542002 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:53:43.542068 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:53:45.033832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:54:15.033626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:54:43.581352 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:54:43.581459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:54:45.033630 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:55:15.033811 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:55:43.625307 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:55:43.625359 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:55:45.033680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:56:15.033692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:56:43.678807 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:56:43.678850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:56:45.033728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:57:15.036144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:57:43.744960 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:57:43.745026 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:57:45.036490 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:58:15.033578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:58:43.777893 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:58:43.778005 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:58:45.033636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:59:15.033640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 04:59:43.834451 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:59:43.834522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 04:59:45.033686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:00:15.036064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:00:43.873139 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:00:43.873187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:00:45.033712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:01:15.033756 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:01:43.900370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:01:43.900459 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:01:45.033702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:02:15.033912 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:02:43.958455 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:02:43.958533 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:02:45.042270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:03:15.033762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/22 05:03:43.990877 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:03:43.990959 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/22 05:03:45.033685 metrics.go:34: INFO No non-zero metrics in the last 30s