By type
2022/03/09 16:36:46.222637 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:36:46.222705 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 16:36:46.222799 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 16:36:46.222851 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 16:36:46.222949 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 16:36:46.223130 publish.go:295: INFO Publisher name: onap-vfc-nslcm-54bbdbd75d-28w7g
2022/03/09 16:36:46.223556 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 16:36:46.223594 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 16:36:46.224235 beat.go:221: INFO filebeat start running.
2022/03/09 16:36:46.224323 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 16:36:46.227460 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 16:36:46.227509 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 16:36:46.227571 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 16:36:46.227584 registrar.go:236: INFO Starting Registrar
2022/03/09 16:36:46.227732 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 16:36:46.227733 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 16:36:46.227871 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/09 16:36:46.227820 sync.go:41: INFO Start sending events to output
2022/03/09 16:36:46.227922 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 16:36:46.228645 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/09 16:37:16.223231 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 publish.events=1 registrar.states.current=1 registrar.states.update=1 registrar.writes=2
2022/03/09 16:37:46.223162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:16.223166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:46.223127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:16.223165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:46.223277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:16.223289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:46.224508 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:16.223256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:46.223168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:51.289028 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:42:16.223212 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.closed=1 filebeat.harvester.open_files=-1 filebeat.harvester.running=-1 publish.events=1 registrar.states.update=1 registrar.writes=1
2022/03/09 16:42:46.223146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:16.223265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:46.223317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:16.223199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:46.223135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:16.223196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:46.223124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:16.223058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:46.223149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:16.223524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:46.223281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:16.223227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:46.223354 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:16.223184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:46.223092 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:16.225695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:46.223167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:16.223352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:46.223130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:16.223086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:46.223080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:16.223108 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:46.223099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:16.223134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:46.223099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:16.223639 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:46.223260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:16.223171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:46.223226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:16.223834 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:46.223080 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:16.223150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:46.223266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:16.223414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:46.223184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:16.223259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:46.223195 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:01:16.223280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:01:46.223133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:02:16.223286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:02:46.223150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:03:16.223160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:03:46.223414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:04:16.223209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:04:46.223116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:05:16.223202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:05:46.223131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:06:16.223097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:06:46.223165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:07:16.223159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:07:26.412046 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/nslcm/runtime_nslcm.log
2022/03/09 17:07:26.477143 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:07:26.477183 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:07:27.482287 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:07:27.482419 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:07:29.486853 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:07:29.486894 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:07:33.493654 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:07:33.493692 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:07:41.498772 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:07:41.498987 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:07:46.223252 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 filebeat.harvester.started=1 libbeat.publisher.published_events=1
2022/03/09 17:07:57.515641 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:07:57.515702 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:08:16.223178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:08:29.535069 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:08:29.535232 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:08:46.223071 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:09:16.223157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:09:29.558121 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:09:29.558209 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:09:46.223144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:10:16.223078 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:10:29.578010 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:10:29.578082 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:10:46.223095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:11:16.223166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:11:29.596774 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:11:29.596947 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:11:46.223117 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:12:16.223104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:12:29.617125 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:12:29.617193 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:12:31.431963 log.go:116: INFO File is inactive: /var/log/onap/vfc/nslcm/runtime_nslcm.log. Closing because close_inactive of 5m0s reached.
2022/03/09 17:12:46.223157 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 17:13:16.223070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:13:29.636466 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:13:29.636529 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:13:46.223121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:14:16.223166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:14:29.656377 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:14:29.656442 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:14:46.223184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:15:16.223203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:15:29.675618 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:15:29.675665 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:15:46.223102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:16:16.223103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:16:29.696397 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:16:29.696449 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:16:46.223058 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:17:16.223196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:17:29.715675 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:17:29.715769 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:17:46.223093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:18:16.223133 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:18:29.736493 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:18:29.736691 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:18:46.223098 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:19:16.223074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:19:29.758024 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:19:29.758103 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:19:46.223086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:20:16.223137 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:20:29.778560 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:20:29.778615 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:20:46.223139 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:21:16.223110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:21:29.800839 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:21:29.800886 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:21:46.223135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:22:16.223144 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:22:29.821347 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:22:29.821403 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:22:46.223135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:23:16.223128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:23:29.838894 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:23:29.838941 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:23:46.223121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:24:16.223155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:24:29.857563 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:24:29.857610 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:24:46.223234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:25:16.223376 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:25:29.876277 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:25:29.876330 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:25:46.223111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:26:16.223135 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:26:29.896466 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:26:29.896539 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:26:46.223111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:27:16.224082 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:27:29.915848 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:27:29.915897 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:27:46.223076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:28:16.223101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:28:29.934580 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:28:29.934624 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:28:46.223159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:29:16.223110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:29:29.954187 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:29:29.954234 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:29:46.223155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:30:16.223109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:30:29.972494 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:30:29.972537 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:30:46.223129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:31:16.223162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:31:29.992316 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:31:29.992357 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:31:46.223086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:32:16.223176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:32:30.011137 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:32:30.011175 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:32:46.223091 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:33:16.223256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:33:30.032001 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:33:30.032045 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:33:46.223260 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:34:16.223208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:34:30.053074 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:34:30.053115 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:34:46.223101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:35:16.223238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:35:30.072702 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:35:30.072764 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:35:46.223083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:36:16.223540 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:36:30.092789 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:36:30.092851 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:36:46.223162 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:37:16.223120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:37:30.115014 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:37:30.115201 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:37:46.246086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:38:16.223155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:38:30.134837 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:38:30.134880 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:38:46.223296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:39:16.226099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:39:30.152064 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:39:30.152182 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:39:46.223165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:40:16.224007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:40:30.168992 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:40:30.169047 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:40:46.223124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:41:16.223110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:41:30.190133 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:41:30.190182 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:41:46.223128 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:42:16.223238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:42:30.209463 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:42:30.209519 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:42:46.223067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:43:16.223123 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:43:30.230595 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:43:30.230697 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:43:46.223267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:44:16.223212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:44:30.249462 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:44:30.249506 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:44:46.223167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:45:16.223205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:45:30.270336 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:45:30.270379 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:45:46.223136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:46:16.223067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:46:30.291864 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:46:30.291910 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:46:46.223104 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:47:16.223099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:47:30.309395 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:47:30.309436 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:47:46.223423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:48:16.223223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:48:30.325677 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:48:30.325721 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:48:46.223111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:49:16.223147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:49:30.347042 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:49:30.347095 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:49:46.223070 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:50:16.223132 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:50:30.367284 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:50:30.367332 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:50:46.223110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:51:16.223188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:51:30.387182 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:51:30.387218 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:51:46.223076 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:52:16.223168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:52:30.406976 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:52:30.407034 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:52:46.223090 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:53:16.223172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:53:30.426429 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:53:30.426469 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:53:46.223099 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:54:16.223116 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:54:30.446933 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:54:30.446982 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:54:46.223151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:55:16.223124 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:55:30.468518 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:55:30.468733 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:55:46.223157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:56:16.223102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:56:30.489738 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:56:30.489879 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:56:46.223085 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:57:16.223120 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:57:30.511122 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:57:30.511166 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:57:46.223131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:58:16.223089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:58:30.529730 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:58:30.529784 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:58:46.223146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:59:16.223106 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:59:30.549872 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:59:30.550082 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:59:46.223102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:00:16.223105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:00:30.569034 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:00:30.569078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:00:46.223102 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:01:16.223223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 18:01:30.591521 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:01:30.591585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 18:01:46.223243 metrics.go:34: INFO No non-zero metrics in the last 30s