Results

          2022/03/09 16:21:30.777178 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/09 16:21:30.777263 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 16:21:30.777346 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 16:21:30.777467 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 16:21:30.777597 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 16:21:30.780069 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-n89rh
2022/03/09 16:21:30.780392 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 16:21:30.780419 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 16:21:30.781040 beat.go:221: INFO filebeat start running.
2022/03/09 16:21:30.781108 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 16:21:30.785339 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 16:21:30.785392 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 16:21:30.785432 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 16:21:30.785621 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 16:21:30.785716 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/09 16:21:30.785739 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 16:21:30.785752 registrar.go:236: INFO Starting Registrar
2022/03/09 16:21:30.785783 sync.go:41: INFO Start sending events to output
2022/03/09 16:21:30.785815 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 16:21:50.791402 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/09 16:21:50.792385 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/09 16:21:50.800113 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/09 16:21:50.800764 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/09 16:21:50.800874 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/09 16:21:55.806073 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:55.806119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:56.810510 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:56.810542 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:58.816838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:58.816898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:00.780113 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 registrar.writes=1
2022/03/09 16:22:02.824420 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:02.824456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:10.830434 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:10.830484 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:26.842633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:26.842854 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:30.777962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:22:58.850886 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:58.850928 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:00.777975 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:30.777964 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:58.854113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:58.854148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:00.778266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:30.777963 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:58.857195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:58.857246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:30.777860 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:58.860265 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:58.860302 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:00.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:30.777951 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:55.806791 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:55.815445 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:55.815457 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:55.815449 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:58.863388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:58.863447 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:00.777957 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/09 16:27:10.808654 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:27:30.777958 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/09 16:27:58.867329 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:58.867385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:00.778048 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:30.778001 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:58.870395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:58.870444 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:00.777955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:30.778081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:58.874827 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:58.874862 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:00.777930 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:30.778019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:58.879088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:58.879131 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:00.777917 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:30.777918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:58.882618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:58.882654 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:00.777882 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:30.780983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:58.886357 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:58.886694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:00.778240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:30.777955 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:58.890745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:58.890776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:30.777887 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:58.895645 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:58.895691 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:00.780055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:30.777901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:58.899779 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:58.899820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:00.778011 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:30.777979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:58.903433 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:58.903490 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:00.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:30.777916 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:58.907325 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:58.907357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:00.777878 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:30.777897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:58.910648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:58.910682 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:00.777929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:30.778005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:58.913439 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:58.913480 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:00.778010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:30.777997 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:58.917390 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:58.917434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:00.777940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:30.777987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:58.920564 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:58.920662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:00.777968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:30.777928 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:58.924068 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:58.924105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:30.777969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:58.940091 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:58.940136 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:00.777967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:30.777865 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:58.954482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:58.954521 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:00.777969 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:30.777949 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:58.960681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:58.960732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:00.777968 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:30.777850 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:58.968453 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:58.968501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:00.777953 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:30.777897 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:58.974460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:58.974497 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:00.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:30.777940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:58.981343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:58.981393 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:00.777985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:30.777931 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:58.988145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:58.988189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:00.777977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:30.778120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:58.995648 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:58.995701 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:00.778090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:30.777915 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:59.002098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:59.002150 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:00.777994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:30.777905 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:59.007758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:59.007796 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:00.778009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:30.777888 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:59.014168 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:59.014219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:00.777943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:30.777898 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:59.022597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:59.022643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:00.778096 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:30.777940 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:59.029077 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:59.029119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:00.777989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:30.778060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:59.035856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:59.035929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:00.777908 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:30.778000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:59.045152 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:59.045366 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:00.777935 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:30.777918 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:59.056621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:59.056840 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:00.777950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:30.777934 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:59.063388 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:59.063437 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:00.777989 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:30.778018 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:59.070427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:59.070462 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:01:00.778068 metrics.go:34: INFO No non-zero metrics in the last 30s