By type
2022/04/17 03:15:16.084173 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/04/17 03:15:16.084260 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/17 03:15:16.084303 metrics.go:23: INFO Metrics logging every 30s
2022/04/17 03:15:16.084428 logstash.go:90: INFO Max Retries set to: 3
2022/04/17 03:15:16.084610 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/17 03:15:16.084815 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-8dstz
2022/04/17 03:15:16.085145 async.go:63: INFO Flush Interval set to: 1s
2022/04/17 03:15:16.085179 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/17 03:15:16.086025 beat.go:221: INFO filebeat start running.
2022/04/17 03:15:16.086174 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/17 03:15:16.093473 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/17 03:15:16.093595 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/17 03:15:16.093656 crawler.go:38: INFO Loading Prospectors: 1
2022/04/17 03:15:16.094027 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/17 03:15:16.094209 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/17 03:15:16.094249 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/17 03:15:16.094275 registrar.go:236: INFO Starting Registrar
2022/04/17 03:15:16.094326 sync.go:41: INFO Start sending events to output
2022/04/17 03:15:16.094380 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/17 03:15:36.097326 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/17 03:15:36.097505 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/17 03:15:36.097602 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/17 03:15:36.097869 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/17 03:15:36.097965 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/17 03:15:41.121621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:41.121675 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:42.125549 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:42.125607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:44.129604 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:44.129648 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:46.086111 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=70 registrar.writes=1
2022/04/17 03:15:48.148109 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:48.148170 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:56.158597 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:15:56.158658 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:12.184926 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:12.185114 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:16.085434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:16:44.208416 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:44.208460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:16:46.084628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:17:16.084747 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:17:44.226623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:17:44.226664 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:17:46.084778 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:18:16.084724 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:18:44.244962 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:18:44.245013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:18:46.084673 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:19:16.084689 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:19:44.264479 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:19:44.264537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:19:46.084674 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:20:16.084725 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:20:41.113322 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/17 03:20:44.288755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:20:44.288811 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:20:46.084700 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/17 03:21:16.084825 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:21:44.308038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:21:44.308082 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:21:46.084575 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:22:16.084684 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:22:44.327996 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:22:44.328063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:22:46.084727 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:23:16.084696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:23:44.353066 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:23:44.353143 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:23:46.084740 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:24:16.084675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:24:44.372801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:24:44.372865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:24:46.084660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:25:16.084820 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:25:44.393596 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:25:44.393653 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:25:46.087037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:26:16.085770 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:26:44.413036 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:26:44.413081 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:26:46.084837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:27:16.084692 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:27:44.432157 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:27:44.432201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:27:46.084732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:28:16.084721 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:28:44.453363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:28:44.453424 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:28:46.084926 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:29:16.084633 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:29:44.472125 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:29:44.472189 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:29:46.084675 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:30:16.084871 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:30:44.494543 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:30:44.494587 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:30:46.084649 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:31:16.084732 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:31:44.514080 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:31:44.514616 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:31:46.084593 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:32:16.084634 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:32:44.537440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:32:44.537504 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:32:46.084660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:33:16.084676 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:33:44.555747 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:33:44.555802 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:33:46.084730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:34:16.084753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:34:44.576871 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:34:44.576932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:34:46.084773 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:35:16.084759 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:35:44.598579 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:35:44.598642 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:35:46.084901 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:36:16.084668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:36:44.617623 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:36:44.617676 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:36:46.084678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:37:16.084576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:37:44.637274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:37:44.637467 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:37:46.084741 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:38:16.085019 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:38:44.657363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:38:44.657402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:38:46.084714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:39:16.084697 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:39:44.675153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:39:44.675213 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:39:46.084815 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:40:16.084600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:40:44.699280 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:40:44.699329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:40:46.084669 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:41:16.084668 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:41:44.718663 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:41:44.718724 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:41:46.084746 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:42:16.084738 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:42:44.738511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:42:44.738545 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:42:46.084791 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:43:16.085015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:43:44.755503 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:43:44.755559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:43:46.084660 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:44:16.084967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:44:44.774011 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:44:44.774064 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:44:46.084790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:45:16.084800 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:45:44.792778 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:45:44.792835 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:45:46.084609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:46:16.084661 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:46:44.812041 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:46:44.812083 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:46:46.084614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:47:16.084826 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:47:44.831823 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:47:44.831891 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:47:46.084667 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:48:16.084690 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:48:44.851982 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:48:44.852034 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:48:46.084701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:49:16.084691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:49:44.872225 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:49:44.872267 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:49:46.084743 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:50:16.084695 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:50:44.889761 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:50:44.889800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:50:46.084609 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:51:16.084714 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:51:44.907667 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:51:44.907709 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:51:46.084590 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:52:16.084678 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:52:44.928298 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:52:44.928342 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:52:46.084702 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:53:16.084657 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:53:44.946752 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:53:44.946991 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:53:46.084790 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:54:16.085094 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:54:44.965097 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:54:44.965156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:54:46.084653 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:55:16.084779 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:55:44.985916 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:55:44.985973 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:55:46.084696 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:56:16.084782 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:56:45.004346 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:56:45.004380 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:56:46.084785 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:57:16.085022 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:57:45.024255 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:57:45.024468 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:57:46.084837 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:58:16.084753 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:58:45.042774 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:58:45.043006 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:58:46.084636 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:59:16.084731 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 03:59:45.060043 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:59:45.060085 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 03:59:46.084631 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:00:16.084763 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:00:45.083468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:00:45.083541 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:00:46.084808 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:01:16.084623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:01:45.100973 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:01:45.101013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:01:46.084589 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:02:16.085346 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:02:45.121468 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:02:45.121512 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:02:46.084635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:03:16.084787 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:03:45.140501 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:03:45.140544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:03:46.084701 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:04:16.084730 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:04:45.159494 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:04:45.159557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:04:46.084735 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:05:16.084664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/17 04:05:45.178426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:05:45.178483 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/17 04:05:46.084566 metrics.go:34: INFO No non-zero metrics in the last 30s