Results

By type

          2022/03/09 16:21:15.361963 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/09 16:21:15.362048 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/09 16:21:15.362120 metrics.go:23: INFO Metrics logging every 30s
2022/03/09 16:21:15.362211 logstash.go:90: INFO Max Retries set to: 3
2022/03/09 16:21:15.362321 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/09 16:21:15.362495 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-d6pv5
2022/03/09 16:21:15.362874 async.go:63: INFO Flush Interval set to: 1s
2022/03/09 16:21:15.362900 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/09 16:21:15.363550 beat.go:221: INFO filebeat start running.
2022/03/09 16:21:15.363632 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/09 16:21:15.369649 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/09 16:21:15.369769 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/09 16:21:15.369830 crawler.go:38: INFO Loading Prospectors: 1
2022/03/09 16:21:15.370205 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/09 16:21:15.370377 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767 
2022/03/09 16:21:15.370417 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/09 16:21:15.370495 registrar.go:236: INFO Starting Registrar
2022/03/09 16:21:15.370558 sync.go:41: INFO Start sending events to output
2022/03/09 16:21:15.370621 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/09 16:21:35.375122 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/09 16:21:35.376702 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/09 16:21:35.377106 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/09 16:21:35.377533 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/09 16:21:35.377820 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/09 16:21:40.393870 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:40.394065 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:41.403232 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:41.403349 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:43.410464 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:43.410559 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:45.366168 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 registrar.writes=1
2022/03/09 16:21:47.429289 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:47.429360 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:55.442696 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:21:55.442776 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:11.484099 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:11.484208 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:15.362595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:22:43.506237 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:43.506289 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:22:45.362467 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:15.362621 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:23:43.523615 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:43.523650 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:23:45.362572 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:15.362492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:24:43.543801 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:43.543860 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:24:45.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:15.362527 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:25:43.565771 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:43.565834 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:25:45.362605 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:15.362471 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:26:40.400671 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/09 16:26:43.586535 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:43.586585 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:26:45.362883 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/09 16:27:15.364069 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:27:43.605843 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:43.605895 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:27:45.362394 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:15.362486 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:28:43.627800 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:43.627863 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:28:45.362505 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:15.362635 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:29:43.648067 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:43.648161 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:29:45.362449 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:15.362523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:30:43.665354 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:43.665404 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:30:45.362454 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:15.362432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:31:43.683303 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:43.683353 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:31:45.362531 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:15.362487 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:32:43.703490 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:43.703566 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:32:45.363240 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:15.362480 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:33:43.723142 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:43.723187 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:33:45.362495 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:15.362424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:34:43.742602 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:43.742661 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:34:45.362411 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:15.362595 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:35:43.762069 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:43.762132 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:35:45.365950 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:15.362529 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:36:43.786153 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:43.786206 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:36:45.362502 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:15.362526 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:37:43.807075 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:43.807134 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:37:45.362604 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:15.362407 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:38:43.827208 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:43.827255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:38:45.362472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:15.362463 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:39:43.849446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:43.849491 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:39:45.362492 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:15.362547 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:40:43.869911 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:43.870219 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:40:45.362664 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:15.362553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:41:43.889262 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:43.889310 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:41:45.362422 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:15.362472 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:42:43.908188 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:43.908237 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:42:45.362632 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:15.362432 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:43:43.927630 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:43.927680 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:43:45.363246 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:15.362543 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:44:43.954755 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:43.954794 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:44:45.362466 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:15.362424 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:45:43.971113 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:43.971169 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:45:45.362434 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:15.362974 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:46:43.988803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:43.988849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:46:45.362553 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:15.362573 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:47:44.012986 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:44.013050 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:47:45.362558 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:15.362618 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:48:44.031441 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:44.031496 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:48:45.362571 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:15.362523 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:49:44.054559 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:44.054639 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:49:45.362433 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:15.362474 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:50:44.083295 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:44.083519 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:50:45.362873 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:15.364047 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:51:44.104966 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:44.105043 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:51:45.362443 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:15.362497 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:52:44.123941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:44.124008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:52:45.362423 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:15.362414 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:53:44.143402 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:44.143452 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:53:45.362485 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:15.362459 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:54:44.162875 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:44.162929 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:54:45.362468 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:15.362651 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:55:44.186071 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:44.186137 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:55:45.362539 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:15.362698 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:56:44.205236 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:44.205284 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:56:45.362532 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:15.362900 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:57:44.242480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:44.242699 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:57:45.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:15.362473 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:58:44.259019 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:44.259056 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:58:45.363601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:15.362524 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 16:59:44.275178 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:44.275214 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 16:59:45.362437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:15.362499 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/09 17:00:44.293306 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:44.293365 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/09 17:00:45.362428 metrics.go:34: INFO No non-zero metrics in the last 30s