By type
2022/03/29 03:02:26.266916 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/29 03:02:26.266973 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/29 03:02:26.267073 logstash.go:90: INFO Max Retries set to: 3
2022/03/29 03:02:26.267192 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/29 03:02:26.267306 metrics.go:23: INFO Metrics logging every 30s
2022/03/29 03:02:26.269566 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-jkc2d
2022/03/29 03:02:26.269906 async.go:63: INFO Flush Interval set to: 1s
2022/03/29 03:02:26.269936 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/29 03:02:26.270389 beat.go:221: INFO filebeat start running.
2022/03/29 03:02:26.270477 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/29 03:02:26.273938 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/29 03:02:26.273997 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/29 03:02:26.274026 crawler.go:38: INFO Loading Prospectors: 1
2022/03/29 03:02:26.274128 registrar.go:236: INFO Starting Registrar
2022/03/29 03:02:26.274180 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/29 03:02:26.274190 sync.go:41: INFO Start sending events to output
2022/03/29 03:02:26.274281 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/29 03:02:26.274307 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/29 03:02:26.274421 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/29 03:02:46.276641 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/29 03:02:46.277819 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/29 03:02:46.277981 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/29 03:02:46.278007 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/29 03:02:46.278021 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/29 03:02:51.302969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:51.303004 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:52.306973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:52.307173 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:54.311543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:54.311732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:56.268341 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=76 registrar.writes=1
2022/03/29 03:02:58.318983 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:02:58.319013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:06.334615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:06.334647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:22.353234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:22.353279 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:26.267739 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:03:54.371334 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:54.371397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:03:56.267612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:04:26.267634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:04:54.389552 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:04:54.389587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:04:56.267666 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:05:26.267633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:05:54.410125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:05:54.410168 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:05:56.267590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:06:26.267626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:06:54.430771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:06:54.430816 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:06:56.267631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:07:26.267633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:07:51.291329 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/29 03:07:54.449095 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:07:54.449140 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:07:56.267635 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/29 03:08:26.267629 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:08:54.465406 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:08:54.465451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:08:56.267747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:09:26.267760 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:09:54.481720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:09:54.481766 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:09:56.267773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:10:26.269074 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:10:54.498851 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:10:54.498886 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:10:56.267625 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:11:26.267846 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:11:54.514563 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:11:54.514602 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:11:56.267766 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:12:26.267702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:12:54.532887 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:12:54.532919 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:12:56.267660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:13:26.267619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:13:54.556464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:13:54.556498 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:13:56.267591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:14:26.267579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:14:54.584591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:14:54.584635 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:14:56.267889 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:15:26.267709 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:15:54.602742 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:15:54.602776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:15:56.267619 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:16:26.267663 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:16:54.620198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:16:54.620579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:16:56.267699 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:17:26.267558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:17:54.638483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:17:54.638523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:17:56.267574 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:18:26.267716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:18:54.656190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:18:54.656243 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:18:56.267696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:19:26.267591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:19:54.673161 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:19:54.673214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:19:56.267565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:20:26.267600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:20:54.689702 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:20:54.689733 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:20:56.267635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:21:26.267586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:21:54.707729 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:21:54.707791 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:21:56.267649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:22:26.267612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:22:54.725507 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:22:54.725544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:22:56.267700 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:23:26.267711 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:23:54.742483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:23:54.742623 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:23:56.267620 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:24:26.267669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:24:54.760640 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:24:54.760681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:24:56.267686 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:25:26.267579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:25:54.780597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:25:54.780647 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:25:56.267597 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:26:26.267668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:26:54.797664 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:26:54.797698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:26:56.267626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:27:26.267778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:27:54.817155 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:27:54.817192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:27:56.267589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:28:26.267668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:28:54.835069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:28:54.835189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:28:56.267665 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:29:26.267570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:29:54.852411 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:29:54.852452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:29:56.267691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:30:26.267615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:30:54.871145 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:30:54.871192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:30:56.267532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:31:26.267610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:31:54.892955 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:31:54.892988 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:31:56.267697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:32:26.267656 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:32:54.915767 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:32:54.915800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:32:56.267626 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:33:26.267531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:33:54.933873 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:33:54.934009 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:33:56.267586 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:34:26.267608 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:34:54.950572 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:34:54.950604 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:34:56.267657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:35:26.267624 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:35:54.968288 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:35:54.968337 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:35:56.267653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:36:26.267557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:36:54.986197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:36:54.986229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:36:56.267604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:37:26.267885 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:37:55.005262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:37:55.005304 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:37:56.267650 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:38:26.267617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:38:55.029138 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:38:55.029203 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:38:56.267648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:39:26.267649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:39:55.046732 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:39:55.046765 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:39:56.267569 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:40:26.267688 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:40:55.064225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:40:55.064258 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:40:56.267716 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:41:26.267567 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:41:55.079789 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:41:55.079823 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:41:56.267570 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:42:26.267670 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:42:55.083035 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:42:55.083067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:42:56.268201 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:43:26.267680 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:43:55.086500 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:43:55.086547 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:43:56.268177 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:44:26.267582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:44:55.089513 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:44:55.089561 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:44:56.267568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:45:26.267668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:45:55.092843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:45:55.092881 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:45:56.267609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:46:26.267587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:46:55.096193 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:46:55.096227 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:46:56.267604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:47:26.267733 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:47:55.100391 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:47:55.100442 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:47:56.268401 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:48:26.268163 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:48:55.104389 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:48:55.104443 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:48:56.267755 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:49:26.267635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:49:55.108382 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:49:55.108414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:49:56.267710 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:50:26.267642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:50:55.112234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:50:55.112265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:50:56.267641 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:51:26.267929 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:51:55.115770 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:51:55.115825 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:51:56.275010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:52:26.267594 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:52:55.119066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:52:55.119110 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:52:56.267587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:53:26.267565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:53:55.122191 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:53:55.122229 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:53:56.267642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:54:26.267566 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:54:55.126150 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:54:55.126192 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:54:56.267612 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:55:26.267591 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:55:55.129718 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:55:55.129754 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:55:56.267683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:56:26.267675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:56:55.135898 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:56:55.135937 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:56:56.267622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:57:26.267588 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:57:55.144053 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:57:55.144450 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:57:56.267548 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:58:26.267595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:58:55.152244 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:58:55.152284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:58:56.267672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:59:26.267685 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 03:59:55.155618 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:59:55.155662 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 03:59:56.267638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:00:26.267600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:00:55.159656 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:00:55.159698 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:00:56.267559 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:01:26.267635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:01:55.163098 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:01:55.163226 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:01:56.267541 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:02:26.267636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:02:55.168671 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:02:55.168706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:02:56.267603 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:03:26.267679 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:03:55.172323 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:03:55.172353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:03:56.267500 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:04:26.267558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:04:55.175537 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:04:55.175573 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:04:56.267661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:05:26.268006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:05:55.179019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:05:55.179053 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:05:56.267712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:06:26.267535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:06:55.182845 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:06:55.182878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:06:56.267531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:07:26.267546 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:07:55.186179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:07:55.186217 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:07:56.267614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:08:26.267571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:08:55.189632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:08:55.189659 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:08:56.267735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:09:26.267894 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:09:55.193911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:09:55.193984 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:09:56.267714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:10:26.267653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:10:55.197395 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:10:55.197428 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:10:56.267690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:11:26.267582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:11:55.201543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:11:55.201624 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:11:56.267617 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:12:26.267606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:12:55.204631 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:12:55.204664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:12:56.267672 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:13:26.267615 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:13:55.208381 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:13:55.208431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:13:56.267571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:14:26.268557 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:14:55.215339 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:14:55.215376 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:14:56.267606 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:15:26.267632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:15:55.218582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:15:55.218625 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:15:56.267607 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:16:26.267747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:16:55.221588 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:16:55.221629 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:16:56.268010 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:17:26.268403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:17:55.224969 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:17:55.225278 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:17:56.267631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:18:26.267649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:18:55.229752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:18:55.229795 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:18:56.267683 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:19:26.267582 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:19:55.234223 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:19:55.234269 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:19:56.267664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:20:26.267751 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/29 04:20:55.238384 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:20:55.238454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/29 04:20:56.267644 metrics.go:34: INFO No non-zero metrics in the last 30s