Migrate the JHipster Console to Kibana 5 about jhipster-console HOT 13 CLOSED

I finally managed to have the ELK v5 stack working ! I commited my work on the elastic-v5 branch.

Warning, all dashboards are broken !

from jhipster-console.

Yes everything works except for alerting, you can start using it by moving to the v2.0.0-beta docker tag : https://github.com/jhipster/jhipster-console/releases/tag/v2.0.0-beta
I'm just waiting for elastalert to release a new version compatible with the elastic stack v5.

from jhipster-console.

It indeed looks super awesome. I love the design. But should we wait for a
stable RC?

Thanks & Regards,
Deepu

On Fri, Apr 8, 2016 at 8:32 PM, Pierre Besson [email protected]
wrote:

https://www.elastic.co/blog/kibana-5-0-0-alpha1?blade=tw

Looks very cool, too bad there doesn't seem to be docker images available.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#24

from jhipster-console.

Yes indeed, but looking at the pace elastic release their product, it should be released shortly.
Also it seems to have better features for monitoring, as well as way to integrate your own plugins.

My idea, was that in the future we could develop a JHipster plugin to show a registry screen + something like spring boot admin: https://github.com/codecentric/spring-boot-admin + gogs for the registry's configuration source.
Maybe we can even integrate things like Hystrix Dashboard and Zipkin http://zipkin.io/

from jhipster-console.

+1 FWIW, there is a nice registry dashboard with downstream services config and hystrix aggregator (via turbine), like the spring boot admin dashboard here: https://github.com/VanRoy/spring-cloud-dashboard

from jhipster-console.

Those projects are nice but one concern I have, is that I'm not sure if they have been given the authorization by the Spring Team to use the names "spring boot" and "spring cloud".

from jhipster-console.

FYI we now have cassandra cluster metrics if you want (from the driver)

from jhipster-console.

@cbornet. Oh yeah, @jdubois told me today about it. I will try to do something in the coming weeks...
[Edit] just taking a look at the docs, it seems it uses dropwizard metrics. Does that means that metrics are already collected and forwarded to the console ? So we just need to make dashboards ?

from jhipster-console.

Work on the elastic v5 migration has been commited to master. It works fine but the dashboards will need to be done again.

The logo also needs to be redone because of Kibana's redesign, now it looks like this:

And in collapsed mode:

Actually the original Kibana logo is this one all white and transparent to go with the ping background.

from jhipster-console.

We can make it transparent as well. Ill try to do it this weekend

Thanks & regards,
Deepu

On 28 Oct 2016 03:12, "Pierre Besson" [email protected] wrote:

Work on the elastic v5 migration has been commited to master. It works
fine but the dashboards will need to be done again.

The logo also needs to be redone because of Kibana's redesign, now it
looks like this:
[image: capture du 2016-10-27 23-34-22]
https://cloud.githubusercontent.com/assets/513471/19786454/57a0ac9c-9c9e-11e6-9651-e52067c13a3c.png
And in collapsed mode:
[image: capture du 2016-10-27 23-35-36]
https://cloud.githubusercontent.com/assets/513471/19786488/77c5a98c-9c9e-11e6-855f-9a6505710b0b.png

Actually the original Kibana logo is this one
https://github.com/elastic/kibana/blob/01b426c94957adc7914371d91c9989b3a155a526/src/ui/public/images/kibana.svg
all white and transparent to go with the ping background.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#24 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABDlF5N0GslyQ_lGWLxh4BgVpBd4OBDUks5q4Rq1gaJpZM4IC9ZN
.

from jhipster-console.

Dashboard migration has been done here: 33d5408
I will soon release a v2 of the Console.

from jhipster-console.

@PierreBesson May you list me the remaining tasks before releasing V2?
Is that possible to create a "V2" milestone for related issues?

Are most of the features working? At the least, log centralization, vizaulization and dashboarding?

from jhipster-console.

@PierreBesson my .yo-rc.json looks like this:

{
  "generator-jhipster": {
    "jhipsterVersion": "3.12.0",
    ...
    "searchEngine": "elasticsearch",
    ...
  }
}

I choose the microservices architecture (gateway, microservice, registry, console...) and try to start it into production environnement.

The spring.data.elasticserach settings use the elasticsearch from console as the "cluster-nodes".
Unfortunatelly the ES client (2.4) is not fully compatible with ES node (5.X).

The following warning is raised again and again:

[unmapped_type:string] should be replaced with [unmapped_type:keyword]

And this dependency doesn't seem to be availalabe form ES 5.X:

<dependency>
     <groupId>org.springframework.boot</groupId>
     <artifactId>spring-boot-starter-data-elasticsearch</artifactId>
</dependency>

Just FYI

from jhipster-console.