# Metricbeat output to Cloudwatch?

**URL:** <https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [August 7, 2017, 7:56pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149 "2017-08-07T19:56:08Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![rherr63](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@rherr63](https://discuss.elastic.co/u/rherr63)\
**Post date:** [August 7, 2017, 7:56pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/1 "2017-08-07T19:56:08Z")

</div>

I saw this link pertaining to Logstash. Can this be modified to send MetricBeat data to CloudWatch (and still use native AWS Cloudwatch functionality such as dashboarding, alerting, CW log events? [https://www.elastic.co/guide/en/logstash/current/plugins-outputs-cloudwatch.html](https://www.elastic.co/guide/en/logstash/current/plugins-outputs-cloudwatch.html)

Or is anything available for this use case?  
Thanks, RHerring

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [August 7, 2017, 10:56pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/2 "2017-08-07T22:56:49Z")

</div>

If you send Metricbeat data to Logstash, you can then send it to Cloudwatch using this.

---

<div class="post-metadata">

**Author:** ![rherr63](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@rherr63](https://discuss.elastic.co/u/rherr63)\
**Post date:** [August 8, 2017, 12:31pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/3 "2017-08-08T12:31:11Z")

</div>

Mark, thank you for your reply. If Logstash is NOT part of our roadmap/data pipeline, are there any other options for sending data from MetricBeat to CloudWatch? I have seen many links about "metric-developer-guide", "beats-contributing", "creating-beat-from-metricbeat". If I have access to a developer, is it possible to create a "CloudWatch" output module to serve this purpose? Thanks, RHerring

---

<div class="post-metadata">

**Author:** ![rherr63](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@rherr63](https://discuss.elastic.co/u/rherr63)\
**Post date:** [August 8, 2017, 8:27pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/4 "2017-08-08T20:27:21Z")

</div>

I was able to confirm the correct terminology now. MetricBeat has several out-of-the-box output options such as Elasticsearch Output, Logstash Output, Kafka Output, Redis Output, etc. Since we do not use any of these options in our data pipeline, we need a new output module for sending MetricBeat metrics to CloudWatch, (e.g. "CloudWatch Output"). If I am reviewing verbiage from your 'Metricbeat Developer Guide', should my developer follow 1.) 'Creating a Metricbeat Module' or 2.) 'Creating a Beat based on Metricbeat' if the end goal is to be able to extend the MetricBeat functionality to accept a new output, e.g. output.cloudwatch:, in the metricbeat.yml file?

Thanks,  
RHerring

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [August 9, 2017, 11:40am UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/5 "2017-08-09T11:40:48Z")

</div>

Writing custom outputs is not included in any developers documentation we have. You can write your custom output and use it with your custom beat based on metricbeat. But you will have to maintain the output yourself, as we're not eager to accept a many more output type in the public beats repository.

See the communities HTTP output for example: [https://github.com/raboof/beats-output-http](https://github.com/raboof/beats-output-http)

---

<div class="post-metadata">

**Author:** ![rherr63](https://avatars.discourse-cdn.com/v4/letter/r/ccd318/32.png) [@rherr63](https://discuss.elastic.co/u/rherr63)\
**Post date:** [August 9, 2017, 12:43pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/6 "2017-08-09T12:43:44Z")

</div>

ok but based on your response, it sounds like creating a new putput is something that is indeed possible to accomplish. That is the main point I needed to confirm. Thank you!

---

<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:** [September 6, 2017, 12:43pm UTC](https://discuss.elastic.co/t/metricbeat-output-to-cloudwatch/96149/7 "2017-09-06T12:43:57Z")

</div>

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