Collapsing of Repos ?
by Heiko W.Rupp
Hi,
we do have a larger number of repositories and source trees.
Now that we have narrowed down the scope of our work a bit and also
have an idea of what we need for the "core services" package, I wonder
if we can collapse repositories and source trees into larger ones.
As an example: alerts and metrics could go together into
hawkular-metrics and the forwarding of data to alerts could be
done with Java method invocation.
What else could be done here?
9 years, 7 months
accounts, tenants, the agent
by John Mazzitelli
Now that Accounts is getting taken out, how is the agent to determine its tenant ID?
The agent needs to know its tenant ID when inserting data into Hawkular Metrics.
Right now, the agent makes an explicit http call to the Accounts URL to obtain the tenant of its user. If Accounts goes away, the only thing left that I can see is to make required the agent attribute "tenantId" in standalone.xml configuraiton of the agent subsystem.
Is that correct? There is no other way to get the tenant ID of a user now, I guess.
(for what its worth, tenant IDs are important in the Open Shift use-case)
9 years, 7 months
Hawkular-Archive - New Org
by Stefan Negrea
Hello,
I would like to propose a new organization in Github to host projects that
no longer receive development. "Hawkular-Archive" seems a good name for
this purpose. The goal is to keep the main Hawkular org focused on
important projects and at the same time preserve work that was already done
but away from the main organization.
>From a quick look at the current organization here are two repositories
that can be moved right away: hawkular-metrics-openshift (Openshit 2.x
cartridge for Hawkular Metrics 0.2.7 or earlier) and hawkular-bus (code
moved to another repo). Am I am sure we can find other repositories to
move.
In the long run we can develop some criteria for archiving projects but for
now we can just do a one-time major cleanup.
Any repositories that should be archived right away? Any other suggestions
for a name? Any thoughts on the idea in general?
Thank you,
Stefan Negrea
Software Engineer
9 years, 7 months
Hawkular-BTM UI Details
by Preethi Kannan
Hi Team,
I am analysing Hawkular-BTM and trying to record business transactions for various applications.
I wish to get more detail about the various tabs we have in the Hawkular-BTM UI like (Candidate,Active,Disabled,Ignored).
It would be great to know the various features and use Hawkular to a greater extent.
Thanks,
Preethi
::DISCLAIMER::
----------------------------------------------------------------------------------------------------------------------------------------------------
The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only.
E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted,
lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents
(with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates.
Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the
views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification,
distribution and / or publication of this message without the prior written consent of authorized representative of
HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately.
Before opening any email and/or attachments, please check them for viruses and other defects.
----------------------------------------------------------------------------------------------------------------------------------------------------
9 years, 7 months
Inventory 0.15.1.Final released
by Lukas Krejci
Hi all,
Inventory 0.15.0.Final had a serious performance regression in the bulk
insert. The 0.15.1.Final fixes that problem and the performance should now be
on the same order of magnitude as previously (still 0.15.x is slower on
creates, updates and deletes than 0.14.x thanks to the new identity hashing
functionality).
Please update as soon as possible,
Thanks,
--
Lukas Krejci
9 years, 7 months
Agent - EAP Domain mode support
by Thomas Heute
The question is likely for Mazz, but I wanted to check how we will support
the WF domain mode.
As far as I understand, we are now able to run the agent in the host
controller but wanted to know a bit more on how we expect the setup to be
(one agent on the host controller for the whole domain ?)
Also I wanted to ask if older versions of the app server could be supported
or only WF 10 ? (in particular in the context of EAP7/EAP6 support)
Thomas
9 years, 7 months
Is there the feature to provide timegap between ripple restart of WildFly(JBoss EAP) cluster in Hawkular?
by Jong Seok Won
Hi all~,
Is there the feature to provide timegap between ripple restart of
WildFly(JBoss EAP) cluster in Hawkular?
If there is no feature, I'm curious there is a roadmap for this feature.
Actually, this kind of feature is useful in a production environment.
I've already checked RHQ(JON) however there is no for ripple restart.
RHQ(JON) provides below in restart operation page of Group menu.
1. "Execute: in the order specified below
2. "Halt on Failure?"
Thanks in advance.
--
Kindly Regards,
Ted Won
9 years, 7 months
communty distribution question
by Jay Shaughnessy
This relates to the "[Hawkular-dev] Future Packaging of Hawkular"
thread. I started this thread to discuss a specific scenario that I
don't know how to handle.
In addition to the components listed in that e-mail, there are a few
other things in the Hawkular repo that weren't mentioned. For example,
we have pinger and we have the inventory-event bus listener. I point
out those two because I think they now exist solely to support the
community UI. URL monitoring and Alert Center do not carry over to
MIQ. With respect to the alert center we have out-of-box trigger
definitions that are currently still active and are defined specifically
to support the UI Alert center in Hawkular classic. And so we have a
situation where code I would otherwise remove may need to exist to
support the UI in the community distribution. Do we really want to
keep a community-edition UI and the server-code that *only* supports
what it does? If we remove it it will severely cripple the UI. But I
fear that the UI will anyway quickly deteriorate unless we make
concerted efforts to maintain compatible server code. Even today I
think the UI is starting to falter. I'm not sure but when I tried to
use the master version today to perform a deployment, it just hung.
So in line with Juca's questioning, what sort of effort do we put into
the community UI? A lot, and keep it working as best as we can and
ensure we mark server code that is relevant to community UI support?
None, and just make the server code be the headless provider it needs to
be to support MIQ, or something in the middle (which usually ends up
being a waste of time).
9 years, 7 months
