# Writing an article - topics to cover?

**URL:** <https://discuss.elastic.co/t/writing-an-article-topics-to-cover/19289>\
**Category:** Elasticsearch\
**Created:** [August 14, 2014, 3:40pm UTC](https://discuss.elastic.co/t/writing-an-article-topics-to-cover/19289 "2014-08-14T15:40:38Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Christopher\_Ambler\_2](https://avatars.discourse-cdn.com/v4/letter/c/b5ac83/32.png) [@Christopher\_Ambler\_2](https://discuss.elastic.co/u/Christopher_Ambler_2)\
**Post date:** [August 14, 2014, 3:40pm UTC](https://discuss.elastic.co/t/writing-an-article-topics-to-cover/19289/1 "2014-08-14T15:40:38Z")

</div>

I've been tasked to write an article (that will be public-facing) on my  
experience setting up ElasticSearch as part of the project I'm working on  
at GoDaddy.

I'd like to solicit input on any topics that I might want to make sure I  
don't miss.

The scope is installation, configuration, and basic monitoring (head and  
marvel) as well as the decent number of issues I came across and how I  
solved them. Indeed, I'll also cover some of the issues that I'm _still_  
having and how I'm working on them.

Since this will be public-facing, though, I'd love to know what others  
would like to see in such an article. If I can, I'll try to cover those  
topics to give it a bit more value.

Thanks!

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/0a8f4d62-0f3f-4cf9-ab1f-3d8043245b7d%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/0a8f4d62-0f3f-4cf9-ab1f-3d8043245b7d%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![nik9000](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nik9000/32/44947_2.png) [@nik9000](https://discuss.elastic.co/u/nik9000)\
**Post date:** [August 14, 2014, 4:02pm UTC](https://discuss.elastic.co/t/writing-an-article-topics-to-cover/19289/2 "2014-08-14T16:02:12Z")

</div>

On Thu, Aug 14, 2014 at 11:40 AM, Christopher Ambler \<  
[const.dogberry@gmail.com](mailto:const.dogberry@gmail.com)\> wrote:

I've been tasked to write an article (that will be public-facing) on my

> experience setting up Elasticsearch as part of the project I'm working on  
> at GoDaddy.
> 
> I'd like to solicit input on any topics that I might want to make sure I  
> don't miss.
> 
> The scope is installation, configuration, and basic monitoring (head and  
> marvel) as well as the decent number of issues I came across and how I  
> solved them. Indeed, I'll also cover some of the issues that I'm _still_  
> having and how I'm working on them.
> 
> Since this will be public-facing, though, I'd love to know what others  
> would like to see in such an article. If I can, I'll try to cover those  
> topics to give it a bit more value.
> 
> Thanks!

Honestly a story of the issues you've hit and how you worked around  
them/plan to work around them would be cool. Its something I'll probably  
do in a few months as well. Once I've worked around enough of those issues  
🙂

Nik

--  
You received this message because you are subscribed to the Google Groups "elasticsearch" group.  
To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/CAPmjWd02CEvmVCPgG56vZAnsnkcNrVb1S7%2B\_9O%2BQ10K5vxucZw%40mail.gmail.com](https://groups.google.com/d/msgid/elasticsearch/CAPmjWd02CEvmVCPgG56vZAnsnkcNrVb1S7%2B_9O%2BQ10K5vxucZw%40mail.gmail.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<div class="post-metadata">

**Author:** ![Ethan\_Winograd](https://avatars.discourse-cdn.com/v4/letter/e/f04885/32.png) [@Ethan\_Winograd](https://discuss.elastic.co/u/Ethan_Winograd)\
**Post date:** [August 15, 2014, 8:17pm UTC](https://discuss.elastic.co/t/writing-an-article-topics-to-cover/19289/3 "2014-08-15T20:17:11Z")

</div>

> > I've been tasked to write an article (that will be public-facing) on my experience setting up Elasticsearch as part of the project I'm working on at GoDaddy.

I think that anything around your approach for estimating disk and ram requirements and how they turned out would be awesome.

---

<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 6, 2017, 1:08am UTC](https://discuss.elastic.co/t/writing-an-article-topics-to-cover/19289/4 "2017-07-06T01:08:13Z")

</div>

Closed on July 6, 2017, 1:08am UTC


