elasticsearch 将我用filebeat上传的内容发送到索引

我创建了一个索引映射，就像这个，现在我将使用filebeat向Elasticsearch发送一个json文件，如何确保配置我的filebeat.yml将信息发送到我刚刚创建的这个新索引映射

索引映射：

PUT _template/packets
{
  "index_patterns": "packets-*",
  "mappings": {
    "pcap_file": {
      "dynamic": "false",
      "properties": {
        "timestamp": {
          "type": "date"
        },
        "layers": {
          "properties": {
            "frame": {
              "properties": {
                "frame_frame_len": {
                  "type": "long"
                },
                "frame_frame_protocols": {
                  "type": "keyword"
                }
              }
            },
            "ip": {
              "properties": {
                "ip_ip_src": {
                  "type": "ip"
                },
                "ip_ip_dst": {
                  "type": "ip"
                }
              }
            },
            "udp": {
              "properties": {
                "udp_udp_srcport": {
                  "type": "integer"
                },
                "udp_udp_dstport": {
                  "type": "integer"
                }
              }
            }
          }
        }
      }
    }
  }
}

my filebeat.yml：

###################### Filebeat Configuration Example 
###################### #########################

# This file is an example configuration file highlighting only the most common
# options. The filebeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/filebeat/index.html

# For more available modules and options, please see the filebeat.reference.yml sample
# configuration file.

#=========================== Filebeat prospectors =============================

filebeat.prospectors:

# Each - is a prospector. Most options can be set at the prospector level, so
# you can use different prospectors for various configurations.
# Below are the prospector specific configurations.

- input_type: log
  paths:
    - "/home/manuel/packets.json"
  document_type: "pcap_file"
  json.keys_under_root: true
processors:
 - drop_event:
     when:
       equals:
         index._type: "pcap_file"
enabled: false
# Change to true to enable this prospector configuration.
  # Paths that should be crawled and fetched. Glob based paths.
  # paths:
    #- /var/log/*.log
    #- c:\programdata\elasticsearch\logs\*

  # Exclude lines. A list of regular expressions to match. It drops the lines that are
  # matching any regular expression from the list.
  #exclude_lines: ['^DBG']

  # Include lines. A list of regular expressions to match. It exports the lines that are
  # matching any regular expression from the list.
  #include_lines: ['^ERR', '^WARN']

  # Exclude files. A list of regular expressions to match. Filebeat drops the files that
  # are matching any regular expression from the list. By default, no files are dropped.
  #exclude_files: ['.gz$']

  # Optional additional fields. These fields can be freely picked
  # to add additional information to the crawled log files for filtering
  #fields:
  #  level: debug
  #  review: 1

  ### Multiline options

  # Mutiline can be used for log messages spanning multiple lines. This is common
  # for Java Stack Traces or C-Line Continuation

  # The regexp Pattern that has to be matched. The example pattern matches all lines starting with [
  #multiline.pattern: ^\[

  # Defines if the pattern set under pattern should be negated or not. Default is false.
  #multiline.negate: false

  # Match can be set to "after" or "before". It is used to define if lines should be append to a pattern
  # that was (not) matched before or after or as long as a pattern is not matched based on negate.
  # Note: After is the equivalent to previous and before is the equivalent to to next in Logstash
  #multiline.match: after
#============================= Filebeat modules ===============================

filebeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

#==================== Elasticsearch template setting ==========================

setup.template.settings:
  index.number_of_shards: 3
  #index.codec: best_compression
  #_source.enabled: false
setup.template.name: "packets-*"
setup.template.pattern: "packets-*"
#================================ General =====================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
#  env: staging


#============================== Dashboards =====================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here, or by using the `-setup` CLI flag or the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

#============================== Kibana =====================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  host: "https://this_is_hidden_and_changed_for_stackoverflow"

#============================= Elastic Cloud ==================================

# These settings simplify using filebeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
cloud.id: "this_is_hidden_and_changed_for_stackoverflow=="

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
cloud.auth: "elastic:this_is_hidden_and_changed_for_stackoverflow"

#================================ Outputs =====================================

# Configure what output to use when sending the data collected by the beat.

#-------------------------- Elasticsearch output ------------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["https://this_is_hidden_and_changed_for_stackoverflow"]
  index: "packets"
  template.enabled: false

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  username: "elastic"
  password: "this_is_hidden_and_changed_for_stackoverflow"
#----------------------------- Logstash output --------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

#================================ Logging =====================================

---

我想确保我将使用filebeat上传的内容将正确提交到我之前设置的Elasticsearch映射，非常感谢我的朋友们

如果您可以直接从filebeat写入ES，那么这是我不知道的功能

我使用Logstash如下所示：

~/logs/*.log -> Filebeat --> LogStash --> ElasticSearch

在所有服务节点上安装FileBeat，在监控节点上安装Logstash，并让Logstash与ES对话。其更清晰的分离（Filebeat只将原始数据发送到主机/端口）和LogStash具有许多解析功能（如果愿意，可以为数据编写转换），您需要在ES中填充合理的索引

---

你使用的是索引模板，对吗？？？（否则您将在ES集群中浪费大量空间）

确保

filebeat.yml

中的模板名称与您在ES中创建的模板名称匹配。您发布的文件显示：

setup.template.name:“数据包-*”

请注意，该值以

-*

结尾。但是模板的名称是

数据包

，没有

-*

。将该行更改为：

---

setup.template.name:“packets”

谢谢用户1016765的回答，你问我是否使用索引模板，我的回答是，如果我使用，我不太理解，我不理解如何使用模板，我的filebeat.yml和我在Kibana中输入的内容正是我在问题中发布的内容，不知道我在做什么。尽管如此，我还是能够使用Filebeat（我没有使用Logstash）将一些数据上传到Elasticsearch，并在Kibana中将其可视化，但对我来说，这似乎是原始数据。你能给我解释一下如何使用模板吗？：）我非常感激我正在安装Logstash顺便说一句，如果你能帮我，我会非常感激。而且，我所做的是用tshark捕获网络数据，结果是一个.json文件，我非常感激你能帮我使用Logstash或其他工具，谢谢你根据Filebeat 6.4 docs，可以从beats向ES发送数据（不使用Logstash作为中介），参考：

~/logs/*.log -> Filebeat --> LogStash --> ElasticSearch