# Logentries on Rancher OS

**URL:** <https://forums.suse.com/t/logentries-on-rancher-os/60>\
**Category:** RancherOS\
**Created:** [July 12, 2015, 6:14am UTC](https://forums.suse.com/t/logentries-on-rancher-os/60 "2015-07-12T06:14:32Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Peter\_Sellars](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/peter_sellars/32/32_2.png) [@Peter\_Sellars](https://forums.suse.com/u/Peter_Sellars)\
**Post date:** [July 12, 2015, 6:14am UTC](https://forums.suse.com/t/logentries-on-rancher-os/60/1 "2015-07-12T06:14:32Z")

</div>

I am investigating the use of Logentries. I have a RancherOS Vagrant instance and a RacherOS AWS instance and would like to know if there is anything I need to know that could cause issues with the Logentries container in a Rancher OS instance?

---

<div class="post-metadata">

**Author:** ![ibuildthecloud](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/ibuildthecloud/32/8_2.png) [@ibuildthecloud](https://forums.suse.com/u/ibuildthecloud)\
**Post date:** [July 14, 2015, 6:00pm UTC](https://forums.suse.com/t/logentries-on-rancher-os/60/2 "2015-07-14T18:00:18Z")

</div>

I don’t have specific experience with Logentries but based off of the documentation I believe it should work because they have a Docker container. Did you try this, did it work?

---

<div class="post-metadata">

**Author:** ![Peter\_Sellars](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/peter_sellars/32/32_2.png) [@Peter\_Sellars](https://forums.suse.com/u/Peter_Sellars)\
**Post date:** [July 15, 2015, 9:31am UTC](https://forums.suse.com/t/logentries-on-rancher-os/60/3 "2015-07-15T09:31:45Z")

</div>

I have tried it with a RancherOS Vagrant instance - I am just trying some network configuration changes in the Vagrant box to see if that is my issue at this time. I have the logentries container running in the RancherOS and see it in the Rancher I have installed on it. Trying to determine if the network configuration is my issue.

Running this command:

```
docker run -d -v /var/run/docker.sock:/var/run/docker.sock logentries/docker-logentries -t [token] -j -a host=`uname -n`

```

I tried that with the networking through the host too using

```
--net=host

```

…still no success.

---

<div class="post-metadata">

**Author:** ![Peter\_Sellars](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/peter_sellars/32/32_2.png) [@Peter\_Sellars](https://forums.suse.com/u/Peter_Sellars)\
**Post date:** [July 17, 2015, 7:29am UTC](https://forums.suse.com/t/logentries-on-rancher-os/60/4 "2015-07-17T07:29:35Z")

</div>

I solved this issue - it was a noob problem. Nothing to do with Rancher OS. I had not configured the token correctly on the Logentries end. Set this up and used it with the Logentries container and now receiving logs. Onwards and upwards now with my RancherOS and Rancher exploration.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [July 17, 2015, 4:10pm UTC](https://forums.suse.com/t/logentries-on-rancher-os/60/5 "2015-07-17T16:10:03Z")

</div>

Great! I’m glad to hear that it’s working. 😄

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [July 17, 2015, 4:10pm UTC](https://forums.suse.com/t/logentries-on-rancher-os/60/6 "2015-07-17T16:10:07Z")

</div>