March 2016 - hawkular-dev - Jboss List Archives

by Austin Kuo

Hi, all. This is Austin. I've been trying to understand how the inventory in agent works. As far as I understand, an inventory is a graph, and the agent sends the graph to the hawkular server with some kind of format. Such that the hawkular server can answer queries with the data that the agent sends. I have a few of questions: 1. What are the various protocols for(dmr, jmx, platform)? 2. And there's Resource and ResourceType, each of them holds a graph, what's the relation between them? Are they isomorphic and each node of ResouceType annotates the corresponding Resource node? Thanks!

9 years, 11 months

4
4
0 / 0

Checkstyle rules

by Lucas Ponce

Hello, If new checkstyle rules are introduced like this: Using the '.*' form of import should be avoided - org.hawkular.alerts.actions.api.*. I am not to enter in a discussion if this is valid or not, but please, then also modify the IDEs helpers or document the change in the settings of the two main IDEs used in the project. Some IDEs by default uses the .* import when there is a number of imports. A documentation in the settings will save time. Thanks, Lucas

9 years, 11 months

2
1
0 / 0

Hawkular Parent 38

by Peter Palaga

Hi *, The new version 38 [1] brings just two minor changes: * upgrade to hawkular-build-tools 15 that now contans apidoc.groovy [3] script for generating REST API documentation from swagger by Pavol. * Move gmavenplus-plugin executions to a dedicated profile so that it is not active by default and the build can run faster for all projects which do not contain any Groovy code [4]. Projects that contain Groovy code will have to activate the plugin by adding <groovy.test>true</groovy.test> to their properties. Note that the previous Parent version 37 contained upgrades to Cassandra 3.3 and Driver 3.0.0. It looks like no component upgraded to v37 yet. I have a PR [5] ready that upgrades to Parent 38 and c* 3.3 in Commons. According to Juca, no major problems are expected in Accounts, while it is fully unclear if Titan will be ready to work with c* 3.3 in Inventory. Best, Peter [1] https://github.com/hawkular/hawkular-parent-pom/commits/38 [2] https://github.com/hawkular/hawkular-parent-pom/commits/37 [3] https://github.com/hawkular/hawkular-build-tools/commit/ec64970d15821d2d9... [4] https://github.com/hawkular/hawkular-parent-pom/commit/72381084614a5dde95... [5] https://github.com/hawkular/hawkular-commons/pull/53

9 years, 12 months

5
6
0 / 0

Alpha 11 - Are you ready?

by Juraci Paixão Kröhling

Team, Now that BTM is integrated and the fixes from Alpha 10 are fixed, we are ready to release Alpha 11. Besides BTM, a couple of people asked for other features/fixes to be included in Alpha 11. So, if you still have something pending that you'd like to see on Alpha 11, do let me know. If nothing is said until Monday morning (CET/UTC), I'll go ahead and start releasing components for Alpha 11. As there were changes in the Commons package, we'll probably need to release all components. The planned schedule looks like this: - Morning of Feb 29th, Monday: Parent, Commons and Accounts - Afternoon of Feb 29th, Monday: Inventory, Metrics, BTM - Morning of Mar 1st, Tuesday: Command Gateway, Agent, Alerts - Afternoon of Mar 1st, Tuesday: Hawkular Also, please do test the parts that concerns your work. - Juca.

9 years, 12 months

5
7
0 / 0

bug in agent - inventory bulk payload bad?

by John Mazzitelli

Jirka - did you file an agent JIRA on this? This is code that was working in the past (no one has touched it for a while AFAIK) so I'm not sure what broke. Sounds like it has to do with that bulk payload builder in the agent. ----- Forwarded Message ----- > From: "Jiri Kremser" <jkremser(a)redhat.com> > * bulk insert that is done by the agent reports some relationships > multiple times (it's a bug on Agent side), I made the inventory immune to > this so that only the first record is taken into consideration and the rest > is ignored (holds for entities as well as relationships)

10 years

1
0
0 / 0

Status Report - Week 9 2015

by Gary Brown

