April 2016 - hawkular-dev - Jboss List Archives

by Heiko W.Rupp

Hey, I have cancelled the Tuesday all-team meeting (the 9:30 EST one) going forward. This format was less of a success lately and going forward we will schedule individual meetings for specific topics. Heiko

7 years, 1 month

1
0
0 / 0

Hawkular.org - Top Menu

by Stefan Negrea

Hello Everybody, I sent last Friday a Hawkular.org PR with a small change, the top menu now includes Metrics as a distinct entry. Here is the PR https://github.com/hawkular/hawkular.github.io/pull/163 . The rationale for this change is to help current and potential users find information about Metrics faster. John Sanda rewrote the entire user guide (very expansive now) and we also have a few more ideas to create more content. If there are no major objections, I would like to have the PR merged this week prior to the release of Metrics 0.16.0. But this also points to a different issue. I do not think the current top menu is adequate for the direction of Hawkular. Adding Metrics to the top menu is the first step, but the entire menu needs to be overhauled. Any thoughts? Thank you, Stefan Negrea Software Engineer

7 years, 1 month

3
2
0 / 0

Please welcome our GSoC students Anuj and Austin

by Heiko W.Rupp

Hello, please welcome Anuj and Austin as this years students on Hawkular. Anuj will work on the Android Client, where he has already done a lot of work. Austin will work on the agent for Vert.x to support inventory (sync) etc and to sort of bring it on par with the WildFly agent. Austin and Anuj are 2 out of 10 students for jboss.org this year. You can read more here: http://pilhuhn.blogspot.de/2016/04/welcome-gsoc-2016-students-to-jboss.html Heiko

7 years, 1 month

8
7
0 / 0

agent 0.17.2.Final - now supports metric sets for prometheus endpoints

by John Mazzitelli

I released another minor release of the agent in order for a new feature to be available. You can now filter metrics to be collected from Prometheus endpoints. Before you had no choice but to collect and store every metric from every Prometheus endpoint being monitored. That is still the default behavior, but now you have the option to selectively choose what metrics you want to collect and store (ignoring all the rest). See this blog entry for more: http://www.hawkular.org/blog/2016/04/22/collecting-metrics-from-prometheu...

7 years, 1 month

1
0
0 / 0

Hawkular Data Mining 0.1.0.Final Release

by Pavol Loffay

