Results

          2022/03/05 03:29:03.985858 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/05 03:29:03.985969 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/05 03:29:03.986115 logstash.go:90: INFO Max Retries set to: 3
2022/03/05 03:29:03.986327 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/05 03:29:03.986491 publish.go:295: INFO Publisher name: onap-vfc-zte-vnfm-driver-65d7c4d97b-xwzcz
2022/03/05 03:29:03.986773 async.go:63: INFO Flush Interval set to: 1s
2022/03/05 03:29:03.986836 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/05 03:29:03.985974 metrics.go:23: INFO Metrics logging every 30s
2022/03/05 03:29:03.987879 beat.go:221: INFO filebeat start running.
2022/03/05 03:29:03.987939 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/05 03:29:03.990950 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/05 03:29:03.990993 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/05 03:29:03.991044 crawler.go:38: INFO Loading Prospectors: 1
2022/03/05 03:29:03.991188 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/05 03:29:03.991292 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/05 03:29:03.991322 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/05 03:29:03.991334 registrar.go:236: INFO Starting Registrar
2022/03/05 03:29:03.991384 sync.go:41: INFO Start sending events to output
2022/03/05 03:29:03.991416 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/05 03:29:03.991985 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/05 03:29:33.987323 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/05 03:30:03.987288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:30:33.987178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:03.987311 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:31:33.987317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:03.987426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:32:33.987235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:03.987295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:33:33.987330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:03.987387 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:34:09.001334 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/05 03:34:33.987311 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/05 03:35:03.987188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:35:33.987222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:03.987232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:36:33.987320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:03.987587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:37:33.987428 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:03.987384 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:38:33.987330 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:03.987192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:39:33.987256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:03.987322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:40:33.987181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:03.987270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:41:33.987250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:03.987207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:42:33.987259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:03.987183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:43:33.987242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:03.987292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:44:33.987258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:03.987296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:45:33.987223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:03.987256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:46:33.987214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:03.987226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:47:33.987409 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:03.987243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:48:33.987225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:03.987239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:49:33.987200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:03.987165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:50:33.987299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:03.987321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:51:33.987192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:03.987342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:52:33.987379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:03.987199 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:53:33.987209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:03.987219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:54:33.987223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:03.987172 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:55:33.987284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:03.987193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:56:33.987214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:03.987141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:57:33.987229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:03.987569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:33.987224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:58:34.139148 log.go:91: INFO Harvester started for file: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log
2022/03/05 03:58:39.094639 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:39.094678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:40.099667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:40.099707 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:42.104780 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:42.104817 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:46.113746 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:46.113784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:54.133713 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:58:54.133755 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:03.987256 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/05 03:59:10.141721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:10.141761 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:33.987399 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 03:59:42.146747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 03:59:42.146785 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:03.987462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:33.987288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:00:42.149920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:00:42.149974 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:03.987241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:33.987487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:01:42.154573 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:01:42.154616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:03.987198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:33.987259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:02:42.158071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:02:42.158119 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:03.987266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:33.987299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:03:39.157744 log.go:116: INFO File is inactive: /var/log/onap/vfc/ztevnfmdriver/runtime_ztevnfmdriver.log. Closing because close_inactive of 5m0s reached.
2022/03/05 04:03:42.162288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:03:42.162324 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:03.987362 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/05 04:04:33.987298 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:04:42.166494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:04:42.166535 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:03.987331 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:33.987211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:05:42.174774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:05:42.174810 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:03.987259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:33.987256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:06:42.178902 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:06:42.178952 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:03.987364 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:33.987299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:07:42.182078 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:07:42.182116 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:03.987166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:33.987220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:08:42.185583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:08:42.185621 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:03.987205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:33.987347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:09:42.191824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:09:42.191943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:03.987207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:33.987243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:10:42.194860 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:10:42.194917 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:03.987254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:33.987252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:11:42.198878 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:11:42.198922 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:03.987240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:33.987221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:12:42.202702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:12:42.202744 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:03.987234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:33.987267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:13:42.206199 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:13:42.206265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:03.987169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:33.987377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:14:42.209401 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:14:42.209440 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:03.987283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:33.987648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:15:42.213378 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:15:42.213417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:03.987289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:33.987592 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:16:42.218485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:16:42.218700 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:03.987261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:33.990837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:17:42.222616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:17:42.222651 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:03.987220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:33.987271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:18:42.226938 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:18:42.226977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:03.987181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:33.987268 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:19:42.230369 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:19:42.230406 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:03.987183 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:33.987210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:20:42.234563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:20:42.234600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:03.987379 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:33.987243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:21:42.238326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:21:42.238371 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:03.987241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:33.987237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:22:42.242064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:22:42.242134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:03.987184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:33.987329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:23:42.248204 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:23:42.248705 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:03.987145 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:33.987506 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:24:42.252255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:24:42.252296 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:03.987703 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:33.987261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:25:42.257350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:25:42.257408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:03.987200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:33.987181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:26:42.261708 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:26:42.261754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:03.987299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:33.987265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:27:42.266512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:27:42.266552 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:03.987241 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:33.987165 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:28:42.270340 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:28:42.270381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:03.987246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:33.987197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:29:42.274244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:29:42.274284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:03.987193 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:33.987345 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:30:42.279345 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:30:42.279381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:03.987233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:33.987224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:31:42.284636 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:31:42.284714 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:03.987243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:33.987356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:32:42.290831 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:32:42.290919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:03.987777 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:33.988765 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:33:42.295342 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:33:42.295385 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:03.987400 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:33.987329 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:34:42.300146 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:34:42.300185 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:03.987244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:33.987194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:35:42.304052 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:35:42.304086 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:03.987520 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:33.987304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:36:42.308582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:36:42.308624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:03.987256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:33.987385 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:37:42.312387 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:37:42.312428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:03.987208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:33.987173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:38:42.315991 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:38:42.316044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:03.987177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:33.987229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:39:42.319721 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:39:42.319751 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:03.987261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:33.988045 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:40:42.325195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:40:42.325256 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:03.987272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:33.987221 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:41:42.328761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:41:42.328792 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:03.987254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:33.987226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:42:42.333507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:42:42.333539 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:03.987178 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:33.987240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:43:42.337497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:43:42.337549 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:03.987247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:33.987285 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:44:42.342364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:44:42.342423 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:03.987747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:33.987252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:45:42.348617 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:45:42.348658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:03.987292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:33.987236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:46:42.352633 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:46:42.352667 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:03.987314 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:33.987170 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:47:42.356371 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:47:42.356410 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:03.987163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:33.987383 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:48:42.360854 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:48:42.360891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:03.987197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:33.987249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:49:42.364513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:49:42.364551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:03.987164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:33.987262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:50:42.368906 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:50:42.368943 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:03.987155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:33.987244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:51:42.373693 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:51:42.373730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:03.987157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:33.987208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:52:42.378343 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:52:42.378487 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:03.987395 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:33.987184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:53:42.382110 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:53:42.382144 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:03.987216 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:33.987213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/05 04:54:42.386112 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:54:42.386158 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/05 04:55:03.987201 metrics.go:34: INFO No non-zero metrics in the last 30s