How to Search an Index?

I am new to Opensearch and trying to query my new index but I don’t get results.

Versions 3.9

Describe the issue: Don’t see data

Configuration: Forward zeek data via rsyslogd

Relevant Logs or Screenshots:

@huaraz Could you run the command below in DevTools?

GET _cat/indices

Do you see any zeek indices there? If yes, do you see any documents there?

GET <zeek_index>/_count

How do you ingest Zeek logs into an OpenSearch cluster?

I get this output

#curl --cacert /opt/opensearch/config/root-ca.pem -u admin   'https://localhost:9200/_cat/indices'
Enter host password for user 'admin':
green  open .plugins-search-relevance-experiment 2UHSKQi9SP-g9M40J_TQDw 1 0        0 0    208b    208b
green  open security-auditlog-2026.10.29         qkavHoHDTbukWLbvP1iJzw 1 0       70 0 276.4kb 276.4kb
green  open .ql-datasources                      -NPsxrNnRym1vkV4NpBn5w 1 0        0 0    208b    208b
green  open top_queries-2026.11.04-89254         Mi6b48pjRQGYsOorX8-yoA 1 0     4630 0   2.1mb   2.1mb
green  open .opendistro-reports-definitions      eOVD8fYFQUaeqVrXvcXGsA 1 0        0 0    208b    208b
green  open .opendistro_security                 Zw6kqGd_TSKgYH1Jy4jWeQ 1 0        9 2  90.9kb  90.9kb
green  open .opendistro-reports-instances        aexbp9BDSWyTtyah4iX2YQ 1 0        0 0    208b    208b
green  open security-auditlog-2026.10.30         1Pj1b98EQLW7Dhw2L7yD7g 1 0        1 0  18.4kb  18.4kb
green  open top_queries-2026.11.10-89281         GAxuYmXDTVCiOmHJ4bawqg 1 0       23 7     1mb     1mb
green  open security-auditlog-2026.11.03         8SGwuUbHThaoUJHtuIRy7A 1 0        4 0    75kb    75kb
green  open security-auditlog-2026.10.16         VX4oGAy8SMexkZXx5pWYnA 1 0        5 0  80.2kb  80.2kb
green  open security-auditlog-2026.10.31         6fE7-BLpT6Onayh82Fzg_w 1 0        2 0  34.7kb  34.7kb
green  open security-auditlog-2026.11.02         Uv-qSOzdTU-ZEwwIR2feqA 1 0       78 0 177.7kb 177.7kb
green  open security-auditlog-2026.11.01         MjQHE_IgTG2B9SKfSce6Ow 1 0       25 0  71.8kb  71.8kb
green  open security-auditlog-2026.10.18         kyvHiARNS5Sb23zX429lcw 1 0        1 0  17.1kb  17.1kb
green  open security-auditlog-2026.10.17         0EhBZrSFRLev6uLN6lo2tA 1 0       13 0 104.7kb 104.7kb
green  open .kibana_92668751_admin_1             PH3_EZOQSbqPlprYmsJiaw 1 0        1 0   5.9kb   5.9kb
yellow open zeek-logs                            w_m-uXYRR7qzN4Tdsmparw 1 1     4902 0   2.3mb   2.3mb
green  open .kibana_92668751_admin_3             RfTQWJ2aQSKsVGHivA4AUQ 1 0        6 0  40.7kb  40.7kb
green  open .kibana_92668751_admin_2             7j7fb0J2RouzM3aH61yX-Q 1 0        3 0  17.9kb  17.9kb
yellow open suricata-logs                        7l3LNvNoROCL7FnVXCZO4g 1 1 61035719 0     9gb     9gb
green  open .kibana_2                            vnq5aUmZRty_qB6o4OMpcQ 1 0        0 0    208b    208b
green  open .kibana_1                            90RETlRLTFO80VcewOJ3bg 1 0        0 0    208b    208b
green  open .kibana_3                            f0-G_2AjRkWm6NdACZjC0Q 1 0        5 0  78.2kb  78.2kb
green  open .plugins-ml-config                   coMYR3tpRO-qM_IS7_DfHw 1 0        1 0   4.6kb   4.6kb
green  open top_queries-2026.11.03-89253         v056-WgWR_a2MoAcwVBI-w 1 0     4789 0   2.2mb   2.2mb
green  open security-auditlog-2026.10.25         lyOzebm6QmeqtJQSNjHA4g 1 0    15732 0     4mb     4mb
green  open security-auditlog-2026.10.24         GOhZKkCpTjmljP_u8wHZiw 1 0     1259 0   1.6mb   1.6mb
green  open .opendistro-job-scheduler-lock       ExFHSJkTSp-UtKTrsf_7Nw 1 0        1 0  12.9kb  12.9kb
green  open security-auditlog-2026.10.26         vGHfyZc7TWOUMBkb9TFFOQ 1 0        1 0  16.3kb  16.3kb
green  open security-auditlog-2026.11.10         lyfo3MKuRTWiYkfUCR6iZg 1 0       18 0   134kb   134kb
#curl --cacert /opt/opensearch/config/root-ca.pem -u admin   'https://localhost:9200/zeek-logs/_count'
Enter host password for user 'admin':
{"count":4902,"\_shards":{"total":1,"successful":1,"skipped":0,"failed":0}}

