# Why is the Sense page not rendering properly?

**URL:** <https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461>\
**Category:** Kibana\
**Tags:** elastic-stack-monitoring\
**Created:** [May 10, 2015, 8:26pm UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461 "2015-05-10T20:26:33Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![henry\_hamster](https://avatars.discourse-cdn.com/v4/letter/h/a88e4f/32.png) [@henry\_hamster](https://discuss.elastic.co/u/henry_hamster)\
**Post date:** [May 10, 2015, 8:26pm UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/1 "2015-05-10T20:26:33Z")

</div>

Hullo,

I am a total newbie to ES but excited to find out more. I got it running on a Raspberry Pi so I have my little ES node with me on long train journeys. Another node runs on my main server.  
I am trying to follow the ES tutorial and it recommended to install Marvel to get access to Sense.  
I can call [http://server.name:9200/\_plugins/marvel/sense](http://server.name:9200/_plugins/marvel/sense) but the page does not render properly (see below).

This is the same whether I am running this from the Pi or the main server, it's the same in Firefox and Chrome. Once I managed to run it to render properly, with the split window, etc. - but I have no idea how I did that.

Surely it must be a stupid newbie mistake, but I'd be grateful if you could point me at it? I did google a little, alas googling for "marvel + sense" is 90% comic related - which I am sure you know 😄  
Anyway, many thanks!  
Henry  
 ![](https://sea2.discourse-cdn.com/elastic/uploads/default/215/687822f90b820b47.PNG)

---

<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:** [May 12, 2015, 6:41am UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/2 "2015-05-12T06:41:17Z")

</div>

What if you open the developer console in your browser and see what is happening.

It could just be that the Pi doesn't have the resources to deal with the request, but that's just a guess.

---

<div class="post-metadata">

**Author:** ![henry\_hamster](https://avatars.discourse-cdn.com/v4/letter/h/a88e4f/32.png) [@henry\_hamster](https://discuss.elastic.co/u/henry_hamster)\
**Post date:** [May 12, 2015, 12:53pm UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/3 "2015-05-12T12:53:31Z")

</div>

Thank you Warkolm,

I suspected that as well, which is why I installed a node on my Ubuntu server (and that has well enough grunt) as I wrote in my original posting.

I did some looking around and found a more fundamental issue - the .deb package installs all the fonts and style sheets in a different directory to the place where the sense webpage is actually trying to find them. Easily fixed with creating a symbolic link in the ../../marvel/\_site directory to point at ../../marvel/\_site/sense/vendor

I shall go and find out where and how to log a bug for this.

Thanks,  
Henry

P.S. Since I wrote this I noticed that the /css and /app folders were also linked incorrectly in the sense page. So I now have three symlinks and all is ticking over nicely.

As all of the marvel plugin installs in one go, I am _fairly_ certain that it is not just some finger trouble on my behalf.

---

<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:** [May 12, 2015, 9:48pm UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/4 "2015-05-12T21:48:31Z")

</div>

We don't provide a deb package for Marvel, it's just a zip file with some proprietary code.

---

<div class="post-metadata">

**Author:** ![bleskes](https://avatars.discourse-cdn.com/v4/letter/b/71c47a/32.png) [@bleskes](https://discuss.elastic.co/u/bleskes)\
**Post date:** [May 26, 2015, 5:51am UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/5 "2015-05-26T05:51:41Z")

</div>

The problem lies in missing an extra trailing slash after the sense url. if you add it ([http://localhost:9200/\_plugin/marvel/sense/](http://localhost:9200/_plugin/marvel/sense/) ) everything seems to works fine.

---

<div class="post-metadata">

**Author:** ![abdbaddude](https://avatars.discourse-cdn.com/v4/letter/a/c2a13f/32.png) [@abdbaddude](https://discuss.elastic.co/u/abdbaddude)\
**Post date:** [March 30, 2016, 6:22pm UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/6 "2016-03-30T18:22:51Z")

</div>

@bleskes Works like charm. Thanks.

---

<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:44pm UTC](https://discuss.elastic.co/t/why-is-the-sense-page-not-rendering-properly/461/7 "2017-07-06T13:44:42Z")

</div>

Closed on July 6, 2017, 1:44pm UTC


