# Configuring OSS Beats (File/Metric) with opendistro

**URL:** https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349
**Category:** Open Source Elasticsearch and Kibana
**Created:** [August 19, 2019, 3:42am UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349 "2019-08-19T03:42:38Z")
**Posts on this page:** 8
**Page:** 1

<div class="post-metadata">

### Author: ![opendistro](https://avatars.discourse-cdn.com/v4/letter/o/7cd45c/32.png) [@opendistro](https://forum.opensearch.org/u/opendistro)
#### Post date: [August 19, 2019, 3:42am UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/1 "2019-08-19T03:42:38Z")

</div>

Hi - We installed opendistro successfully and tried to do setup for filebeat/metricbeat for Linux & Windows both.

We downloaded right OSS beat packages as per other threads  
[https://artifacts.elastic.co/downloads/beats/metricbeat/metricbeat-oss-6.3.0-linux-x86\_64.tar.gz](https://artifacts.elastic.co/downloads/beats/metricbeat/metricbeat-oss-6.3.0-linux-x86_64.tar.gz)  
[https://artifacts.elastic.co/downloads/beats/heartbeat/heartbeat-oss-6.3.0-linux-x86\_64.tar.gz](https://artifacts.elastic.co/downloads/beats/heartbeat/heartbeat-oss-6.3.0-linux-x86_64.tar.gz)  
[https://artifacts.elastic.co/downloads/beats/filebeat/heartbeat-oss-6.3.0-linux-x86\_64.tar.gz](https://artifacts.elastic.co/downloads/beats/filebeat/heartbeat-oss-6.3.0-linux-x86_64.tar.gz)

ran following command  
filebeat setup -e --dashboards --pipelines --template

We tried all versions 7.1.1 to 6.3.0

Error in console →

500 Internal Server Error: {“error”:{“root\_cause”:[{“type”:“security\_exception”,“reason”:“Unexpected exception indices:admin/get”}],“type”:“security\_exception”,“reason”:“Unexpected exception indices:admin/get”},“status”:500}

Exiting: request checking for ILM availability failed: 500 Internal Server Error: {“error”:{“root\_cause”:[{“type”:“security\_exception”,“reason”:“Unexpected exception indices:admin/get”}],“type”:“security\_exception”,“reason”:“Unexpected exception indices:admin/get”},“status”:500}

Error in Elastic search -

[2019-08-19T03:37:43,286][WARN][r.suppressed] [node-1] path: /\_xpack, params: {index=\_xpack}  
org.elasticsearch.ElasticsearchSecurityException: Unexpected exception indices:admin/get  
at com.amazon.opendistroforelasticsearch.security.filter.OpenDistroSecurityFilter.apply0(OpenDistroSecurityFilter.java:274) [opendistro\_security-1.1.0.0.jar:1.1.0.0]  
at com.amazon.opendistroforelasticsearch.security.filter.OpenDistroSecurityFilter.apply(OpenDistroSecurityFilter.java:119) [opendistro\_security-1.1.0.0.jar:1.1.0.0]  
at org.elasticsearch.action.support.TransportAction$RequestFilterChain.proceed(TransportAction.java:143) [elasticsearch-7.1.1.jar:7.1.1]  
at org.elasticsearch.action.support.TransportAction.execute(TransportAction.java:121) [elasticsearch-7.1.1.jar:7.1.1]

Please help!!

---

<div class="post-metadata">

### Author: ![ogulman](https://avatars.discourse-cdn.com/v4/letter/o/9fc29f/32.png) [@ogulman](https://forum.opensearch.org/u/ogulman)
#### Post date: [August 19, 2019, 7:37am UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/2 "2019-08-19T07:37:30Z")

</div>

try to add into your winlogbeat configuration:

```
setup.ilm.enabled: false

```

also follow version compatibility:

> **[Support Matrix](https://www.elastic.co/support/matrix#matrix_compatibility)**

---

<div class="post-metadata">

### Author: ![opendistro](https://avatars.discourse-cdn.com/v4/letter/o/7cd45c/32.png) [@opendistro](https://forum.opensearch.org/u/opendistro)
#### Post date: [August 19, 2019, 9:43am UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/3 "2019-08-19T09:43:12Z")

</div>

Hi - does not help.  
I wonder why OSS beat version sends xpack commands?

Anyone has gotten beats to work with opendistro?

---

<div class="post-metadata">

### Author: ![ogulman](https://avatars.discourse-cdn.com/v4/letter/o/9fc29f/32.png) [@ogulman](https://forum.opensearch.org/u/ogulman)
#### Post date: [August 19, 2019, 11:29am UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/4 "2019-08-19T11:29:47Z")

</div>

It’s works well with opendistro.  
Did you restart a winlogbeat service after changing config?

---

<div class="post-metadata">

### Author: ![opendistro](https://avatars.discourse-cdn.com/v4/letter/o/7cd45c/32.png) [@opendistro](https://forum.opensearch.org/u/opendistro)
#### Post date: [August 20, 2019, 7:14am UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/5 "2019-08-20T07:14:51Z")

</div>

Thank you. It worked for winlogbeat  
But does not work for any of the linux beats - file, audit, heart.  
Any thoughts on that?

---

<div class="post-metadata">

### Author: ![Ryan\_Downey](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/ryan_downey/32/347_2.png) [@Ryan\_Downey](https://forum.opensearch.org/u/Ryan_Downey)
#### Post date: [August 27, 2019, 6:57pm UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/6 "2019-08-27T18:57:23Z")

</div>

From what I understand this is telling you theres some sort of security enabled. Either xpack has been set up or you have users/passwords setup that are preventing the beat from accessing the indices. Check that any of those settings are set correctly and/or turned off. OSS is interesting because they wont talk to a non-oss stack from what I understand but non-oss beats can talk to an oss stack.

---

<div class="post-metadata">

### Author: ![Binging](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.opensearch.org/binging/32/1088_2.png) [@Binging](https://forum.opensearch.org/u/Binging)
#### Post date: [February 4, 2021, 4:40pm UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/7 "2021-02-04T16:40:04Z")

</div>

Same problem with Linux VMs:  
According to this info : [Troubleshoot - Open Distro Documentation](https://opendistro.github.io/for-elasticsearch-docs/docs/troubleshoot/)

 ![image](https://us1.discourse-cdn.com/flex019/uploads/mauve_hedgehog/original/2X/1/121450f671bc17dbe87c9ccd0deb3f9bc7166531.png)

Anyone can show some examples of how to play with ssl things how to generate client .pem stuff !?

---

<div class="post-metadata">

### Author: ![madcowtricks](https://avatars.discourse-cdn.com/v4/letter/m/2acd7d/32.png) [@madcowtricks](https://forum.opensearch.org/u/madcowtricks)
#### Post date: [February 13, 2021, 9:32pm UTC](https://forum.opensearch.org/t/configuring-oss-beats-file-metric-with-opendistro/1349/8 "2021-02-13T21:32:42Z")

</div>

I’m still fighting the same error as you. But I did figure out making a client ssl to point at. Go back to where you configured security guard to generate your nodes and root-ca keys. Add the node you want a certificate for in the yml file. Then type searchguard/tools/sgtlstools.sh -crt -c ./search-guard.yml -t ./certs".  
This assumes you have a copy of your root signing key in the directory certs
