Results

By type

          2022/03/20 03:21:26.815086 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/20 03:21:26.815182 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/20 03:21:26.815368 logstash.go:90: INFO Max Retries set to: 3
2022/03/20 03:21:26.815514 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/20 03:21:26.815747 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-8vprp
2022/03/20 03:21:26.815872 metrics.go:23: INFO Metrics logging every 30s
2022/03/20 03:21:26.816166 async.go:63: INFO Flush Interval set to: 1s
2022/03/20 03:21:26.816207 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/20 03:21:26.817046 beat.go:221: INFO filebeat start running.
2022/03/20 03:21:26.817442 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/20 03:21:26.837582 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/20 03:21:26.837709 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/20 03:21:26.837941 crawler.go:38: INFO Loading Prospectors: 1
2022/03/20 03:21:26.837931 registrar.go:236: INFO Starting Registrar
2022/03/20 03:21:26.838005 sync.go:41: INFO Start sending events to output
2022/03/20 03:21:26.838198 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/20 03:21:26.838244 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/20 03:21:26.838431 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/20 03:21:26.838481 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/20 03:21:56.816796 metrics.go:39: INFO Non-zero metrics in the last 30s: registrar.writes=1
2022/03/20 03:21:56.849380 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/20 03:21:56.849652 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/20 03:21:56.849824 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/20 03:21:56.850113 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/20 03:21:56.850180 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/20 03:22:01.890408 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:01.890464 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:02.899927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:02.899996 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:04.934895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:04.934956 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:08.977331 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:08.977402 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:17.025274 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:17.025327 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:26.816624 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=72
2022/03/20 03:22:33.087799 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:33.087874 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:22:56.816565 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:23:05.139393 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:23:05.139445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:23:26.816406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:23:56.816389 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:24:05.257025 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:05.257099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:24:26.816372 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:24:56.820087 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:25:05.300634 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:25:05.300706 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:25:26.816440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:25:56.816246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:26:05.329775 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:26:05.329849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:26:26.816407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:26:56.819337 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:27:01.923270 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/20 03:27:05.360101 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:27:05.360166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:27:26.817526 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/20 03:27:56.816554 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:28:05.402427 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:28:05.402482 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:28:26.816507 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:28:56.817793 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:29:05.432540 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:29:05.432606 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:29:26.816283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:29:56.816236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:30:05.465006 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:30:05.465079 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:30:26.816319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:30:56.816642 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:31:05.490867 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:31:05.490916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:31:26.816402 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:31:56.816356 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:32:05.534849 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:32:05.534910 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:32:26.816236 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:32:56.816292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:33:05.559001 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:33:05.559073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:33:26.816648 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:33:56.816638 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:34:05.592829 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:34:05.592894 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:34:26.816373 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:34:56.817255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:35:05.617498 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:35:05.617551 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:35:26.816435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:35:56.816426 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:36:05.668180 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:36:05.668246 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:36:26.816419 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:36:56.816576 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:37:05.696179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:37:05.696244 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:37:26.816568 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:37:56.818616 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:38:05.725866 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:38:05.726065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:38:26.818036 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:38:56.818452 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:39:05.772216 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:39:05.772265 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:39:26.816431 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:39:56.816233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:40:05.844678 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:40:05.844739 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:40:26.816614 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:40:56.816712 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:41:05.897907 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:41:05.897982 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:41:26.816640 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:41:56.816768 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:42:05.981750 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:42:05.981809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:42:26.819455 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:42:56.820539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:43:06.067483 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:43:06.067523 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:43:26.816832 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:43:56.820042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:44:06.106474 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:44:06.106639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:44:26.816465 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:44:56.818220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:45:06.194895 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:45:06.194968 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:45:26.822587 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:45:56.816435 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:46:06.287135 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:46:06.287216 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:46:26.816403 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:46:56.824131 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:47:06.357082 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:47:06.357145 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:47:26.828083 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:47:56.816253 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:48:06.400198 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:48:06.400259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:48:26.816299 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:48:56.819899 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:49:06.545268 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:49:06.545350 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:49:26.819542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:49:56.816579 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:50:06.583511 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:50:06.583557 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:50:26.816316 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:50:56.821067 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:51:06.669003 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:51:06.669067 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:51:26.816325 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:51:56.816499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:52:06.704672 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:52:06.704716 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:52:26.820208 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:52:56.816503 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:53:06.767874 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:53:06.767960 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:53:26.816462 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:53:56.816789 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:54:06.802571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:54:06.803167 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:54:26.816319 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:54:56.818947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:55:06.826526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:55:06.826584 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:55:26.816535 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:55:56.816532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:56:06.852525 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:56:06.852607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:56:26.818237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:56:56.816295 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:57:06.897285 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:57:06.897335 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:57:26.816600 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:57:56.816691 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:58:06.936064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:58:06.936127 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:58:26.816406 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:58:56.816662 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:59:07.027824 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:59:07.027878 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 03:59:26.816246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 03:59:56.816623 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:00:07.056267 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:00:07.056344 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:00:26.817243 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:00:56.816246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:01:07.081493 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:01:07.081537 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:01:26.818530 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:01:56.816256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:02:07.114184 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:02:07.114249 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:02:26.816467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:02:56.816622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:03:07.142108 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:03:07.142171 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:03:26.816327 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:03:56.816420 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:04:07.176739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:04:07.176794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:04:26.816410 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:04:56.816488 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:05:07.206788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:05:07.206839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:05:26.816468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:05:56.817181 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:06:07.248197 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:06:07.248259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:06:26.816450 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:06:56.816971 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:07:07.286364 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:07:07.286433 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:07:26.816440 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:07:56.816552 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:08:07.318478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:08:07.318543 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:08:26.816415 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:08:56.816470 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:09:07.341440 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:09:07.341501 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:09:26.816542 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:09:56.816814 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/20 04:10:07.369266 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/20 04:10:07.369329 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host