By type
2022/03/10 14:48:32.192302 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/10 14:48:32.192353 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 14:48:32.192447 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 14:48:32.192542 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 14:48:32.192686 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-gx8hj
2022/03/10 14:48:32.192840 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 14:48:32.192947 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 14:48:32.192966 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 14:48:32.193927 beat.go:221: INFO filebeat start running.
2022/03/10 14:48:32.194107 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 14:48:32.201390 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 14:48:32.201577 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 14:48:32.201848 registrar.go:236: INFO Starting Registrar
2022/03/10 14:48:32.201878 sync.go:41: INFO Start sending events to output
2022/03/10 14:48:32.202234 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 14:48:32.201767 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 14:48:32.205731 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 14:48:32.205929 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/10 14:48:32.205986 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 14:48:42.210766 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/10 14:48:42.210993 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/10 14:48:42.211070 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/10 14:48:42.211152 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/10 14:48:42.211209 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/10 14:48:47.227921 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:47.227967 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:48.232987 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:48.233035 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:50.238788 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:50.238872 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:54.252214 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:48:54.252255 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:02.193371 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=5 filebeat.harvester.running=5 filebeat.harvester.started=5 libbeat.publisher.published_events=76 registrar.writes=1
2022/03/10 14:49:02.264051 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:02.264099 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:18.287094 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:18.287148 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:32.193367 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:49:50.308398 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:49:50.308454 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:50:02.193333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:50:32.193222 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:50:50.328365 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:50:50.328414 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:51:02.193164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:51:32.193610 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:51:50.346446 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:51:50.346553 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:52:02.193287 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:52:32.193210 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:52:50.367133 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:52:50.367225 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:53:02.193320 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:53:32.193622 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:53:47.226843 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/10 14:53:50.387445 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:53:50.387515 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:54:02.193099 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/10 14:54:32.193580 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:54:50.409074 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:54:50.409115 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:55:02.193167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:55:32.193247 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:55:50.430720 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:55:50.430786 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:56:02.193223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:56:32.193184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:56:50.452128 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:56:50.452732 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:57:02.193169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:57:32.193107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:57:50.472785 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:57:50.472870 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:58:02.193130 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:58:32.193227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:58:50.490341 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:58:50.490379 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:59:02.197086 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:59:32.196628 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 14:59:50.507620 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 14:59:50.507657 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:00:02.193125 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:00:32.193343 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:00:50.529754 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:00:50.529839 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:01:02.193230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:01:32.193269 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:01:50.547861 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:01:50.547898 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:02:02.193174 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:02:32.193151 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:02:50.567692 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:02:50.567762 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:03:02.193312 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:03:32.193232 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:03:50.585719 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:03:50.585772 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:04:02.193229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:04:32.193142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:04:50.607526 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:04:50.607579 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:05:02.193184 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:05:32.193147 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:05:50.626179 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:05:50.626230 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:06:02.193188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:06:32.193148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:06:50.647687 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:06:50.647730 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:07:02.193229 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:07:32.193228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:07:50.674062 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:07:50.674105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:08:02.193238 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:08:32.193194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:08:50.694990 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:08:50.695037 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:09:02.193263 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:09:32.193255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:09:50.714044 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:09:50.714355 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:10:02.193252 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:10:32.193196 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:10:50.733632 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:10:50.733683 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:11:02.193227 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:11:32.193168 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:11:50.753694 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:11:50.753749 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:12:02.193213 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:12:32.193223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:12:50.772175 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:12:50.772221 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:13:02.193157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:13:32.193203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:13:50.791806 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:13:50.791849 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:14:02.193237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:14:32.193256 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:14:50.810320 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:14:50.810378 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:15:02.193103 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:15:32.193166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:15:50.827591 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:15:50.827637 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:16:02.193176 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:16:32.193233 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:16:50.845151 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:16:50.845201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:17:02.193237 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:17:32.193203 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:17:50.866281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:17:50.866345 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:18:02.193282 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:18:32.193155 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:18:50.890803 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:18:50.890857 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:19:02.193166 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:19:32.193234 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:19:50.918512 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:19:50.918563 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:20:02.193219 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:20:32.193228 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 15:20:50.938739 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:20:50.938989 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 15:21:02.193090 metrics.go:34: INFO No non-zero metrics in the last 30s