Accomplishments and key updates: - HWKBTM-342 Fix minor formatting inconsistency between BTM standalone and Hawkular integration UI for the APM page. Also integrated UI dropdown defaults were incorrect on the APM page. - Test and released 0.7.1.FInal of BTM, and merged HWKBTM-312 to integrate BTM into Hawkular. - Test and release BTM 0.7.2.Final with changes required by parent 36 (relocation of modules artifacts). - Completed work on HWKBTM-268 to derive communication (latency) information and provide a REST endpoint for obtaining graph nodes/links for creating a graphical representation of the communication between distributed services. - HWKBTM-353 When obtaining communication details, need to identify the initial fragment as a client (previously based on same uri as the consumer) - ENTESB-5040 Work with GSS to investigate and fix RTGov/Swyd classpath conflict around drools - Trying out node.js as possible next instrumentation environment. Found an interesting project (https://github.com/ValYouW/njsTrace) that can instrument a nodejs app - quite flexible but doesn't give access to all the information we would require, but demonstrates the approach that can be taken to achieve the desired results Next steps: - HWKBTM-340 More accurately calculate the completion time across a business txn with multiple fragments. - More node.js investigation as a background task Risks: - none Asks for Thomas: - none

10 years

1
0
0 / 0

Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1

by Michael Foley

A single instance of the following meeting has been modified: Subject: Discussion, Planning, and status on Testing Openshift & Hawk-Metrics Integration for Openshift 3.1 Organizer: "Michael Foley" <mfoley(a)redhat.com> Location: Bluejeans http://www.bluejeans.com/mfoley51 Time: Wednesday, March 2, 2016, 3:00:00 PM - 3:30:00 PM GMT -05:00 US/Canada Eastern Required: pruan(a)redhat.com; mmahoney(a)redhat.com; vnguyen(a)redhat.com; snegrea(a)redhat.com; jsanda(a)redhat.com; mwringe(a)redhat.com Optional: jon-qa-list(a)redhat.com; jboss-on-team(a)redhat.com; hawkular-dev(a)lists.jboss.org *~*~*~*~*~*~*~*~*~* Hi, Let's have a discussion and planning session on testing Openshift & Hawkular Integration! Let's use this etherpad to coordinate the discussion -->> http://pad.engineering.redhat.com/Management-nextAndOpenshiftTestPlanning 5 Point Plan for Openshift 3.1 GA * Unit tests .... owned by Hawk-Metrics developers * Integration tests ... owned by Hawk-Metrics developers and Hawk-Metrics QE * Performance CI on Hawk-Metrics (this one is actually new and was not discussed on Wednesday , but I now see it makes sense) * Functional Integration tests on Hawk-Metrics latest + Openshift Origin latest * Funtional/UI .... Cucumber/Ruby tests ...owned by Openshift QE * Functional/Rest ... Cucumber/Ruby tests ... owned by Openshift QE * Performance & Scalability .... owned by Openshift QE Regards, Michael Foley QE Supervisor, Middleware BU

10 years

1
0
0 / 0

Upgrading Hawkular Metrics to Cassandra 3.x

by John Sanda

Since Hawkular is still primarily in development mode upgrading dependencies, including databases, is fairly painless. Metrics 0.8.0 however was included in OpenShift 3.1, which means upgrading Cassandra in Metrics is going to be more involved than upgrading the parent pom and upgrading our dev environments, e.g., changing ccm cluster. The following is a brief description of the steps that need to be performed, Run nodetool drain Shut down the node Back up configuration and data files Install new version of Cassandra Apply configuration changes (from old version) to new version. This would include files like cassandra.yaml, cassandra-env.sh, etc. Start the node Run nodetool upgradesstables Repeat for each node in the cluster These steps can be performed as a rolling upgrade; however, no application schema changes should be made until the upgrade is complete and until cluster reports schema agreement. With respect to OpenShift, how much of this needs to be automated? Matt, can you share some insights here? I would like to figure out sooner rather than later how much work we think is involved. Thanks - John

10 years

2
2
0 / 0

GSOC - 2016 Hawkular-Android Client

by k.krish＠yahoo.com

Dear All, I am Krishna, I am currently pursuing my Masters in Computing at NUS - National University of Singapore. I came across the project Hawkular-Android Client and I am very much interested in working on the project. I have participated and completed the GSOC - 2015 Program with the community Syslog-ng Project. I have developed a Syslog-ng Server monitoring application for Android. The link for the project - GSOC 2015 - https://github.com/Krishna41/Syslog-ng-Monitor-Android I have also created a UI Testing Project with Robotium Framework. Test Project Link - https://github.com/Krishna41/Syslog-ng-Monitor-Android-Test I kindly request you all to guide me provide suggestions for moving forward. I am very much excited and looking forward to working with JBoss Community. Thanks and Regards,Krishna.

10 years

2
1
0 / 0

ManageIQ / Hawkular - some questions

by Lucas Ponce

Hi, As commented in the IRC I am going to prepare some questions about the $SUBJECT. I have spent a couple of days reviewing ruby and starting to look into ManageIQ architecture where Hawkular will be a Middleware provider. Some my preliminar doubts (perhaps this was discussed in a different thread, so please, point me to that if I missed it): * Where will be stored metrics and inventory ? That info should live in the provider (owner of that information) and copied to ManageIQ repository ? Or on the contrary, ManageIQ will be the owner of that info and the provider is a technical cache. * How information of the providers is collected ? In some preliminary meeting I understood that agents or whatever mechanism that collects information of the middleware domain should be sent to the provider. Is this valid ? or the architecture is that in the future all agents should be managed directly into ManageIQ ? I guess that this is some kind of hybrid architecture as there will be always external provider (thinking on Amazon or other domain) that is managed by ManageIQ but the provider is the owner of the info. * Alerting This perhaps brings to me as I have personal interest on this topic. I see that ManageIQ has alerting features, so it can define alerts and group them in policies into resources in some way. >From what I see and related with the previous information, who is the owner of the information ? provider or ManageIQ ? I can see that ManageIQ can be the owner of alerts definitions but perhaps the provider can have their own pre-configured alerts and feed ManageIQ. (I am thinking again in how this works for the Amazon model, I'm sure that Amazon cloud will have their own alerting definitions, perhaps an hybrid approach can be used here). Also, I have the same doubt with Events, one of the major features of Hawkular Alerts was to manage events in a generic way, so, if the provider if the owner of the metrics/inventory it makes sense in a first approach that it can be the owner of some of middleware events (perhaps Events might have several meanings here, it happened to us in Hawkular and also with the ManageIQ integration that term should be revisit to be sure that we are talking about same concept). * Roles Are we going to provide strong role profiles ? for example a middleware role, that only can see the Middleware information without any access to cloud/infrastructure. * API One of the feedbacks I have heard from people about Hawkular and with experience with OpenShift/CloudForms is the use of the API to personalize and automate powerful tasks (for example, feeding events generated by an application, not just for the container). How API should work in this case ? All API should be proxied/routed by ManageIQ or accesing to the provider API is valid ? (Again, thinking on external providers like Amazon makes me wonder what is the goal of this). I have more doubts (perhaps more related of the global architecture as I am not yet familiar with it) but I think these 5 topics are high level and it could help to understand better the context. (Again, perhaps these ones are discussed/written in other thread, and are obvious, but I couldn't find them). Thanks, Lucas

10 years

3
2
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

hawkular-dev March 2016