You could use opensearch-dashboards’ dev_tools, it allows you to easily target your cluster
Here is how you can get 10 random documents:

GET zeek-logs/_search
{
  "query": {
    "match_all": {}
  }
}

With curl, it would be:
curl -sSu admin https://localhost:9200/zeek-logs/_search -H 'content-type: application/json' -d '{"query": {"match_all": {}}}'

@huaraz I’ve just tested Zeek with OpenSearch. I had no issues ingesting and reading thrrough Discovery the Zeek’s logs in OS.

I ingested Zeek’s logs into the OpenSearch index through Fluent Bit.

Could you check your timestamps? How do you ingest your Zeek’s logs

I use rsyslog and can see the files are read and I connect to localhost:9200.

lsof -n -P -p 662947
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
rsyslogd 662947 root cwd DIR 8,3 4096 2 /
rsyslogd 662947 root rtd DIR 8,3 4096 2 /
rsyslogd 662947 root txt REG 8,3 817760 434346 /usr/sbin/rsyslogd
rsyslogd 662947 root mem REG 8,3 133384 403738 /usr/lib64/libgcc_s.so.1
rsyslogd 662947 root mem REG 8,3 788704 397583 /usr/lib64/libpcre2-8.so.0.14.0
rsyslogd 662947 root mem REG 8,3 264456 392351 /usr/lib64/libselinux.so.1
rsyslogd 662947 root mem REG 8,3 79512 397251 /usr/lib64/libresolv.so.2
rsyslogd 662947 root mem REG 8,3 67560 403696 /usr/lib64/libkeyutils.so.1.10
rsyslogd 662947 root mem REG 8,3 198632 405883 /usr/lib64/libbrotlicommon.so.1.1.0
rsyslogd 662947 root mem REG 8,3 67824 398337 /usr/lib64/libkrb5support.so.0.1
rsyslogd 662947 root mem REG 8,3 67552 405675 /usr/lib64/libcom_err.so.2.1
rsyslogd 662947 root mem REG 8,3 133176 436719 /usr/lib64/libk5crypto.so.3.1
rsyslogd 662947 root mem REG 8,3 857936 436729 /usr/lib64/libkrb5.so.3.3
rsyslogd 662947 root mem REG 8,3 67528 418683 /usr/lib64/libjitterentropy.so.3.6.3
rsyslogd 662947 root mem REG 8,3 133904 400846 /usr/lib64/libsasl2.so.3.0.0
rsyslogd 662947 root mem REG 8,3 1968184 399293 /usr/lib64/libunistring.so.5.2.0
rsyslogd 662947 root mem REG 8,3 67480 408114 /usr/lib64/libbrotlidec.so.1.1.0
rsyslogd 662947 root mem REG 8,3 723008 418660 /usr/lib64/libzstd.so.1.5.7
rsyslogd 662947 root mem REG 8,3 397560 436715 /usr/lib64/libgssapi_krb5.so.2.2
rsyslogd 662947 root mem REG 8,3 5844152 395473 /usr/lib64/libcrypto.so.3.5.0
rsyslogd 662947 root mem REG 8,3 1064928 436702 /usr/lib64/libssl.so.3.5.0
rsyslogd 662947 root mem REG 8,3 133016 434778 /usr/lib64/libpsl.so.5.3.5
rsyslogd 662947 root mem REG 8,3 531720 436746 /usr/lib64/libssh.so.4.10.5
rsyslogd 662947 root mem REG 8,3 67808 401626 /usr/lib64/liblber.so.2.0.200
rsyslogd 662947 root mem REG 8,3 461832 423188 /usr/lib64/libldap.so.2.0.200
rsyslogd 662947 root mem REG 8,3 133088 406756 /usr/lib64/libidn2.so.0.4.0
rsyslogd 662947 root mem REG 8,3 198696 434794 /usr/lib64/libnghttp2.so.14.29.3
rsyslogd 662947 root mem REG 8,3 987568 397085 /usr/lib64/libcurl.so.4.8.0
rsyslogd 662947 root mem REG 8,3 68600 391691 /usr/lib64/rsyslog/omelasticsearch.so
rsyslogd 662947 root mem REG 8,3 69408 398674 /usr/lib64/rsyslog/imfile.so
rsyslogd 662947 root mem REG 8,3 76096 397207 /usr/lib64/libnss_compat.so.2
rsyslogd 662947 root mem REG 8,3 68744 398677 /usr/lib64/rsyslog/imklog.so
rsyslogd 662947 root mem REG 8,3 69392 398685 /usr/lib64/rsyslog/imuxsock.so
rsyslogd 662947 root mem REG 8,3 68424 398679 /usr/lib64/rsyslog/immark.so
rsyslogd 662947 root mem REG 8,3 68264 398687 /usr/lib64/rsyslog/lmnet.so
rsyslogd 662947 root mem REG 8,3 67672 397609 /usr/lib64/libcap.so.2.78
rsyslogd 662947 root mem REG 8,3 2128224 397160 /usr/lib64/libc.so.6
rsyslogd 662947 root mem REG 8,3 67704 397914 /usr/lib64/libuuid.so.1.3.0
rsyslogd 662947 root mem REG 8,3 1186328 422965 /usr/lib64/libsystemd.so.0.40.0
rsyslogd 662947 root mem REG 8,3 67712 423547 /usr/lib64/libfastjson.so.4.3.0
rsyslogd 662947 root mem REG 8,3 67480 423552 /usr/lib64/libestr.so.0.0.0
rsyslogd 662947 root mem REG 8,3 694792 397192 /usr/lib64/libm.so.6
rsyslogd 662947 root mem REG 8,3 133288 936485 /usr/lib64/zlib-ng-compat/libz.so.1.3.1.zlib-ng
rsyslogd 662947 root mem REG 8,3 233944 397122 /usr/lib/ld-linux-aarch64.so.1
rsyslogd 662947 root 0r CHR 1,3 0t0 4 /dev/null
rsyslogd 662947 root 1w CHR 1,3 0t0 4 /dev/null
rsyslogd 662947 root 2w CHR 1,3 0t0 4 /dev/null
rsyslogd 662947 root 3u unix 0xffff0573c8b6bb80 0t0 6085 /run/systemd/journal/syslog type=DGRAM (UNCONNECTED)
rsyslogd 662947 root 4r CHR 1,9 0t0 8 /dev/urandom
rsyslogd 662947 root 5r REG 0,25 0 4026532000 /proc/kmsg
rsyslogd 662947 root 6r REG 8,4 2273627958 3932452 /data/suricata/logs/eve.json
rsyslogd 662947 root 7r a_inode 0,16 0 59 inotify
rsyslogd 662947 root 8r DIR 8,3 4096 2 /
rsyslogd 662947 root 9r DIR 8,4 4096 2 /data
rsyslogd 662947 root 10r DIR 8,4 4096 3932161 /data/suricata
rsyslogd 662947 root 11r DIR 8,4 4096 3932162 /data/suricata/logs
rsyslogd 662947 root 12r REG 8,4 2273627958 3932452 /data/suricata/logs/eve.json
rsyslogd 662947 root 13w REG 8,3 2983471 1003 /var/log/messages
rsyslogd 662947 root 14u unix 0xffff0573c416d500 0t0 38920542 type=DGRAM (CONNECTED)
rsyslogd 662947 root 15w REG 8,3 1197885 23565 /var/log/localmessages
rsyslogd 662947 root 16r DIR 8,4 4096 4587521 /data/zeek
rsyslogd 662947 root 17r DIR 8,4 4096 4587522 /data/zeek/logs
rsyslogd 662947 root 18r DIR 8,4 4096 4606697 /data/zeek/spool/zeek
rsyslogd 662947 root 19r REG 8,4 42846 4607317 /data/zeek/spool/zeek/stats.log
rsyslogd 662947 root 20r DIR 8,4 4096 4587523 /data/zeek/spool
rsyslogd 662947 root 21r DIR 8,4 4096 4587536 /data/zeek/spool/tmp/post-terminate-standalone-2026-11-14-13-52-23-1047099
rsyslogd 662947 root 22r REG 8,4 19 4606159 /data/zeek/spool/zeek/stderr.log
rsyslogd 662947 root 23r REG 8,4 42846 4607317 /data/zeek/spool/zeek/stats.log
rsyslogd 662947 root 24r REG 8,4 19 4606159 /data/zeek/spool/zeek/stderr.log
rsyslogd 662947 root 25u a_inode 0,16 0 59 [eventfd:45]
rsyslogd 662947 root 26r REG 8,4 198507 4607175 /data/zeek/spool/zeek/quic.log
rsyslogd 662947 root 27r REG 8,4 922 4607628 /data/zeek/spool/zeek/known_hosts.log
rsyslogd 662947 root 28r REG 8,4 198507 4607175 /data/zeek/spool/zeek/quic.log
rsyslogd 662947 root 29r REG 8,4 7087146 4605789 /data/zeek/spool/zeek/files.log
rsyslogd 662947 root 30r REG 8,4 204 4587592 /data/zeek/spool/zeek/stdout.log
rsyslogd 662947 root 31r REG 8,4 7087146 4605789 /data/zeek/spool/zeek/files.log
rsyslogd 662947 root 32r REG 8,4 55930 4605556 /data/zeek/spool/zeek/weird.log
rsyslogd 662947 root 33r REG 8,4 2413690 4607665 /data/zeek/spool/zeek/ssl.log
rsyslogd 662947 root 34r REG 8,4 2413690 4607665 /data/zeek/spool/zeek/ssl.log
rsyslogd 662947 root 35r REG 8,4 1185580 4607357 /data/zeek/spool/zeek/ntp.log
rsyslogd 662947 root 36r REG 8,4 204 4587592 /data/zeek/spool/zeek/stdout.log
rsyslogd 662947 root 37r REG 8,4 1185580 4607357 /data/zeek/spool/zeek/ntp.log
rsyslogd 662947 root 38r REG 8,4 55930 4605556 /data/zeek/spool/zeek/weird.log
rsyslogd 662947 root 39r REG 8,4 71468 4607257 /data/zeek/spool/zeek/x509.log
rsyslogd 662947 root 40r REG 8,4 71468 4607257 /data/zeek/spool/zeek/x509.log
rsyslogd 662947 root 41r REG 8,4 7040779 4607629 /data/zeek/spool/zeek/http.log
rsyslogd 662947 root 42r REG 8,4 7040779 4607629 /data/zeek/spool/zeek/http.log
rsyslogd 662947 root 43r REG 8,4 3179 4607047 /data/zeek/spool/zeek/capture_loss.log
rsyslogd 662947 root 44r REG 8,4 3179 4607047 /data/zeek/spool/zeek/capture_loss.log
rsyslogd 662947 root 45r REG 8,4 7893295 4607669 /data/zeek/spool/zeek/syslog.log
rsyslogd 662947 root 46r REG 8,4 3917 4606872 /data/zeek/spool/zeek/analyzer.log
rsyslogd 662947 root 47r REG 8,4 7893295 4607669 /data/zeek/spool/zeek/syslog.log
rsyslogd 662947 root 48r REG 8,4 40816040 4607627 /data/zeek/spool/zeek/dns.log
rsyslogd 662947 root 49r REG 8,4 3917 4606872 /data/zeek/spool/zeek/analyzer.log
rsyslogd 662947 root 50r REG 8,4 40816040 4607627 /data/zeek/spool/zeek/dns.log
rsyslogd 662947 root 51r REG 8,4 2717252 4607136 /data/zeek/spool/zeek/snmp.log
rsyslogd 662947 root 52r REG 8,4 2717252 4607136 /data/zeek/spool/zeek/snmp.log
rsyslogd 662947 root 53r REG 8,4 72358 4607208 /data/zeek/spool/zeek/notice.log
rsyslogd 662947 root 54u a_inode 0,16 0 59 [eventfd:52]
rsyslogd 662947 root 55r REG 8,4 29833927 4607265 /data/zeek/spool/zeek/conn.log
rsyslogd 662947 root 56r REG 8,4 72358 4607208 /data/zeek/spool/zeek/notice.log
rsyslogd 662947 root 57r REG 8,4 40955 4607209 /data/zeek/spool/zeek/ocsp.log
rsyslogd 662947 root 58r REG 8,4 29833927 4607265 /data/zeek/spool/zeek/conn.log
rsyslogd 662947 root 59u IPv6 60063227 0t0 TCP [::1]:58956->[::1]:9200 (ESTABLISHED)
rsyslogd 662947 root 60r REG 8,4 826 4607231 /data/zeek/spool/zeek/tunnel.log
rsyslogd 662947 root 61u IPv6 71402255 0t0 TCP [::1]:45432->[::1]:9200 (ESTABLISHED)
rsyslogd 662947 root 62r REG 8,4 2714 4607657 /data/zeek/spool/zeek/known_services.log
rsyslogd 662947 root 63r REG 8,4 922 4607628 /data/zeek/spool/zeek/known_hosts.log
rsyslogd 662947 root 64r REG 8,4 2714 4607657 /data/zeek/spool/zeek/known_services.log
rsyslogd 662947 root 65u IPv6 71697690 0t0 TCP [::1]:34270->[::1]:9200 (ESTABLISHED)
rsyslogd 662947 root 66u a_inode 0,16 0 59 [eventfd:46]
rsyslogd 662947 root 67r REG 8,4 6392 4607354 /data/zeek/spool/zeek/software.log
rsyslogd 662947 root 68r REG 8,4 6392 4607354 /data/zeek/spool/zeek/software.log
rsyslogd 662947 root 69r REG 8,4 40955 4607209 /data/zeek/spool/zeek/ocsp.log
rsyslogd 662947 root 70r REG 8,4 90 4607626 /data/zeek/spool/zeek/packet_filter.log
rsyslogd 662947 root 71r REG 8,4 90 4607626 /data/zeek/spool/zeek/packet_filter.log
rsyslogd 662947 root 72r REG 8,4 42034 4607608 /data/zeek/spool/zeek/loaded_scripts.log
rsyslogd 662947 root 73r REG 8,4 42034 4607608 /data/zeek/spool/zeek/loaded_scripts.log
rsyslogd 662947 root 74r REG 8,4 826 4607231 /data/zeek/spool/zeek/tunnel.log
rsyslogd 662947 root 75u a_inode 0,16 0 59 [eventfd:47]
rsyslogd 662947 root 76r REG 8,4 4063 4607271 /data/zeek/spool/zeek/dhcp.log
rsyslogd 662947 root 77u IPv6 63815138 0t0 TCP [::1]:52694->[::1]:9200 (ESTABLISHED)
rsyslogd 662947 root 78r REG 8,4 4063 4607271 /data/zeek/spool/zeek/dhcp.log
rsyslogd 662947 root 79r REG 8,4 814 4606190 /data/zeek/spool/zeek/pe.log
rsyslogd 662947 root 80r REG 8,4 814 4606190 /data/zeek/spool/zeek/pe.log
rsyslogd 662947 root 85w REG 8,3 2277782 58053 /var/log/NetworkManager
rsyslogd 662947 root 100u IPv6 64048709 0t0 TCP [::1]:49808->[::1]:9200 (ESTABLISHED)
rsyslogd 662947 root 103u FIFO 0,6 0t0 708 /dev/xconsole
rsyslogd 662947 root 104w CHR 4,10 0t0 28 /dev/tty10
rsyslogd 662947 root 105w REG 8,3 773386 52 /var/log/warn

