By type
2022/03/12 03:00:14.761775 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/12 03:00:14.761844 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/12 03:00:14.761965 metrics.go:23: INFO Metrics logging every 30s
2022/03/12 03:00:14.762273 logstash.go:90: INFO Max Retries set to: 3
2022/03/12 03:00:14.762388 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/12 03:00:14.762572 publish.go:295: INFO Publisher name: onap-portal-sdk-5cddb5b4f8-stqqn
2022/03/12 03:00:14.762996 async.go:63: INFO Flush Interval set to: 1s
2022/03/12 03:00:14.763036 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/12 03:00:14.763920 beat.go:221: INFO filebeat start running.
2022/03/12 03:00:14.764004 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/12 03:00:14.769153 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/12 03:00:14.769222 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/12 03:00:14.769310 crawler.go:38: INFO Loading Prospectors: 1
2022/03/12 03:00:14.769382 registrar.go:236: INFO Starting Registrar
2022/03/12 03:00:14.769408 sync.go:41: INFO Start sending events to output
2022/03/12 03:00:14.769524 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/12 03:00:14.769609 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/12 03:00:14.769655 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/12 03:00:14.769684 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/12 03:00:34.772381 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/audit.log
2022/03/12 03:00:34.772547 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/metrics.log
2022/03/12 03:00:34.772791 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/debug.log
2022/03/12 03:00:34.773148 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/application.log
2022/03/12 03:00:34.774237 log.go:91: INFO Harvester started for file: /var/log/onap/onapsdk/error.log
2022/03/12 03:00:39.790968 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:39.791060 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:40.794937 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:40.794978 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:42.800116 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:42.800200 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:44.762460 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/12 03:00:46.806917 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:46.806988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:54.816104 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:00:54.816269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:10.839020 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:10.839081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:14.762559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:01:42.858973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:42.859080 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:01:44.762625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:02:14.762327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:02:42.879634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:02:42.879672 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:02:44.763407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:03:14.762352 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:03:42.899745 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:03:42.899806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:03:44.762263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:04:14.762253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:04:42.927501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:04:42.927534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:04:44.762259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:05:14.762291 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:05:39.784849 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/12 03:05:39.784865 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/error.log. Closing because close_inactive of 5m0s reached.
2022/03/12 03:05:39.784890 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/metrics.log. Closing because close_inactive of 5m0s reached.
2022/03/12 03:05:39.784903 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/debug.log. Closing because close_inactive of 5m0s reached.
2022/03/12 03:05:42.952125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:05:42.952374 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:05:44.762438 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/12 03:05:48.802665 log.go:116: INFO File is inactive: /var/log/onap/onapsdk/application.log. Closing because close_inactive of 5m0s reached.
2022/03/12 03:06:14.762249 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/12 03:06:42.974081 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:06:42.974142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:06:44.762328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:07:14.762278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:07:42.998061 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:07:42.998117 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:07:44.762237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:08:14.762220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:08:43.018119 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:08:43.018166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:08:44.762292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:09:14.762248 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:09:43.037452 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:09:43.037598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:09:44.762499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:10:14.762427 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:10:43.058270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:10:43.058325 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:10:44.762303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:11:14.762347 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:11:43.077328 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:11:43.077367 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:11:44.762254 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:12:14.762205 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:12:43.096939 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:12:43.097021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:12:44.762269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:13:14.762280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:13:43.118128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:13:43.118175 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:13:44.762346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:14:14.762328 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:14:43.138419 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:14:43.138456 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:14:44.762339 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:15:14.762368 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:15:43.156035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:15:43.156078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:15:44.762249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:16:14.762226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:16:43.175421 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:16:43.175464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:16:44.762419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:17:14.762306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:17:43.200209 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:17:43.200272 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:17:44.762304 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:18:14.762293 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:18:43.218405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:18:43.218454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:18:44.762338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:19:14.762230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:19:43.238479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:19:43.238508 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:19:44.762301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:20:14.762263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:20:43.264338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:20:43.264389 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:20:44.762261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:21:14.762322 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:21:43.281484 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:21:43.281524 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:21:44.762344 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:22:14.762202 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:22:43.299187 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:22:43.299241 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:22:44.762220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:23:14.762307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:23:43.318101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:23:43.318177 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:23:44.762313 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:24:14.762232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:24:43.339669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:24:43.339712 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:24:44.762292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:25:14.762281 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:25:43.359102 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:25:43.359159 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:25:44.762284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:26:14.762235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:26:43.379189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:26:43.379243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:26:44.762224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:27:14.762259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:27:43.398299 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:27:43.398349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:27:44.762230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:28:14.762280 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:28:43.417375 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:28:43.417435 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:28:44.762262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:29:14.762196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:29:43.438799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:29:43.438852 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:29:44.762736 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:30:14.762301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:30:43.459973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:30:43.460012 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:30:44.762213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:31:14.762842 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:31:43.478885 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:31:43.478938 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:31:44.762256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:32:14.762246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:32:43.502529 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:32:43.502588 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:32:44.762234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:33:14.762288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:33:43.522482 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:33:43.522523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:33:44.762225 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:34:14.762349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:34:43.542444 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:34:43.542494 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:34:44.762271 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:35:14.762297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:35:43.561158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:35:43.561534 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:35:44.762501 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:36:14.762289 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:36:43.583792 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:36:43.583828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:36:44.762321 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:37:14.762317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:37:43.602142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:37:43.602181 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:37:44.762214 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:38:14.762273 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:38:43.623656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:38:43.623710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:38:44.762430 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:39:14.762213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:39:43.642743 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:39:43.643065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:39:44.762207 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:40:14.762258 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:40:43.664519 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:40:43.664582 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:40:44.762270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:41:14.762196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:41:43.684706 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:41:43.684759 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:41:44.762405 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:42:14.762297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:42:43.703962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:42:43.703996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:42:44.762440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:43:14.762223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:43:43.725479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:43:43.725518 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:43:44.762624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:44:14.762435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:44:43.729183 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:44:43.729223 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:44:44.762243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:45:14.762380 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:45:43.737816 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:45:43.737848 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:45:44.762335 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:46:14.762197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:46:43.747560 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:46:43.747591 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:46:44.762224 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:47:14.762288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:47:43.754791 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:47:43.754863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:47:44.762473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:48:14.762360 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:48:43.764281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:48:43.764318 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:48:44.762343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:49:14.762233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:49:43.773213 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:49:43.773257 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:49:44.762498 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:50:14.762417 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:50:43.779853 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:50:43.779911 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:50:44.762251 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:51:14.762299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:51:43.787338 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:51:43.787392 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:51:44.762277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:52:14.762242 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:52:43.794485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:52:43.794529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:52:44.762336 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:53:14.762272 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:53:43.801280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:53:43.801311 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:53:44.762287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:54:14.762303 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:54:43.808781 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:54:43.808820 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:54:44.762445 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:55:14.762266 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:55:43.815225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:55:43.815255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:55:44.762270 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:56:14.762244 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:56:43.823383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:56:43.823417 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:56:44.762228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:57:14.762220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:57:43.831525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:57:43.831561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:57:44.762227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:58:14.762259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:58:43.839006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:58:43.839037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:58:44.762261 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:59:14.762243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 03:59:43.846094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:59:43.846142 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 03:59:44.762337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:00:14.762378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:00:43.852532 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:00:43.852567 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:00:44.762362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:01:14.763134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:01:43.859177 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:01:43.859211 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:01:44.762267 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:02:14.762342 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:02:43.865741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:02:43.865786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:02:44.762211 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:03:14.762308 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:03:43.875051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:03:43.875381 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:03:44.762236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:04:14.762233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:04:43.882669 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:04:43.882704 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:04:44.762222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:05:14.762239 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:05:43.890142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:05:43.890184 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:05:44.762277 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:06:14.762312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:06:43.898408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:06:43.898451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:06:44.762296 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:07:14.762377 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:07:43.905767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:07:43.905805 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:07:44.762307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:08:14.762301 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:08:43.914143 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:08:43.914179 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:08:44.762317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:09:14.762243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:09:43.921418 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:09:43.921446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:09:44.762222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:10:14.762290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:10:43.927995 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:10:43.928031 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:10:44.762315 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:11:14.762287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:11:43.935292 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:11:43.935446 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:11:44.762210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:12:14.762866 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:12:43.942990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:12:43.943044 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:12:44.762250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:13:14.762338 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:13:43.950768 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:13:43.950828 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:13:44.762235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:14:14.762262 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:14:43.958920 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:14:43.958956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:14:44.762263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:15:14.762325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:15:43.966804 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:15:43.966845 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:15:44.762204 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:16:14.762276 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:16:43.974681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:16:43.974733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:16:44.762538 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:17:14.762250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:17:43.981350 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:17:43.981390 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:17:44.762326 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:18:14.762265 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:18:43.990305 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:18:43.990350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:18:44.762290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:19:14.762692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:19:43.998264 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:19:43.998297 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:19:44.762349 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:20:14.762200 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:20:44.005681 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:20:44.005710 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:20:44.762286 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:21:14.762282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:21:44.015097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:21:44.015149 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:21:44.762487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:22:14.762259 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:22:44.022955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:22:44.023076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:22:44.762212 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:23:14.762375 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:23:44.030942 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:23:44.030977 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:23:44.762450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:24:14.762327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:24:44.041075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:24:44.041108 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:24:44.762279 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:25:14.762192 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:25:44.047820 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:25:44.047874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:25:44.762307 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:26:14.762317 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:26:44.054957 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:26:44.054992 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:26:44.762250 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:27:14.762284 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:27:44.062577 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:27:44.062629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:27:44.762410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:28:14.762423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:28:44.069688 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:28:44.070283 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:28:44.762290 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:29:14.762246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/12 04:29:44.079445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:29:44.079504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/12 04:29:44.762340 metrics.go:34: INFO No non-zero metrics in the last 30s