By type
2022/03/08 10:39:51.605351 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/08 10:39:51.605483 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/08 10:39:51.605665 logstash.go:90: INFO Max Retries set to: 3
2022/03/08 10:39:51.605819 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/08 10:39:51.606085 metrics.go:23: INFO Metrics logging every 30s
2022/03/08 10:39:51.606392 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-kxcvj
2022/03/08 10:39:51.606771 async.go:63: INFO Flush Interval set to: 1s
2022/03/08 10:39:51.606815 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/08 10:39:51.608206 beat.go:221: INFO filebeat start running.
2022/03/08 10:39:51.608331 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/08 10:39:51.623264 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/08 10:39:51.623428 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/08 10:39:51.623662 registrar.go:236: INFO Starting Registrar
2022/03/08 10:39:51.623731 crawler.go:38: INFO Loading Prospectors: 1
2022/03/08 10:39:51.626658 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/08 10:39:51.627134 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/08 10:39:51.627294 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/08 10:39:51.627328 sync.go:41: INFO Start sending events to output
2022/03/08 10:39:51.627437 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/08 10:40:21.607571 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/08 10:40:21.633665 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/08 10:40:21.634151 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/08 10:40:21.634435 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/08 10:40:21.634657 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/08 10:40:21.634931 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/08 10:40:21.709366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:21.709419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:22.714509 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:22.714551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:24.729146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:24.729203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:28.794528 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:28.794613 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:36.848586 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:36.849097 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:51.606669 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
2022/03/08 10:40:52.938855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:40:52.938995 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:41:21.606692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:41:24.979626 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:41:24.979692 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:41:51.606735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:42:21.606954 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:42:25.022009 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:42:25.022093 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:42:51.607286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:43:21.606612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:43:25.058935 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:43:25.059030 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:43:51.606568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:44:21.606796 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:44:25.109366 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:44:25.109424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:44:51.609043 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:45:21.606559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:45:25.133836 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:45:25.133896 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:45:26.698431 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/08 10:45:33.719046 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/08 10:45:33.719109 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/08 10:45:33.719293 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/08 10:45:51.606584 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-4
2022/03/08 10:46:21.606739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:46:25.168092 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:46:25.169522 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:46:51.606719 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:47:21.606799 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:47:25.228099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:47:25.228174 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:47:51.608808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:48:21.606749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:48:25.250845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:48:25.251235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:48:51.606442 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:49:21.606654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:49:25.276471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:49:25.276536 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:49:51.610998 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:50:21.606470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:50:25.315215 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:50:25.315295 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:50:51.606906 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:51:21.610465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:51:25.352680 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:51:25.353581 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:51:51.612911 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:52:21.608476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:52:25.459629 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:52:25.459708 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:52:51.606861 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:53:21.606575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:53:25.540383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:53:25.540456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:53:51.606564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:54:21.607388 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:54:25.612966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:54:25.613019 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:54:51.606677 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:55:21.608886 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:55:25.648441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:55:25.648524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:55:51.611939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:56:21.606625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:56:25.677226 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:56:25.677473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:56:51.607299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:57:21.607080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:57:25.721403 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:57:25.721491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:57:51.611682 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:58:21.606818 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:58:25.797590 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:58:25.797909 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:58:51.606646 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:59:21.606622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 10:59:25.832543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:59:25.832862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 10:59:51.606620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:00:21.606728 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:00:25.866826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:00:25.866929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:00:51.606746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:01:21.606564 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:01:25.919921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:01:25.919964 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:01:51.606974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:02:21.607582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:02:25.948049 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:02:25.948126 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:02:51.606548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:03:21.609379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:03:25.998692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:03:25.998751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:03:51.606680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:04:21.613795 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:04:26.054341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:04:26.054401 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:04:51.606808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:05:21.606551 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:05:26.091312 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:05:26.091388 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:05:51.606813 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:06:21.606942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:06:26.138340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:06:26.138415 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:06:51.607098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:07:21.611327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:07:26.163692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:07:26.163756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:07:51.606762 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:08:21.606575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:08:26.191205 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:08:26.191280 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:08:51.606532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:09:21.606672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:09:26.233758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:09:26.233838 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:09:51.614827 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:10:21.608299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:10:26.276504 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:10:26.276576 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:10:51.606557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:11:21.606691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:11:26.317091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:11:26.317167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:11:51.607456 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:12:21.606643 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:12:26.344164 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:12:26.344215 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:12:51.606749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:13:21.608905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:13:26.369652 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:13:26.369735 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:13:51.606568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:14:21.609415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:14:26.429241 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:14:26.429837 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:14:51.606851 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:15:21.606655 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:15:26.455296 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:15:26.455378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:15:51.606806 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:16:21.606598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:16:26.499233 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:16:26.499277 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:16:51.606578 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:17:21.606613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:17:26.531085 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:17:26.531164 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:17:51.606614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:18:21.606476 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:18:26.564658 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:18:26.564730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:18:51.610381 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:19:21.609323 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:19:26.614171 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:19:26.614301 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:19:51.607032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:20:21.606704 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:20:26.657475 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:20:26.657567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:20:51.606816 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:21:21.608295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:21:26.700132 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:21:26.700216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:21:51.607034 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:22:21.607519 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:22:26.723015 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:22:26.723075 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:22:51.607709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:23:21.609399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:23:26.754632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:23:26.754733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:23:51.606830 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:24:21.606572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:24:26.804650 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:24:26.805524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:24:51.606664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:25:21.606838 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:25:26.890155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:25:26.890258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:25:51.606503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:26:21.606584 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:26:26.972471 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:26:26.972547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:26:51.606707 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:27:21.606904 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:27:26.997669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:27:26.997731 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:27:51.607299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:28:21.606717 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:28:27.040134 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:28:27.040205 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:28:51.607822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:29:21.606627 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:29:27.066824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:29:27.066935 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:29:51.606744 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:30:21.606688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:30:27.095347 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:30:27.095419 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:30:51.606807 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:31:21.606528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:31:27.143955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:31:27.144684 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:31:51.606956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:32:21.606636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:32:27.174202 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:32:27.174311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:32:51.606672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:33:21.615027 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:33:27.211839 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:33:27.211914 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:33:51.606751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:34:21.610965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:34:27.244579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:34:27.244646 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:34:51.606618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:35:21.606459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:35:27.296361 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:35:27.296432 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:35:51.606619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:36:21.606513 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:36:27.326721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:36:27.326802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:36:51.606613 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:37:21.606812 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:37:27.358271 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:37:27.358333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:37:51.606898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:38:21.606771 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:38:27.401293 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:38:27.401360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:38:51.606535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:39:21.606617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:39:27.449185 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:39:27.449242 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:39:51.607182 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:40:21.606653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:40:27.517413 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:40:27.517467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:40:51.613623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:41:21.606788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:41:27.551017 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:41:27.551072 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:41:51.616280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:42:21.614363 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:42:27.593706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:42:27.593768 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:42:51.606595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:43:21.606609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:43:27.644192 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:43:27.644253 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:43:51.606826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:44:21.606641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:44:27.736386 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:44:27.736471 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:44:51.606528 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:45:21.606892 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:45:27.760082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:45:27.760172 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:45:51.610955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:46:21.606507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:46:27.793812 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:46:27.793871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:46:51.606749 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:47:21.607450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:47:27.830195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:47:27.830316 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:47:51.606699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:48:21.606647 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:48:27.855805 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:48:27.855871 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:48:51.606537 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:49:21.606598 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:49:27.878770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:49:27.878846 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:49:51.607366 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:50:21.606919 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:50:27.930513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:50:27.930578 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:50:51.606654 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:51:21.606875 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:51:27.966941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:51:27.967119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:51:51.611149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:52:21.611088 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:52:27.995237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:52:27.995321 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:52:51.611668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:53:21.607121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:53:28.024566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:53:28.024637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:53:51.607047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:54:21.606711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:54:28.050632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:54:28.050850 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:54:51.606544 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:55:21.607788 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:55:28.095903 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:55:28.096901 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:55:51.614380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:56:21.606956 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:56:28.174604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:56:28.174694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:56:51.607535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:57:21.606522 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:57:28.240700 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:57:28.240769 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:57:51.608507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:58:21.606849 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:58:28.268007 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:58:28.268059 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:58:51.606691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:59:21.606942 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 11:59:28.351110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:59:28.351185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 11:59:51.606538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:00:21.609372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:00:28.395032 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:00:28.395095 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:00:51.606616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:01:21.606590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:01:28.441660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:01:28.441737 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:01:51.606622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:02:21.606939 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:02:28.471704 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:02:28.471777 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:02:51.606965 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:03:21.607743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:03:28.518060 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:03:28.518105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:03:51.606678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:04:21.606514 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:04:28.569412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:04:28.569486 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:04:51.606487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:05:21.606507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:05:28.636388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:05:28.636467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:05:51.606582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:06:21.606658 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:06:28.675210 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:06:28.675264 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:06:51.609392 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:07:21.606822 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:07:28.727830 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:07:28.727907 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:07:51.608441 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:08:21.606841 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:08:28.753262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:08:28.753357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:08:51.608260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:09:21.606997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:09:28.809895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:09:28.810021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:09:51.608706 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:10:21.606793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/08 12:10:28.842753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/08 12:10:28.842795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host