By type
2022/03/10 03:01:11.979706 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 03:01:11.979759 beat.go:186: INFO Setup Beat: filebeat; Version: 5.5.0
2022/03/10 03:01:11.979833 metrics.go:23: INFO Metrics logging every 30s
2022/03/10 03:01:11.979893 logstash.go:90: INFO Max Retries set to: 3
2022/03/10 03:01:11.979981 outputs.go:108: INFO Activated logstash as output plugin.
2022/03/10 03:01:11.980166 publish.go:295: INFO Publisher name: onap-portal-app-8648cbdd47-vvm9k
2022/03/10 03:01:11.980441 async.go:63: INFO Flush Interval set to: 1s
2022/03/10 03:01:11.980462 async.go:64: INFO Max Bulk Size set to: 2048
2022/03/10 03:01:11.982114 beat.go:221: INFO filebeat start running.
2022/03/10 03:01:11.982213 registrar.go:68: INFO No registry file found under: /usr/share/filebeat/data/registry. Creating a new registry file.
2022/03/10 03:01:11.994265 registrar.go:106: INFO Loading registrar data from /usr/share/filebeat/data/registry
2022/03/10 03:01:11.994509 registrar.go:123: INFO States Loaded from registrar: 0
2022/03/10 03:01:11.994693 crawler.go:38: INFO Loading Prospectors: 1
2022/03/10 03:01:11.995628 prospector_log.go:65: INFO Prospector with previous states loaded: 0
2022/03/10 03:01:11.996306 prospector.go:124: INFO Starting prospector of type: log; id: 12576369028753478767
2022/03/10 03:01:11.996463 crawler.go:58: INFO Loading and starting Prospectors completed. Enabled prospectors: 1
2022/03/10 03:01:11.996498 registrar.go:236: INFO Starting Registrar
2022/03/10 03:01:11.996836 sync.go:41: INFO Start sending events to output
2022/03/10 03:01:11.997027 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2022/03/10 03:01:22.000135 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/application.log
2022/03/10 03:01:22.000337 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/audit.log
2022/03/10 03:01:22.000525 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/error.log
2022/03/10 03:01:22.000650 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/debug.log
2022/03/10 03:01:22.000798 log.go:91: INFO Harvester started for file: /var/log/onap/onapportal/metrics.log
2022/03/10 03:01:27.021326 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:27.021372 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:28.025409 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:28.025445 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:30.031566 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:30.031599 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:34.039776 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:34.039806 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:41.982470 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/03/10 03:01:42.052158 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:42.052201 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:58.069753 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:01:58.069818 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:02:11.980156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:02:30.087956 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:02:30.088008 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:02:41.980297 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:03:11.980220 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:03:30.106953 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:03:30.106994 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:03:41.980378 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:04:11.980146 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:04:30.124281 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:04:30.124315 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:04:41.980171 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:05:11.980152 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:05:30.142562 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:05:30.142598 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:05:41.980188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:06:11.980601 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:06:27.022656 log.go:116: INFO File is inactive: /var/log/onap/onapportal/audit.log. Closing because close_inactive of 5m0s reached.
2022/03/10 03:06:30.163741 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:06:30.163779 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:06:41.980280 metrics.go:39: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=-1
2022/03/10 03:07:11.980150 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:07:30.184156 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:07:30.184196 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:07:41.980173 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:08:11.980333 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:08:30.202975 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:08:30.203156 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:08:41.980223 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:09:11.980129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:09:30.221582 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:09:30.221627 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:09:41.980156 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:10:11.980110 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:10:30.267965 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:10:30.268013 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:10:41.980169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:11:11.980437 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:11:30.286040 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:11:30.286076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:11:41.980134 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:12:11.980148 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:12:30.314941 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:12:30.314985 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:12:41.980121 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:13:11.980194 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:13:30.331485 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:13:30.331529 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:13:41.980190 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:14:11.980129 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:14:30.350270 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:14:30.350320 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:14:41.980111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:15:11.980167 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:15:30.369488 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:15:30.369689 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:15:41.980105 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:16:11.980197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:16:30.388261 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:16:30.388354 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:16:41.980141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:11.980157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:17:30.406480 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:17:30.406947 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:17:41.980160 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:11.980111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:18:30.423765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:18:30.423809 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:18:41.980158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:11.980169 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:19:30.443064 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:19:30.443102 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:19:41.980218 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:11.980306 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:20:30.462826 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:20:30.462932 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:20:41.980097 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:11.980154 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:21:30.481258 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:21:30.481292 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:21:41.980235 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:11.980109 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:22:30.504460 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:22:30.504514 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:22:41.980141 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:11.980107 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:23:30.521308 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:23:30.521358 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:23:41.980143 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:11.980138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:24:30.539363 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:24:30.539397 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:24:41.980226 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:11.980257 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:25:30.557396 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:25:30.557434 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:25:41.980197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:11.980157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:26:30.576201 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:26:30.576239 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:26:41.980288 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:11.980198 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:27:30.594876 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:27:30.594921 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:27:41.980230 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:11.980142 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:28:30.613466 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:28:30.613511 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:28:41.980149 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:11.980188 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:29:30.629834 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:29:30.629875 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:29:41.980100 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:11.980197 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:30:30.647580 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:30:30.647615 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:30:41.980158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:11.980185 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:31:30.665195 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:31:30.665235 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:31:41.980157 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:11.980111 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:32:30.684012 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:32:30.684076 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:32:41.980119 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:11.980164 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:33:30.702765 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:33:30.702800 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:33:41.980189 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:11.980138 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:34:30.722927 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:34:30.722970 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:34:41.980209 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:11.980274 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:35:30.745412 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:35:30.745451 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:35:41.980153 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:11.980159 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:36:30.763625 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:36:30.763669 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:36:41.980255 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:11.982012 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:37:30.781045 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:37:30.781105 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:37:41.980264 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:11.980158 metrics.go:34: INFO No non-zero metrics in the last 30s
2022/03/10 03:38:30.798896 tcp.go:26: WARN DNS lookup failure "log-ls": lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:38:30.798939 single.go:140: ERR Connecting error publishing events (retrying): lookup log-ls on 169.254.25.10:53: no such host
2022/03/10 03:38:41.980181 metrics.go:34: INFO No non-zero metrics in the last 30s