Hello community, I have setup Graylog version 6.0.6+4aa664f with Opensearch v2.16.0 on Ubuntu. i followed the official documentation and installed Graylog, then i integrated it with Wazuh indexer which runs on Opensearch version 2.8.0. I’m getting the following error when I go to the search tab: [image] The last week i changed the data types of a few data fields over Wazuh and those were with data type “conflict”, after a few days i saw it was affecting my Graylog server with this error. So i changed back those data types, reindexed all my indices or removed unused and removed the “conflict” data type from the wazuh indexer. After removing and reindexing all my indices i reinstalled the Garylog to see the error again. I have checked previos questions about this subject but non was working for me. No logs have been sent yet to the Graylog all i did is to integrate the Wazuh indexer. What can i do from this point? i have no more ideas how to continue. Any help will be appreciated. My Graylog config file: ############################ # GRAYLOG CONFIGURATION FILE ############################ # # This is the Graylog configuration file. The file has to use ISO 8859-1/Latin-1 character encoding. # Characters that cannot be directly represented in this encoding can be written using Unicode escapes # as defined in https://docs.oracle.com/javase/specs/jls/se8/html/jls-3.html#jls-3.3, using the \u prefix. # For example, \u002c. # # * Entries are generally expected to be a single line of the form, one of the following: # # propertyName=propertyValue # propertyName:propertyValue # # * White space that appears between the property name and property value is ignored, # so the following are equivalent: # # name=Stephen # name = Stephen # # * White space at the beginning of the line is also ignored. # # * Lines that start with the comment characters ! or # are ignored. Blank lines are also ignored. # # * The property value is generally terminated by the end of the line. White space following the # property value is not ignored, and is treated as part of the property value. # # * A property value can span several lines if each line is terminated by a backslash (‘\’) character. # For example: # # targetCities=\ # Detroit,\ # Chicago,\ # Los Angeles # # This is equivalent to targetCities=Detroit,Chicago,Los Angeles (white space at the beginning of lines is ignored). # # * The characters newline, carriage return, and tab can be inserted with characters \n, \r, and \t, respectively. # # * The backslash character must be escaped as a double backslash. For example: # # path=c:\\docs\\doc1 # # If you are running more than one instances of Graylog server you have to select one of these # instances as leader. The leader will perform some periodical tasks that non-leaders won't perform. is_leader = true # The auto-generated node ID will be stored in this file and read after restarts. It is a good idea # to use an absolute file path here if you are starting Graylog server from init scripts or similar. node_id_file = /etc/graylog/server/node-id # You MUST set a secret to secure/pepper the stored user passwords here. Use at least 64 characters. # Generate one by using for example: pwgen -N 1 -s 96 # ATTENTION: This value must be the same on all Graylog nodes in the cluster. # Changing this value after installation will render all user sessions and encrypted values in the database invalid. (e.g. encrypted access tokens) password_secret = ************ # The default root user is named 'admin' #root_username = admin # You MUST specify a hash password for the root user (which you only need to initially set up the # system and in case you lose connectivity to your authentication backend) # This password cannot be changed using the API or via the web interface. If you need to change it, # modify it in this file. # Create one by using for example: echo -n yourpassword | shasum -a 256 # and put the resulting hash value into the following line root_password_sha2 = ********************* # The email address of the root user. # Default is empty #root_email = "" # The time zone setting of the root user. See http://www.joda.org/joda-time/timezones.html for a list of valid time zones. # Default is UTC #root_timezone = UTC # Set the bin directory here (relative or absolute) # This directory contains binaries that are used by the Graylog server. # Default: bin bin_dir = /usr/share/graylog-server/bin # Set the data directory here (relative or absolute) # This directory is used to store Graylog server state. data_dir = /var/lib/graylog-server # Set plugin directory here (relative or absolute) plugin_dir = /usr/share/graylog-server/plugin ############### # HTTP settings ############### #### HTTP bind address # # The network interface used by the Graylog HTTP interface. # # This network interface must be accessible by all Graylog nodes in the cluster and by all clients # using the Graylog web interface. # # If the port is omitted, Graylog will use port 9000 by default. # # Default: 127.0.0.1:9000 http_bind_address = 0.0.0.0:9000 #http_bind_address = [2001:db8::1]:9000 #### HTTP publish URI # # The HTTP URI of this Graylog node which is used to communicate with the other Graylog nodes in the cluster and by all # clients using the Graylog web interface. # # The URI will be published in the cluster discovery APIs, so that other Graylog nodes will be able to find and connect to this Graylog node. # # This configuration setting has to be used if this Graylog node is available on another network interface than $http_bind_address, # for example if the machine has multiple network interfaces or is behind a NAT gateway. # # If $http_bind_address contains a wildcard IPv4 address (0.0.0.0), the first non-loopback IPv4 address of this machine will be used. # This configuration setting *must not* contain a wildcard address! # # Default: http://$http_bind_address/ #http_publish_uri = http://192.168.1.1:9000/ #### External Graylog URI # # The public URI of Graylog which will be used by the Graylog web interface to communicate with the Graylog REST API. # # The external Graylog URI usually has to be specified, if Graylog is running behind a reverse proxy or load-balancer # and it will be used to generate URLs addressing entities in the Graylog REST API (see $http_bind_address). # # When using Graylog Collector, this URI will be used to receive heartbeat messages and must be accessible for all collectors. # # This setting can be overridden on a per-request basis with the "X-Graylog-Server-URL" HTTP request header. # # Default: $http_publish_uri #http_external_uri = #### Enable CORS headers for HTTP interface # # This allows browsers to make Cross-Origin requests from any origin. # This is disabled for security reasons and typically only needed if running graylog # with a separate server for frontend development. # # Default: false #http_enable_cors = false #### Enable GZIP support for HTTP interface # # This compresses API responses and therefore helps to reduce # overall round trip times. This is enabled by default. Uncomment the next line to disable it. #http_enable_gzip = false # The maximum size of the HTTP request headers in bytes. #http_max_header_size = 8192 # The size of the thread pool used exclusively for serving the HTTP interface. #http_thread_pool_size = 64 ################ # HTTPS settings ################ #### Enable HTTPS support for the HTTP interface # # This secures the communication with the HTTP interface with TLS to prevent request forgery and eavesdropping. # # Default: false #http_enable_tls = true # The X.509 certificate chain file in PEM format to use for securing the HTTP interface. #http_tls_cert_file = /path/to/graylog.crt # The PKCS#8 private key file in PEM format to use for securing the HTTP interface. #http_tls_key_file = /path/to/graylog.key # The password to unlock the private key used for securing the HTTP interface. #http_tls_key_password = secret # If set to "true", Graylog will periodically investigate indices to figure out which fields are used in which streams. # It will make field list in Graylog interface show only fields used in selected streams, but can decrease system performance, # especially on systems with great number of streams and fields. stream_aware_field_types=false # Comma separated list of trusted proxies that are allowed to set the client address with X-Forwarded-For # header. May be subnets, or hosts. #trusted_proxies = 127.0.0.1/32, 0:0:0:0:0:0:0:1/128 # List of Elasticsearch hosts Graylog should connect to. # Need to be specified as a comma-separated list of valid URIs for the http ports of your elasticsearch nodes. # If one or more of your elasticsearch hosts require authentication, include the credentials in each node URI that # requires authentication. # # Default: http://127.0.0.1:9200 elasticsearch_hosts = https://graylog:****@*.*.*.*:9200 # Maximum number of attempts to connect to elasticsearch on boot for the version probe. # # Default: 0, retry indefinitely with the given delay until a connection could be established #elasticsearch_version_probe_attempts = 5 # Waiting time in between connection attempts for elasticsearch_version_probe_attempts # # Default: 5s #elasticsearch_version_probe_delay = 5s # Maximum amount of time to wait for successful connection to Elasticsearch HTTP port. # # Default: 10 Seconds #elasticsearch_connect_timeout = 10s # Maximum amount of time to wait for reading back a response from an Elasticsearch server. # (e. g. during search, index creation, or index time-range calculations) # # Default: 60 seconds #elasticsearch_socket_timeout = 60s # Maximum idle time for an Elasticsearch connection. If this is exceeded, this connection will # be tore down. # # Default: inf #elasticsearch_idle_timeout = -1s # Maximum number of total connections to Elasticsearch. # # Default: 200 #elasticsearch_max_total_connections = 200 # Maximum number of total connections per Elasticsearch route (normally this means per # elasticsearch server). # # Default: 20 #elasticsearch_max_total_connections_per_route = 20 # Maximum number of times Graylog will retry failed requests to Elasticsearch. # # Default: 2 #elasticsearch_max_retries = 2 # Enable automatic Elasticsearch node discovery through Nodes Info, # see https://www.elastic.co/guide/en/elasticsearch/reference/5.4/cluster-nodes-info.html # # WARNING: Automatic node discovery does not work if Elasticsearch requires authentication, e. g. with Shield. # # Default: false #elasticsearch_discovery_enabled = true # Filter for including/excluding Elasticsearch nodes in discovery according to their custom attributes, # see https://www.elastic.co/guide/en/elasticsearch/reference/5.4/cluster.html#cluster-nodes # # Default: empty #elasticsearch_discovery_filter = rack:42 # Frequency of the Elasticsearch node discovery. # # Default: 30s # elasticsearch_discovery_frequency = 30s # Set the default scheme when connecting to Elasticsearch discovered nodes # # Default: http (available options: http, https) #elasticsearch_discovery_default_scheme = http # Enable payload compression for Elasticsearch requests. # # Default: false #elasticsearch_compression_enabled = true # Enable use of "Expect: 100-continue" Header for Elasticsearch index requests. # If this is disabled, Graylog cannot properly handle HTTP 413 Request Entity Too Large errors. # # Default: true #elasticsearch_use_expect_continue = true # Graylog uses Index Sets to manage settings for groups of indices. The default options for index sets are configurable # for each index set in Graylog under System > Configuration > Index Set Defaults. # The following settings are used to initialize in-database defaults on the first Graylog server startup. # Specify these values if you want the Graylog server and indices to start with specific settings. # The prefix for the Default Graylog index set. # elasticsearch_index_prefix = graylogo # The name of the index template for the Default Graylog index set. # #elasticsearch_template_name = graylog-internal # The prefix for the for graylog event indices. # #default_events_index_prefix = gl-events # The prefix for graylog system event indices. # #default_system_events_index_prefix = gl-system-events # Analyzer (tokenizer) to use for message and full_message field. The "standard" filter usually is a good idea. # All supported analyzers are: standard, simple, whitespace, stop, keyword, pattern, language, snowball, custom # Elasticsearch documentation: https://www.elastic.co/guide/en/elasticsearch/reference/2.3/analysis.html # Note that this setting only takes effect on newly created indices. # #elasticsearch_analyzer = standard # How many Elasticsearch shards and replicas should be used per index? # #elasticsearch_shards = 1 #elasticsearch_replicas = 0 # Maximum number of attempts to connect to datanode on boot. # Default: 0, retry indefinitely with the given delay until a connection could be established #datanode_startup_connection_attempts = 5 # Waiting time in between connection attempts for datanode_startup_connection_attempts # # Default: 5s # datanode_startup_connection_delay = 5s # Disable the optimization of Elasticsearch indices after index cycling. This may take some load from Elasticsearch # on heavily used systems with large indices, but it will decrease search performance. The default is to optimize # cycled indices. # #disable_index_optimization = true # Optimize the index down to <= index_optimization_max_num_segments. A higher number may take some load from Elasticsearch # on heavily used systems with large indices, but it will decrease search performance. The default is 1. # #index_optimization_max_num_segments = 1 # Time interval to trigger a full refresh of the index field types for all indexes. This will query ES for all indexes # and populate any missing field type information to the database. # #index_field_type_periodical_full_refresh_interval = 5m # You can configure the default strategy used to determine when to rotate the currently active write index. # Multiple rotation strategies are supported, the default being "time-size-optimizing": # - "time-size-optimizing" tries to rotate daily, while focussing on optimal sized shards. # The global default values can be configured with # "time_size_optimizing_retention_min_lifetime" and "time_size_optimizing_retention_max_lifetime". # - "count" of messages per index, use elasticsearch_max_docs_per_index below to configure # - "size" per index, use elasticsearch_max_size_per_index below to configure # - "time" interval between index rotations, use elasticsearch_max_time_per_index to configure # A strategy may be disabled by specifying the optional enabled_index_rotation_strategies list and excluding that strategy. # #enabled_index_rotation_strategies = count,size,time,time-size-optimizing # The default index rotation strategy to use. #rotation_strategy = time-size-optimizing # (Approximate) maximum number of documents in an Elasticsearch index before a new index # is being created, also see no_retention and elasticsearch_max_number_of_indices. # Configure this if you used 'rotation_strategy = count' above. # #elasticsearch_max_docs_per_index = 20000000 # (Approximate) maximum size in bytes per Elasticsearch index on disk before a new index is being created, also see # no_retention and elasticsearch_max_number_of_indices. Default is 30GB. # Configure this if you used 'rotation_strategy = size' above. # #elasticsearch_max_size_per_index = 32212254720 # (Approximate) maximum time before a new Elasticsearch index is being created, also see # no_retention and elasticsearch_max_number_of_indices. Default is 1 day. # Configure this if you used 'rotation_strategy = time' above. # Please note that this rotation period does not look at the time specified in the received messages, but is # using the real clock value to decide when to rotate the index! # Specify the time using a duration and a suffix indicating which unit you want: # 1w = 1 week # 1d = 1 day # 12h = 12 hours # Permitted suffixes are: d for day, h for hour, m for minute, s for second. # #elasticsearch_max_time_per_index = 1d # Controls whether empty indices are rotated. Only applies to the "time" rotation_strategy. # #elasticsearch_rotate_empty_index_set=false # Provides a hard upper limit for the retention period of any index set at configuration time. # # This setting is used to validate the value a user chooses for the maximum number of retained indexes, when configuring # an index set. However, it is only in effect, when a time-based rotation strategy is chosen. # # If a rotation strategy other than time-based is selected and/or no value is provided for this setting, no upper limit # for index retention will be enforced. This is also the default. # Default: none #max_index_retention_period = P90d # Optional upper bound on elasticsearch_max_time_per_index # #elasticsearch_max_write_index_age = 1d # Disable message retention on this node, i. e. disable Elasticsearch index rotation. #no_retention = false # Decide what happens with the oldest indices when the maximum number of indices is reached. # The following strategies are available: # - delete # Deletes the index completely (Default) # - close # Closes the index and hides it from the system. Can be re-opened later. # #retention_strategy = delete # This configuration list limits the retention strategies available for user configuration via the UI # The following strategies can be disabled: # - delete # Deletes the index completely (Default) # - close # Closes the index and hides it from the system. Can be re-opened later. # - none # No operation is performed. The index stays open. (Not recommended) # WARNING: At least one strategy must be enabled. Be careful when extending this list on existing installations! disabled_retention_strategies = none,close # How many indices do you want to keep for the delete and close retention types? # #elasticsearch_max_number_of_indices = 20 # Disable checking the version of Elasticsearch for being compatible with this Graylog release. # WARNING: Using Graylog with unsupported and untested versions of Elasticsearch may lead to data loss! # #elasticsearch_disable_version_check = true # Do you want to allow searches with leading wildcards? This can be extremely resource hungry and should only # be enabled with care. See also: https://docs.graylog.org/docs/query-language allow_leading_wildcard_searches = false # Do you want to allow searches to be highlighted? Depending on the size of your messages this can be memory hungry and # should only be enabled after making sure your Elasticsearch cluster has enough memory. allow_highlighting = false # Sets field value suggestion mode. The possible values are: # 1. "off" - field value suggestions are turned off # 2. "textual_only" - field values are suggested only for textual fields # 3. "on" (default) - field values are suggested for all field types, even the types where suggestions are inefficient performance-wise field_value_suggestion_mode = on # Global timeout for index optimization (force merge) requests. # Default: 1h #elasticsearch_index_optimization_timeout = 1h # Maximum number of concurrently running index optimization (force merge) jobs. # If you are using lots of different index sets, you might want to increase that number. # This value should be set lower than elasticsearch_max_total_connections_per_route, otherwise index optimization # could deplete all the client connections to the search server and block new messages ingestion for prolonged # periods of time. # Default: 10 #elasticsearch_index_optimization_jobs = 10 # Mute the logging-output of ES deprecation warnings during REST calls in the ES RestClient #elasticsearch_mute_deprecation_warnings = true # Time interval for index range information cleanups. This setting defines how often stale index range information # is being purged from the database. # Default: 1h #index_ranges_cleanup_interval = 1h # Batch size for the Elasticsearch output. This is the maximum (!) number of messages the Elasticsearch output # module will get at once and write to Elasticsearch in a batch call. If the configured batch size has not been # reached within output_flush_interval seconds, everything that is available will be flushed at once. Remember # that every outputbuffer processor manages its own batch and performs its own batch write calls. # ("outputbuffer_processors" variable) output_batch_size = 500 # Flush interval (in seconds) for the Elasticsearch output. This is the maximum amount of time between two # batches of messages written to Elasticsearch. It is only effective at all if your minimum number of messages # for this time period is less than output_batch_size * outputbuffer_processors. output_flush_interval = 1 # As stream outputs are loaded only on demand, an output which is failing to initialize will be tried over and # over again. To prevent this, the following configuration options define after how many faults an output will # not be tried again for an also configurable amount of seconds. output_fault_count_threshold = 5 output_fault_penalty_seconds = 30 # Number of process buffer processors running in parallel. # By default, the value will be determined automatically based on the number of CPU cores available to the JVM, using # the formula ( * 0.36 + 0.625) rounded to the nearest integer. # Set this value explicitly to override the dynamically calculated value. Try raising the number if your buffers are # filling up. #processbuffer_processors = 5 # Number of output buffer processors running in parallel. # By default, the value will be determined automatically based on the number of CPU cores available to the JVM, using # the formula ( * 0.162 + 0.625) rounded to the nearest integer. # Set this value explicitly to override the dynamically calculated value. Try raising the number if your buffers are # filling up. #outputbuffer_processors = 3 # The size of the thread pool in the output buffer processor. # Default: 3 #outputbuffer_processor_threads_core_pool_size = 3 # UDP receive buffer size for all message inputs (e. g. SyslogUDPInput). #udp_recvbuffer_sizes = 1048576 # Time in milliseconds after which a detected stale leader node is being rechecked on startup. #stale_leader_timeout = 2000 # Time in milliseconds which Graylog is waiting for all threads to stop on shutdown. #shutdown_timeout = 30000 # MongoDB connection string # See https://docs.mongodb.com/manual/reference/connection-string/ for details mongodb_uri = mongodb://localhost/graylog # Authenticate against the MongoDB server # '+'-signs in the username or password need to be replaced by '%2B' #mongodb_uri = mongodb://grayloguser:secret@localhost:27017/graylog # Use a replica set instead of a single host #mongodb_uri = mongodb://grayloguser:secret@localhost:27017,localhost:27018,localhost:27019/graylog?replicaSet=rs01 # DNS Seedlist https://docs.mongodb.com/manual/reference/connection-string/#dns-seedlist-connection-format #mongodb_uri = mongodb+srv://server.example.org/graylog # Increase this value according to the maximum connections your MongoDB server can handle from a single client # if you encounter MongoDB connection problems. mongodb_max_connections = 1000 # Maximum number of attempts to connect to MongoDB on boot for the version probe. # # Default: 0, retry indefinitely until a connection can be established #mongodb_version_probe_attempts = 5 # Email transport #transport_email_enabled = false #transport_email_hostname = mail.example.com #transport_email_port = 587 #transport_email_use_auth = true #transport_email_auth_username = you@example.com #transport_email_auth_password = secret #transport_email_from_email = graylog@example.com #transport_email_socket_connection_timeout = 10s #transport_email_socket_timeout = 10s # Encryption settings # # ATTENTION: # Using SMTP with STARTTLS *and* SMTPS at the same time is *not* possible. # Use SMTP with STARTTLS, see https://en.wikipedia.org/wiki/Opportunistic_TLS #transport_email_use_tls = true # Use SMTP over SSL (SMTPS), see https://en.wikipedia.org/wiki/SMTPS # This is deprecated on most SMTP services! #transport_email_use_ssl = false # Specify and uncomment this if you want to include links to the stream in your stream alert mails. # This should define the fully qualified base url to your web interface exactly the same way as it is accessed by your users. #transport_email_web_interface_url = https://graylog.example.com # The default connect timeout for outgoing HTTP connections. # Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds). # Default: 5s #http_connect_timeout = 5s # The default read timeout for outgoing HTTP connections. # Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds). # Default: 10s #http_read_timeout = 10s # The default write timeout for outgoing HTTP connections. # Values must be a positive duration (and between 1 and 2147483647 when converted to milliseconds). # Default: 10s #http_write_timeout = 10s # HTTP proxy for outgoing HTTP connections # ATTENTION: If you configure a proxy, make sure to also configure the "http_non_proxy_hosts" option so internal # HTTP connections with other nodes does not go through the proxy. # Examples: # - http://proxy.example.com:8123 # - http://username:password@proxy.example.com:8123 #http_proxy_uri = # A list of hosts that should be reached directly, bypassing the configured proxy server. # This is a list of patterns separated by ",". The patterns may start or end with a "*" for wildcards. # Any host matching one of these patterns will be reached through a direct connection instead of through a proxy. # Examples: # - localhost,127.0.0.1 # - 10.0.*,*.example.com #http_non_proxy_hosts = # Connection timeout for a configured LDAP server (e. g. ActiveDirectory) in milliseconds. #ldap_connection_timeout = 2000 # Disable the use of a native system stats collector (currently OSHI) #disable_native_system_stats_collector = false # The default cache time for dashboard widgets. (Default: 10 seconds, minimum: 1 second) #dashboard_widget_default_cache_time = 10s # For some cluster-related REST requests, the node must query all other nodes in the cluster. This is the maximum number # of threads available for this. Increase it, if '/cluster/*' requests take long to complete. # Should be http_thread_pool_size * average_cluster_size if you have a high number of concurrent users. #proxied_requests_thread_pool_size = 64 # The default HTTP call timeout for cluster-related REST requests. This timeout might be overriden for some # resources in code or other configuration values. (some cluster metrics resources use a lower timeout) #proxied_requests_default_call_timeout = 5s # The server is writing processing status information to the database on a regular basis. This setting controls how # often the data is written to the database. # Default: 1s (cannot be less than 1s) #processing_status_persist_interval = 1s # Configures the threshold for detecting outdated processing status records. Any records that haven't been updated # in the configured threshold will be ignored. # Default: 1m (one minute) #processing_status_update_threshold = 1m # Configures the journal write rate threshold for selecting processing status records. Any records that have a lower # one minute rate than the configured value might be ignored. (dependent on number of messages in the journal) # Default: 1 #processing_status_journal_write_rate_threshold = 1 # Automatically load content packs in "content_packs_dir" on the first start of Graylog. #content_packs_loader_enabled = false # The directory which contains content packs which should be loaded on the first start of Graylog. # Default: /contentpacks #content_packs_dir = data/contentpacks # A comma-separated list of content packs (files in "content_packs_dir") which should be applied on # the first start of Graylog. # Default: empty #content_packs_auto_install = grok-patterns.json # The allowed TLS protocols for system wide TLS enabled servers. (e.g. message inputs, http interface) # Setting this to an empty value, leaves it up to system libraries and the used JDK to chose a default. # Default: TLSv1.2,TLSv1.3 (might be automatically adjusted to protocols supported by the JDK) #enabled_tls_protocols = TLSv1.2,TLSv1.3 # Optional limits on scheduling concurrency by job type. No more than the specified number of worker # threads will be executing jobs of the specified type across the entire cluster. # Default: no limitation # Note: Monitor job queue metrics to avoid excessive backlog of unprocessed jobs when using this setting! # Available job types in Graylog Open: # check-for-cert-renewal-execution-v1 # event-processor-execution-v1 # notification-execution-v1 #job_scheduler_concurrency_limits = event-processor-execution-v1:2,notification-execution-v1:2

Error: [type=illegal_argument_exception, reason=key [types] while integrating wazuh indexer (opensearch) to graylog

Wine_Merchant September 9, 2024, 8:27am 2

It looks like someone else had this issue, does their solution fix the issue?

Topic		Replies	Views
Integrating wazuh indexer with Graylog Graylog Central (peer support)	9	6508	November 14, 2022
Graylog indices Graylog Central (peer support)	22	7046	June 27, 2018
Graylog 5.0 with Wazuh Indexer Graylog Central (peer support)	11	9594	May 23, 2023
Quick Fix - bypass expired Cert to view lidices on Opensearch Graylog Central (peer support) access-specific-log- , architecture	4	254	March 17, 2025
Elasticsearch exception reason=key [types] is not supported in the metadata section Graylog Central (peer support)	6	7387	January 27, 2023

Error: [type=illegal_argument_exception, reason=key [types] while integrating wazuh indexer (opensearch) to graylog

Related topics