By type
2022/04/07 03:27:58.492991 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/07 03:27:58.493046 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/04/07 03:27:58.493156 logstash.go:90: INFO Max Retries set to: 3
2022/04/07 03:27:58.493251 outputs.go:108: INFO Activated logstash as output plugin.
2022/04/07 03:27:58.493409 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-rqqsz
2022/04/07 03:27:58.493637 async.go:63: INFO Flush Interval set to: 1s
2022/04/07 03:27:58.493660 async.go:64: INFO Max Bulk Size set to: 2048
2022/04/07 03:27:58.493269 metrics.go:23: INFO Metrics logging every 30s
2022/04/07 03:27:58.504215 beat.go:221: INFO filebeat start running.
2022/04/07 03:27:58.504419 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/04/07 03:27:58.511707 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/04/07 03:27:58.512312 registrar.go:123: INFO States Loaded from registrar: 0
2022/04/07 03:27:58.512400 crawler.go:38: INFO Loading Prospectors: 1
2022/04/07 03:27:58.512721 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/04/07 03:27:58.512848 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/04/07 03:27:58.514326 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/04/07 03:27:58.515912 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/04/07 03:27:58.516079 registrar.go:236: INFO Starting Registrar
2022/04/07 03:27:58.516140 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/04/07 03:27:58.516294 sync.go:41: INFO Start sending events to output
2022/04/07 03:27:58.516435 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/04/07 03:27:58.516601 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/04/07 03:27:58.517422 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/04/07 03:27:58.517763 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/04/07 03:28:03.565014 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:03.565096 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:04.571234 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:04.571293 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:06.580273 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:06.580320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:10.600478 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:10.600514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:18.607583 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:18.607643 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:28.494053 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/04/07 03:28:34.624283 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:34.624333 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:28:58.494060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:29:06.644000 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:29:06.644236 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:29:28.493937 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:29:58.494030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:30:06.664533 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:30:06.664586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:30:28.494059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:30:58.493947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:31:06.686924 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:31:06.687047 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:31:28.494278 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:31:58.494055 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:32:06.708194 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:32:06.708255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:32:28.494081 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:32:58.493957 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:33:03.544633 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/04/07 03:33:06.729189 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:33:06.729259 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:33:28.494060 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/04/07 03:33:58.494017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:34:06.752126 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:34:06.752166 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:34:28.494023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:34:58.494127 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:35:06.787571 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:35:06.787610 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:35:28.494249 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:35:58.493977 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:36:06.812088 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:36:06.812147 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:36:28.494023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:36:58.494015 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:37:06.835855 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:37:06.835924 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:37:28.493991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:37:58.494050 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:38:06.858705 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:38:06.858756 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:38:28.494159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:38:58.494068 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:39:06.881405 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:39:06.881460 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:39:28.494283 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:39:58.493994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:40:06.897497 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:40:06.897544 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:40:28.494008 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:40:58.493991 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:41:06.919370 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:41:06.919408 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:41:28.493967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:41:58.494052 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:42:06.937922 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:42:06.938063 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:42:28.493995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:42:58.493983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:43:06.956508 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:43:06.956681 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:43:28.494060 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:43:58.494017 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:44:06.975730 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:44:06.975812 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:44:28.494009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:44:58.493972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:45:06.995815 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:45:06.995857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:45:28.494031 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:45:58.494140 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:46:07.014128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:46:07.014169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:46:28.494030 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:46:58.494101 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:47:07.032114 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:47:07.032162 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:47:28.494002 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:47:58.494041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:48:07.051616 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:48:07.051689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:48:28.494016 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:48:58.494064 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:49:07.077979 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:49:07.078025 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:49:28.493947 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:49:58.493996 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:50:07.097838 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:50:07.097898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:50:28.493982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:50:58.494164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:51:07.123013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:51:07.123061 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:51:28.494136 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:51:58.494161 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:52:07.174914 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:52:07.174967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:52:28.493994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:52:58.494097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:53:07.221319 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:53:07.221369 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:53:28.495863 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:53:58.494362 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:54:07.255417 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:54:07.255473 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:54:28.494025 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:54:58.493981 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:55:07.285972 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:55:07.286021 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:55:28.493985 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:55:58.494292 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:56:07.305856 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:56:07.305905 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:56:28.494061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:56:58.494032 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:57:07.326534 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:57:07.326586 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:57:28.494118 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:57:58.494049 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:58:07.344818 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:58:07.344865 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:58:28.493990 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:58:58.494020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:59:07.368291 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:59:07.368357 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 03:59:28.493972 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 03:59:58.493943 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:00:07.390553 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:00:07.390607 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:00:28.493970 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:00:58.493980 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:01:07.414862 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:01:07.414916 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:01:28.493995 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:01:58.494089 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:02:07.433744 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:02:07.433784 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:02:28.494023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:02:58.494059 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:03:07.457660 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:03:07.457797 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:03:28.494189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:03:58.494095 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:04:07.479245 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:04:07.479322 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:04:28.494029 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:04:58.494003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:05:07.504013 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:05:07.504073 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:05:28.494061 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:05:58.494005 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:06:07.536476 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:06:07.536531 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:06:28.494000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:06:58.494037 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:07:07.556758 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:07:07.556819 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:07:28.493962 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:07:58.494000 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:08:07.576383 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:08:07.576431 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:08:28.494009 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:08:58.493982 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:09:07.593426 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:09:07.593470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:09:28.494051 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:09:58.493948 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:10:07.626038 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:10:07.626092 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:10:28.493979 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:10:58.493987 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:11:07.646646 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:11:07.646694 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:11:28.494020 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:11:58.494560 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:12:07.665621 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:12:07.665678 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:12:28.494026 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:12:58.494024 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:13:07.684424 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:13:07.684470 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:13:28.494237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:13:58.494288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:14:07.705785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:14:07.705857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:14:28.494093 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:14:58.494054 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:15:07.729186 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:15:07.729328 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:15:28.494023 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:15:58.494006 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:16:07.750217 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:16:07.750375 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:16:28.494480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:16:58.493994 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:17:07.768165 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:17:07.768204 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:17:28.494041 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:17:58.494003 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:18:07.787547 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:18:07.787600 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:18:28.493961 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:18:58.494047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:19:07.806398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:19:07.806454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:19:28.494007 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:19:58.493983 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:20:07.824008 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:20:07.824078 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:20:28.493967 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:20:58.494042 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/04/07 04:21:07.843190 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/04/07 04:21:07.843235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host