Hello Everyone, I am happy to announce first release 0.1.0.Final of Hawkular Data Mining. Release contains several time series models and utility classes for time series modelling: *Time series models* - Simple exponential smoothing - Double exponential smoothing (Holt's linear trend) - Seasonal triple exponential smoothing (Holt Winters) - Simple moving average (Weighted moving average) - AutomaticForecaster - which automatically selects the best model - All these models are estimated using maximum likelihood estimation and available for online learning Time series manipulation & Statistics - Augmented Dickey-Fuller test - Autocorrelation function (ACF) - Time series decomposition - Time series lagging - Time series differencing - Automatic period identification If you want to try it with Hawkular: https://goo.gl/R93k02 1. clone https://github.com/hawkular/hawkular/tree/datamining - hawkular/hawkular branch datamining 2. build with -Pdev && run 3. enable predictions preferably for every metric https://github.com/hawkular/hawkular-datamining and wait for some time (see below) 4. go to the Explorer tab, choose metric and increase forecasting horizon Data Mining is currently not able to query historical metric data from metrics due to authentication issues. However it still receives metrics from bus so it is important to enable predictions as soon as possible and wait for some time to collect data (or increase collection interval). This will be fixed in the next versions. Thanks to Jiri Kremser and UI team for helping with predictive charts. Useful links: - Docs <http://www.hawkular.org/docs/components/datamining/index.html> - REST API <http://www.hawkular.org/docs/rest/rest-datamining.html> Regards Pavol

7 years, 1 month

4
4
0 / 0

Termin gestrichen: Hawkular-Team Update - Di 26. Apr. 2016 3:30PM - 4PM (hrupp@redhat.com)

by hrupp＠redhat.com

Dieser Termin wurde gestrichen und aus Ihrem Kalender entfernt. Titel: Hawkular-Team Update This is a all-Hawkular team meeting to give updates where we are and so on. This is *open to the public*. Location: on bluejeans: https://redhat.bluejeans.com/hrupp/ or alternatively teleconference Reservationless+ , passcode 204 2160 481 You can find Dial-In telephone numbers here: https://www.intercallonline.com/listNumbersByCode.action?confCode=2042160481 RedHat internal short dial numbers are 16666 and 15555 (and probably others, depends on your location) Wann: Di 26. Apr. 2016 3:30PM - 4PM Berlin Wo: pc 204 2160 481 Kalender: hrupp(a)redhat.com Wer * Heiko Rupp - Organisator * Mike Thompson * Lucas Ponce * jcosta(a)redhat.com * amendonc(a)redhat.com * Jay Shaughnessy * theute(a)redhat.com * John Sanda * John Mazzitelli * mwringe(a)redhat.com * abonas(a)redhat.com * Peter Palaga * gbrown(a)redhat.com * Gabriel Cardoso * lkrejci(a)redhat.com * Jiri Kremser * Thomas Segismont * hawkular-dev(a)lists.jboss.org * snegrea(a)redhat.com * Simeon Pinder * miburman(a)redhat.com Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter hawkular-dev(a)lists.jboss.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie können auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen für Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empfänger Ihre Antwort auf die Einladung ändern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding

7 years, 1 month

1
0
0 / 0

Pozvánka: Discuss Inventory Sync - St 2016/04/20 3:30PM - 4:30PM (Hawkular)

by lkrejci＠redhat.com

Byli jste pozváni na následující událost. Název: Discuss Inventory Sync With the first version of the inventory sync (or rather "dump" as it exists at the moment) in inventory, I'd like to invite you to discuss its features and future directions so that we make it as useful as possible for the feed writers. https://bluejeans.com/8169978803 Kdy: St 2016/04/20 3:30PM - 4:30PM Středoevropský čas - Praha Kde: https://bluejeans.com/8169978803 Kalendář: Hawkular Kdo: * lkrejci(a)redhat.com- autor * jmazzite(a)redhat.com * jshaughn(a)redhat.com * hrupp(a)redhat.com * hawkular-dev(a)lists.jboss.org Podrobnosti o události: https://www.google.com/calendar/event?action=VIEW&eid=cTExdWdzbXR0Z3Y2M2x... Pozvánka z Kalendáře Google: https://www.google.com/calendar/ Tento e-mail na účet hawkular-dev(a)lists.jboss.org jste obdrželi z toho důvodu, že jste účastníkem této události. Chcete-li se odhlásit z odběru oznámení o této události, odmítněte událost. Případně si můžete na adrese https://www.google.com/calendar/ zaregistrovat účet Google a řídit nastavení oznámení pro celý svůj kalendář. Přeposláním této pozvánky byste mohli komukoli z příjemců umožnit, aby změnil vaši odpověď na toto pozvání. Další informace najdete na https://support.google.com/calendar/answer/37135#forwarding

7 years, 1 month

2
1
0 / 0

agent 0.17.1.Final released - prometheus support

by John Mazzitelli

Hawkular WildFly Agent 0.17.1.Final has been released - this is the first release with Prometheus support. The agent can now be told to scrape Prometheus endpoints for metric data (so it now supports DMR (WildFly/EAP) monitoring, Platform monitoring, Jolokia/JMX monitoring, and now Prometheus endpoint monitoring). See my blog on the details here: http://management-platform.blogspot.com/2016/04/prometheus-metric-endpoin...

7 years, 1 month

2
1
0 / 0

Termin gestrichen: Hawkular-Team Update - Di 19. Apr. 2016 3:30PM - 4PM (hrupp@redhat.com)

by hrupp＠redhat.com

Dieser Termin wurde gestrichen und aus Ihrem Kalender entfernt. Titel: Hawkular-Team Update This is a all-Hawkular team meeting to give updates where we are and so on. This is *open to the public*. Location: on bluejeans: https://redhat.bluejeans.com/hrupp/ or alternatively teleconference Reservationless+ , passcode 204 2160 481 You can find Dial-In telephone numbers here: https://www.intercallonline.com/listNumbersByCode.action?confCode=2042160481 RedHat internal short dial numbers are 16666 and 15555 (and probably others, depends on your location) Wann: Di 19. Apr. 2016 3:30PM - 4PM Berlin Wo: pc 204 2160 481 Kalender: hrupp(a)redhat.com Wer * Heiko Rupp - Organisator * Jiri Kremser * theute(a)redhat.com * abonas(a)redhat.com * jcosta(a)redhat.com * Lucas Ponce * Simeon Pinder * Gabriel Cardoso * snegrea(a)redhat.com * John Sanda * John Mazzitelli * lkrejci(a)redhat.com * Jay Shaughnessy * gbrown(a)redhat.com * mwringe(a)redhat.com * miburman(a)redhat.com * Peter Palaga * Mike Thompson * amendonc(a)redhat.com * Thomas Segismont * hawkular-dev(a)lists.jboss.org Einladung von Google Kalender: https://www.google.com/calendar/ Sie erhalten diese E-Mail unter hawkular-dev(a)lists.jboss.org, da Sie ein Gast bei diesem Termin sind. Lehnen Sie diesen Termin ab, um keine weiteren Informationen zu diesem Termin zu erhalten. Sie können auch unter https://www.google.com/calendar/ ein Google-Konto erstellen und Ihre Benachrichtigungseinstellungen für Ihren gesamten Kalender steuern. Wenn Sie diese Einladung weiterleiten, kann jeder Empfänger Ihre Antwort auf die Einladung ändern. Weitere Informationen finden Sie unter https://support.google.com/calendar/answer/37135#forwarding

7 years, 1 month

1
0
0 / 0

Re: [Hawkular-dev] Do not depend on Keycloak anymore

by Juraci Paixão Kröhling

Bringing this discussion to the list. Summary so far: === If all those requirements got dropped, specially "multiple organizations" and "multi tenancy", then there's really no point in having Accounts. Without the UI/self-registration/SSO, I doubt we need to depend on Keycloak. I added SSO to this list because if there will be no user interaction on Hawkular, there's no "single sign on" required there. It's still not clear to me, though, if we need to care about authorization. Are we getting calls only from "trusted" clients? Also, should we use the same user base as MiQ, or should we have a "system account" only? Having a system account might make more sense here, and we won't need to integrate with their user database. With this system account, we would act like a database: any user with valid credentials would be allowed to read/write data. We would trust the client if the client said "store this data for this tenant". Instead of tokens, we could have just system accounts. Revoking a token would mean just removing this system account. === > On 15 Apr 2016, at 14:38, John Mazzitelli wrote: > > What about agents/feeds? They aren't talking to CFME ; they are > talking directly to the Hawkular Server (or Hawkular-Metrics if in > METRICS-ONLY mode, such as in Open Shift). Is there not going to be > any Basic Auth headers anymore? If there will still need to be > authentication, then it must be the JAAS credentials and not the > Accounts tokens, I suppose. If we have system accounts, then agents would use a system account, like they would use a token. Admins are free to create one system account per agent (key/secret), or use one shared account to all agents (jdoe/password). For all "we" (Hawkular backend) care, it's all done by JAAS. In fact, if all goes well, there will be no need to change anything for the agents. And I'm considering that the auth is done by Basic auth. If we *need* to have other authentication mechanisms, we need to deviate from JAAS. On 15.04.2016 14:43, Heiko W.Rupp wrote: > Yes, that *may* require a change. Or not if we e.g. have > - accounts-keycloak > - accounts-jaas > where the latter does the mapping as a jaas provider/plugin. > But yes we need to secure the agent/server comm. And we > need to apply SSL for the product (isn't that part of http/2 anyway). So far, I don't see the need in having Keycloak, or Accounts. Securing the agent/server communication is not relevant to the discussion, as it's independent from the authentication mechanism being used. - Juca.

7 years, 1 month

3
9
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev April 2016