# Beat's Central Management - Error initializing output: output type undefined

**URL:** <https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495>\
**Category:** Beats\
**Tags:** fleet, metricbeat\
**Created:** [February 7, 2019, 5:55pm UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495 "2019-02-07T17:55:13Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 7, 2019, 5:55pm UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/1 "2019-02-07T17:55:13Z")

</div>

Hello World!

I'm trying to follow:

- [Beats central management | Metricbeat Reference [6.6] | Elastic](https://www.elastic.co/guide/en/beats/metricbeat/current/configuration-central-management.html)
- [How central management works | Metricbeat Reference [6.6] | Elastic](https://www.elastic.co/guide/en/beats/metricbeat/current/how-central-managment-works.html#how-central-managment-works)
- [Enroll Beats in central management | Metricbeat Reference [6.6] | Elastic](https://www.elastic.co/guide/en/beats/metricbeat/current/enroll-beats.html).

and even though through `Central Management (Beta)`'s `Config Status` says `OK`, I'm not seeing any of events in `filebeat-*` and/or `metricbeat-*`(

I'm not sure if this is relevant as beat was enrolled for Central Management

```
# metricbeat test config
Config OK
# metricbeat test output
Error initializing output: output type undefined
# 

```

Please advise.

---

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [February 12, 2019, 9:32am UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/2 "2019-02-12T09:32:49Z")

</div>

Hi @alexus 🙂

Can you paste the contents of your Metricbeat configuration? It doesn't seem an error of Central Management.

I think that the problem is that you don't have an output defined in your Metricbeat configuration file. Check it and ensure you have an uncommented output like:

```auto
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["localhost:9200"]

  # Optional protocol and basic auth credentials.
  #protocol: "https"
  #username: "elastic"
  #password: "changeme"

```

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 12, 2019, 5:06pm UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/3 "2019-02-12T17:06:29Z")

</div>

As I mentioned in earlier, I did enroll of \*beat into Central Management, so my config is tiny now:

```
management:
  enabled: true
  period: 1m0s
  access_token: ${management.accesstoken}
  kibana:
    protocol: https
    host: X:443
    ssl: null
    timeout: 10s
    ignoreversion: true
  blacklist:
    output: console|file

```

not sure if `output.elasticsearch` is required anymore, and that is probably why I'm getting an error while doing "test output".

---

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [February 14, 2019, 9:54am UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/4 "2019-02-14T09:54:08Z")

</div>

Yes, you are right, I didn't tought about it but the `test output` command relies on what is written in the YML file. It doesn't check with CM yet.

Maybe you can file us an issue on Github if you think it's a good addition 🙂

---

<div class="post-metadata">

**Author:** ![Matthew\_Apperson](https://avatars.discourse-cdn.com/v4/letter/m/6bbea6/32.png) [@Matthew\_Apperson](https://discuss.elastic.co/u/Matthew_Apperson)\
**Post date:** [February 21, 2019, 2:35pm UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/5 "2019-02-21T14:35:56Z")

</div>

Did you configure an output configuration in CM via a tag assigned to these beats?

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 22, 2019, 5:28am UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/6 "2019-02-22T05:28:49Z")

</div>

yes, an output configuration block was configured in CM via a tag was assigned to these beats.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [February 22, 2019, 5:30am UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/7 "2019-02-22T05:30:26Z")

</div>

ok, will file issue on GitHub as I do think it's good addition to say relevant to CM...

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 22, 2019, 5:30am UTC](https://discuss.elastic.co/t/beats-central-management-error-initializing-output-output-type-undefined/167495/8 "2019-03-22T05:30:42Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.