# APM Server Offline Retention / Synchronization

**URL:** <https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155>\
**Category:** APM\
**Created:** [June 24, 2018, 4:42pm UTC](https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155 "2018-06-24T16:42:53Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![hayden.ball](https://avatars.discourse-cdn.com/v4/letter/h/ebca7d/32.png) [@hayden.ball](https://discuss.elastic.co/u/hayden.ball)\
**Post date:** [June 24, 2018, 4:42pm UTC](https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155/1 "2018-06-24T16:42:53Z")

</div>

Hello.

The APM system looks really promising, and I'm hoping we'll be able to use it to solve our needs.

We've a slightly difficult situation as we've an app that runs in the cloud, but also on client operated site boxes. Site boxes are often offline when in use, and we synchronise data when they next have an internet connection.

We've successfully managed to collect logs by using Logstash's persistent queues, and we're investigating using metricbeat (outputting to Logstash) for system metrics for our site boxes. We're also looking for an APM solution, and I'm hoping that Elastic's APM Server will be up to the job.

Currently, the documentation doesn't mention any way of configuring APM Server to output to Logstash.  
Is there any way we could support offline collection of metrics using APM Server (either by outputting to Logstash or otherwise)? If not, is this something that's planned?

---

<div class="post-metadata">

**Author:** ![hayden.ball](https://avatars.discourse-cdn.com/v4/letter/h/ebca7d/32.png) [@hayden.ball](https://discuss.elastic.co/u/hayden.ball)\
**Post date:** [June 24, 2018, 5:17pm UTC](https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155/2 "2018-06-24T17:17:24Z")

</div>

Came across [https://github.com/elastic/apm-server/issues/664](https://github.com/elastic/apm-server/issues/664) after posting this, so it looks like it's on the roadmap.

Out of interest, is there any way of making Logstash "appear" like ElasticSearch in the mean time?  
I wonder if a TCP input with the es\_bulk codec (or something similar) might work?

---

<div class="post-metadata">

**Author:** ![gil](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/gil/32/41911_2.png) [@gil](https://discuss.elastic.co/u/gil)\
**Post date:** [June 25, 2018, 5:34pm UTC](https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155/3 "2018-06-25T17:34:27Z")

</div>

@hayden.ball Thanks for giving APM a spin, we're eager to hear more of your feedback.

Your setup does seem challenging but it sounds like you're very close to a working solution. I've updated the github issue with a configuration that might work for your needs. We will continue to update that issue as we make progress towards a supported solution.

---

<div class="post-metadata">

**Author:** ![hayden.ball](https://avatars.discourse-cdn.com/v4/letter/h/ebca7d/32.png) [@hayden.ball](https://discuss.elastic.co/u/hayden.ball)\
**Post date:** [June 26, 2018, 12:44pm UTC](https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155/4 "2018-06-26T12:44:57Z")

</div>

Thanks Gil - I'll give it a go.

---

<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:** [July 17, 2018, 8:45am UTC](https://discuss.elastic.co/t/apm-server-offline-retention-synchronization/137155/5 "2018-07-17T08:45:08Z")

</div>

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