February 2016 - hawkular-dev - Jboss List Archives

by Juraci Paixão Kröhling

Team, Just like it was done last release, I propose the following schedule for Alpha 10. The release date is set to Feb 17th (Wed), so: - Feb 11th, Thursday: Parent, Commons and Accounts - Feb 12th, Friday: Inventory, Metrics, BTM - Feb 15th, Monday: Command Gateway, Agent, Alerts - Feb 16th, Tuesday: Hawkular Once Accounts is released, I'll be submitting a PR for the downstream components. - Juca.

8 years, 3 months

1
1
0 / 0

how long to give for peer-review

by John Mazzitelli

Once a PR is created and we ask for peer-review and merge, how long should be given to that process before we go ahead and merge the PR?

8 years, 3 months

3
2
0 / 0

Host agent ?

by Thomas Heute

With embedded agents, we lost few main features: - Ability to discover servers that are off or not (yet) instrumented - Ability to start servers remotely - Ability to report DOWN availability (other than by lack of UP) Should we reintroduce a small (optional ?) host agent ? The agent would only fulfill those tasks (+ embedded agent installer) and redirect all other tasks to the embedded agents. We can address a limited set of platforms (Linux only) to start with, and maybe use environment specific features if those exists (Like RHEV-M host agent if appropriate) WDYT ? Thomas

8 years, 3 months

7
9
0 / 0

(no subject)

by Anuj Garg

hey.. Pull request for android client https://github.com/hawkular/hawkular-android-client/pull/49 It is logging in successfully with master. but as there is issue in trigger and all at master at present, they are not coming. but when replaced key and secret and using with alpha 9 everything worked (by username password coz key/secret were creating problem there ). Implies code is working perfectly fine :)

8 years, 3 months

1
0
0 / 0

cmdgw and agent PR needs peer-review and merge

by John Mazzitelli

cmdgw PR: https://github.com/hawkular/hawkular-command-gateway/pull/51 agent PR: https://github.com/hawkular/hawkular-agent/pull/152 JIRA: https://issues.jboss.org/browse/HAWKULAR-790 I associated this with that JIRA because that JIRA is introducing a UI feature that requires it to know the current state of the statistics enabled flag on all the wildfly subsystems. These PRs provide the ability for the UI to ask the agent for that information. (NOTE: the agent PR can't be merged until the cmdgw PR is merged at which time I can take out the agent's cmdgw snapshot dependency)

8 years, 3 months

1
0
0 / 0

agent PR needs peer-review and merge

by John Mazzitelli

The following agent PR needs peer-review and merge: PR: https://github.com/hawkular/hawkular-agent/pull/151/files JIRA: https://issues.jboss.org/browse/HWKAGENT-58 Agent installer needs to be able to be told to install the agent in metrics-only mode. Requires changes to the underlying wildfly installer stuff that libor initially built.

8 years, 3 months

1
0
0 / 0

Receive data via bus from outside?

by Heiko W.Rupp

Hey, while I am pretty sure we said we do not want to receive data (Metrics, Inventory) from outside Hawkular via Bus, I wanted to make sure anyway. Do we make sure that the bus is only visible internally then (e.g. only binding to management interface)?

8 years, 3 months

2
1
0 / 0

Good article on correlation

by Heiko W.Rupp

https://medium.com/@zexxon/logs-models-and-metrics-how-and-why-they-need-... -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht München HRB 153243 Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey, Charlie Peters

8 years, 3 months

1
0
0 / 0

agent PR needs peer-review

by John Mazzitelli

Here's another agent PR that needs peer-review and merging. PR: https://github.com/hawkular/hawkular-agent/pull/150 JIRA: https://issues.jboss.org/browse/HWKAGENT-57 The issue here is that when the agent is told to shutdown by the WildFly container controller, the agent should set availability metrics to DOWN for local resources. So in the shutdown code of the agent service, it now gets a list of all configured avail metrics that need to be set to DOWN and sets them, making sure WF doesn't completely shutdown until those metrics are set (needed to do some changes around async storage to the metrics REST API - had to add a wait period just so the stop() method doesn't return until after the metrics are set - otherwise, WF will shutdown potentially before all the REST calls are made). Anyway, this doesn't fully solve the issue because there are cases when the agent's WF container dies abruptly (i.e. crashes). That's next on my todo - see https://issues.jboss.org/browse/HAWKULAR-407

8 years, 3 months

1
0
0 / 0

Use of jira trackers

by Heiko W.Rupp

Someone asked: > I thought HAWKULAR project's metrics component means Hawkular-UI > metrics component. Why is there a metrics component under > Hawkular-JIRA? We have "HWKMETRICS" which should be used instead. > Confusing. HAWKULAR is the over all jira project for Hawkular. Stuff that is needed for the overall project is recorded there. For the individual subcomponents of Hawkular, we have a jira-component and sometimes also a separate HWK* tracker. Projects can use that to track their individual issues or also breakdown of tasks that were originally recorded in HAWKULAR as a "top level" item. Users that download Hawkular and find an issue will file it in HAWKULAR and not chase the individual HWK* jira - most often because they do not know about it. Also release notes for Hakular are created from HAWKULAR jira (only) UI-specific work is recorded in the UI component of HAWKULAR -- Reg. Adresse: Red Hat GmbH, Technopark II, Haus C, Werner-von-Siemens-Ring 14, D-85630 Grasbrunn Handelsregister: Amtsgericht München HRB 153243 Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey, Charlie Peters

8 years, 3 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev February 2016