# Confusion on the Create Beat instruction

**URL:** <https://discuss.elastic.co/t/confusion-on-the-create-beat-instruction/197981>\
**Category:** Beats\
**Tags:** beats-development\
**Created:** [September 4, 2019, 5:52am UTC](https://discuss.elastic.co/t/confusion-on-the-create-beat-instruction/197981 "2019-09-04T05:52:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nee\_Defeng](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nee_defeng/32/45771_2.png) [@Nee\_Defeng](https://discuss.elastic.co/u/Nee_Defeng)\
**Post date:** [September 4, 2019, 5:52am UTC](https://discuss.elastic.co/t/confusion-on-the-create-beat-instruction/197981/1 "2019-09-04T05:52:16Z")

</div>

According to this url:  
[https://www.elastic.co/guide/en/beats/devguide/master/newbeat-generate.html](https://www.elastic.co/guide/en/beats/devguide/master/newbeat-generate.html)

```
Now create a directory under $GOPATH for your repository and change to the new directory:
mkdir ${GOPATH}/src/github.com/{user}
cd ${GOPATH}/src/github.com/{user}

```

And then later in the document, it says:

```
Beat Name [Examplebeat]: Countbeat
Your Github Name [your-github-name]: {username}
Beat Path [github.com/ **{github id}** /{beat name}]:
Firstname Lastname: {Full Name}

```

Is this {github id} the same as the {user}?

And then when [fetch dependencies and set up the Beat] in the next step, it never asks for the {user} directory any more. What is it used for? Since I am having some errors (as in my last post), I believe it is the documentation error, and it needs to be fixed ASAP.

---

<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:** [October 2, 2019, 6:02am UTC](https://discuss.elastic.co/t/confusion-on-the-create-beat-instruction/197981/2 "2019-10-02T06:02:21Z")

</div>

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