But when I look at the data I see just data from 30th Oct i.e. from 2 weeks ago and I created a lot more data since. How can I check where it goes. I have 17G on disk in opensearch.

curl -skSu admin https://localhost:9200/suricata-logs/_search -H ‘content-type: application/json’ -d ‘{“query”: {“match_all”: {}}}’ | jq
Enter host password for user ‘admin’:
{
“took”: 3606,
“timed_out”: false,
“_shards”: {
“total”: 1,
“successful”: 1,
“skipped”: 0,
“failed”: 0
},
“hits”: {
“total”: {
“value”: 10000,
“relation”: “gte”
},
“max_score”: 1.0,
“hits”: [
{
“_index”: “suricata-logs”,
“_id”: “59aqjKEBg8-BEsQSJ9Fj”,
“_score”: 1.0,
“_source”: {
“timestamp”: “2026-10-30T11:55:23.858280+0000”,
“in_iface”: “eth0”,
“event_type”: “alert”,
“pkt_src”: “wire/pcap”,
“alert”: {
“action”: “allowed”,
“gid”: 1,
“signature_id”: 2200121,
“rev”: 1,
“signature”: “SURICATA Ethertype unknown”,
“category”: “Generic Protocol Command Decode”,
“severity”: 3
}
}
},

I also get also with large count but only 1 success.

# curl --cacert /opt/opensearch/config/root-ca.pem -u admin ‘https://localhost:9200/zeek-logs/_count’

Enter host password for user ‘admin’:
{“count”:7611,“_shards”:{“total”:1,“successful”:1,“skipped”:0,“failed”:0}}

# curl --cacert /opt/opensearch/config/root-ca.pem -u admin ‘https://localhost:9200/zeek0/suricata-logs/_count’
Enter host password for user ‘admin’:
{“count”:82033117,“_shards”:{“total”:1,“successful”:1,“skipped”:0,“failed”:0}}

I use this rsyslog config

template(name="zeekJson" type="list") {
    property(name="msg")
}

ruleset(name="zeekToOpenSearch") {
    action(
        type="omelasticsearch"
        server="localhost"
        serverport="9200"
        usehttps="on"
        uid="rsyslog_zeek"
        pwd="XXX"
        tls.cacert="/opt/opensearch/config/root-ca.pem"
        searchType=""
        searchIndex="zeek-logs"
        template="zeekJson"
        bulkmode="on"
        action.resumeretrycount="-1"
    )
}

input(
    type="imfile"
    File="/data/zeek/logs/current/\*.log"
    Tag="zeek:"
    Facility="local0"
    Severity="info"
    addMetadata="on"
    PersistStateInterval="100"
    Ruleset="zeekToOpenSearch"
)

#Send each original EVE JSON line as the OpenSearch document.

#Do not use format="jsonf": that would escape the JSON into a string.

template(name="suricataJson" type="list") {
    property(name="msg")
}

#Keep these events out of rsyslog's default rules, which may write

#local0.info messages to /var/log/messages.

ruleset(name="suricataToOpenSearch") {
    action(
        type="omelasticsearch"
        server="localhost"
        serverport="9200"
        usehttps="on"
        uid="rsyslog_suricata"
        pwd="XXX"
        tls.cacert="/opt/opensearch/config/root-ca.pem"
        searchType=""
        searchIndex="suricata-logs"
        template="suricataJson"
        bulkmode="on"
        action.resumeretrycount="-1"
    )
}

input(
    type="imfile"
    File="/data/suricata/logs/eve.json"
    Tag="suricata:"
    Facility="local0"
    Severity="info"
    addMetadata="on"
    PersistStateInterval="100"
    Ruleset="suricataToOpenSearch"
)

please make some effort to get formatting in your posts

Hi @huaraz. The ‘successful’ value refers to the number of indices. You’ve targeted only one index in your query and your query output confirms that index has been read/accessed successfully.

The count returns the number of documents in that index.

@huaraz I’ve tested Zeek logs with your approach.

The main difference between your deployment and mine is how Zeek logs are ingested into OpenSearch.

In your setup, rsyslog forwards the raw Zeek JSON logs without transforming the fields. In my setup, Filebeat processes the logs and normalizes fields such as ts into a proper timestamp format.

        "_index": "zeek-logs",
        "_id": "uc2D7qEBbd9VkAkkeo60",
        "_score": 1,
        "_source": {
          "ts": 1795002890.282505,
          "uid": "CeauXp1JRYxjGSIKD9",
          "id.orig_h": "10.150.186.14",
          "id.orig_p": 51112,
          "id.resp_h": "209.85.202.147",
          "id.resp_p": 443,
          "version": "1",
          "client_initial_dcid": "50218261caa5b3ff",
          "client_scid": "",
          "server_scid": "f0218261caa5b3ff",
          "server_name": "t2.gstatic.com",
          "client_protocol": "h3",
          "history": "IIISZZiiiIiishoooHOOOioO"
        }
      }

As a result, your deployment requires an OpenSearch index template to map the ts field as a date (epoch_second), whereas my Filebeat pipeline handles this conversion automatically.

PUT _index_template/zeek-template
{
  "index_patterns": ["zeek-*"],
  "priority": 200,
  "template": {
    "mappings": {
      "properties": {
        "ts": {
          "type": "date",
          "format": "epoch_second"
        }
      }
    }
  }
}

You’ve stated that this worked for you before. Did you change anything in the ts field mapping? How did you handle timestamp before?