I am no Karaf expert but yes those features exist in the Karaf world as
well. You can install decanter which has alerting, monitoring, kibana for
logs and metrics. Off course you can install hawtio inside karaf as well.

I guess one critical thing to consider is whether you want to completely
separate your services so that they are independent of each other. The
advantage being failure or a bug in one does not affect the others. That is
the path I chose. I am not sure how spring admin works. Do you need to
embed it in every service and access it via a URL or does it connect
remotely to each service? Anyway for metrics and system level monitoring of
our docker containers and ec2 instances  we choose to go with telegraf  and
grafana. It works really well and we can view the metrics of each service
we have deployed. Grafana 4 has alerts so we can send slack messages if
memory or cpu goes up.  Then we added the elk stack for viewing logs and
trigger alerts for application level errors.

Would be interesting to hear from those we have worked with spring admin
and how they have done their setup.

Den 14 mars 2017 1:24 fm skrev "Mark Nuttall [via Camel]" <
ml-node+s465427n5795400...@n5.nabble.com>:

> It is. :)  There are other ways. As fully featured? (aka 12 factored app).
> I've not found it. FYI - You will need more than just Docker (see the
> things I mentioned).
>
> I was on my tablet at work earlier so it was tough to type and send links.
> So, for completeness, here is the link to Spring Boot Admin
> https://github.com/codecentric/spring-boot-admin
> and a video -
> https://spring.io/blog/2016/12/07/spring-tips-bootiful-dashboards
>
>
> On Mon, Mar 13, 2017 at 5:28 PM, mtod09 <[hidden email]
> <http:///user/SendEmail.jtp?type=node&node=5795400&i=0>> wrote:
>
> > Thanks Mark,
> >
> > I was just logging on to ask that exact question. The Spring Boot seems
> > like
> > a pretty clean way of packaging and delivering Camel to Docker.
> >
> > Mike
> >
> >
> >
> > --
> > View this message in context: http://camel.465427.n5.nabble.
> > com/Recommend-a-platform-for-running-Camel-tp5795331p5795397.html
> > Sent from the Camel - Users mailing list archive at Nabble.com.
> >
>
>
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://camel.465427.n5.nabble.com/Recommend-a-platform-for-running-Camel-
> tp5795331p5795400.html
> To start a new topic under Camel - Users, email
> ml-node+s465427n465428...@n5.nabble.com
> To unsubscribe from Camel - Users, click here
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=465428&code=c291Y2lhbmNlLmVxZGFtLnJhc2h0aUBnbWFpbC5jb218NDY1NDI4fDE1MzI5MTE2NTY=>
> .
> NAML
> <http://camel.465427.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>




--
View this message in context: 
http://camel.465427.n5.nabble.com/Recommend-a-platform-for-running-Camel-tp5795331p5795404.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Reply via email to