HEADS UP: Hawkular Services is now on Inventory.v3
by Heiko W.Rupp
Hey,
sorry for not sending this email earlier.
Hawkular-services has in master and also release 0.36
switched to new Inventory.v3, which is Inventory on Metrics.
The old Inventory component (that uses a relational DB)
has been removed.
The Ruby client gem has been bumped to version 3.0.1
to cater for this change [1].
Agent(s) 1.0.cr1 are also using this new Inventory code.
Joel is currently preparing a show&tell to walk us through
the new Inventory version and will also update docs on
hawkular.org accordingly.
My thanks goes to everyone involved to make this happen
and especially to Joel who did the majority of the work.
Heiko
[1] And HawkFX in master is also using that gem version now.
--
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, Michael O'Neill,
Eric Shander
8 years, 10 months
bug in MiQ / javaagent integration - needs to be fixed
by John Mazzitelli
There is a problem with the new Java agent and MiQ.
This problem is because the agent is no longer in WildFly's DMR tree of resources (because only WildFly subsystems are in the DMR tree).
Look here:
https://github.com/hawkular/hawkular-agent/blob/master/hawkular-javaagent...
So when the agent (java or subsystem agent, doesn't matter) is monitoring EAP over the DMR management interface, that's the metadata it uses. You can see we inject two non-WildFly attributes (immutable and in-container) under the WildFly Server type. But these come from the agent - hence why you see:
path: /subsystem=hawkular-wildfly-agent
But when running this as a java agent, that resource doesn't exist - there is no agent subsystem anymore. So the immutable and in-container attributes end up not getting defined under the WildFly Server resource.
The problem is MiQ looks for those attributes under WildFly Servers to determine if the agent is in immutable mode and if its running in a container.
In effect, we are trying to inject under a WildFly Server resource completely unrelated information (immutable and in-container attributes) - those are related to the AGENT, not the WildFly Server itself (i.e. you won't see those two attributes if you use the jboss-cli under the root "/" resource).
We probably should have had MiQ examine the AGENT resource for this (since "immutable" and "in container" are attributes on the agent, not the server). And we shouldn't define "immutable" and "in container" under the WildFly Server resource because that is depending on the fact that the agent is running as a subsystem. As a Java Agent, as you see, those attributes will never show any values because there is no agent subsystem.
MiQ can look at the agent attributes because the agent itself exposes immutable and in-container (because they ARE actual properties the agent has) in inventory. Under the agent resource in inventory you will see these:
https://github.com/hawkular/hawkular-agent/blob/master/hawkular-javaagent...
Note that we DO expose immutable and in-container under the Agent JMX resource in inventory also - and it has the same resource name as the subsystem agent (the name as you will see it in inventory):
https://github.com/hawkular/hawkular-agent/blob/master/hawkular-javaagent...
Hence why I think the best/easiest thing to do is get MiQ to examine the attributes on the resource where they really belong (and we should remove them from the WildFly Server type).
8 years, 10 months
OpenShift OAuth authentication and authorization for Hawkular APM
by Lars Milland
Hi
It would be really great if a functionality for Hawkular APM could be
found/established, matching the one that exists for Hawkular Metrics wise
for OpenShift, where the metrics are stored per tenant/namespace, and then
Hawkular security wise is integrated to the OAuth based security model of
OpenShift.
Is that a requirement/feature that have been considered? Or would it maybe
already be possible to integrate the Hawkular APM components to OpenShift
OAuth based security. Even if the Hawkular APM storage and security model
would not fit to the fully multitenant way of OpenShift, if just the
security model of a Hawkular APM installation could be connected to the
OpenShift OAuth model, then one Hawkular APM instance could be setup with
"service account tokens" used for sending metrics to the instance, and users
could log into the Hawkular APM UI with again OpenShift OAuth managed
credentials, mapped to roles coming from the OAuth ticket. Much the same way
that the security model of the OpenShift integrated Jenkins works - see:
https://github.com/openshift/jenkins-openshift-login-plugin
The current security model of APM is rather limited as far as I understand -
and based solely on a single manually fixed username/password for both
contributing application performance metrics/log entries, and same for the
Hawkular APM UI.
Best regards
Lars Milland
8 years, 10 months
Add functionality to change password.
by Mohammad Murad
Hello
I'm a contributor to the Android Client of Hawkular.
On the Gitter channel I suggested that we should give the user an option to
change the password. Currently there is no REST API for that. This will be
very helpful if the credentials of the user are compromised.
Heiko W. Rupp asked me suggest this here.
If I can help with this, please let me know.
Regards
M. Murad
GitHub <http://github.com/free4murad>
8 years, 10 months
Hawkular Agent 1.0.0.CR1 has been released - inventory in metrics
by John Mazzitelli
Hawkular Agent 1.0.0.CR1 has been released.
This includes the new "inventory in metrics" feature - Hawkular-Inventory is no longer used to store inventory, the inventory is now stored in Hawkular-Metrics within Cassandra.
This is a *significant* change and needs people to beat on it heavily before we can claim victory (hence why it has the CR1 designation and not Final).
So, please grab it and use it when you need to use an agent.
If you find any bugs, please submit HWKAGENT JIRAs at https://issues.jboss.org/projects/HWKAGENT
--John Mazz
[this message was sent on April 24, 2017 at 9:19pm EDT]
8 years, 10 months
Proposal for Query DSL
by Benjamin Heiskell
Hey all,
I recently deployed Hawkular because I found its scaling model appealing.
It has been working well for our basic monitoring usage when combined with
Grafana.
One of my consumers is trying to graph KPIs that involve cross-metric
mathematics like sums, division, and moving averages (i.e., post-ingress
transformations). I looked into how to accomplish this with Hawkular, but I
didn't see any obvious way to do it. The stats endpoint seems to only
support aggregations on a single metric/tag at a time. I'm finding that we
can't visualize these metrics the same way you can with other TSDBs like
Graphite/Prometheus.
I did a little research, and found Heiko Rupp's blog post on HawkFX where
he seems to already be exploring this idea [1]. Perhaps the query language
item on the 2017 road map refers to incorporating this?
I would like to assist in developing this feature. Given that there is
already a tags DSL, it seems like it would make sense to extend that to
support metric transformations.
Grafana is also considering adding this to Grafana itself, but it doesn't
look like the ticket has any traction [2]. Additionally, shipping
potentially megabytes of data to Grafana (or the user's browser) to
aggregate doesn't seem ideal.
I documented a few TSDB DSLs styles here [3].
What do you all think?
Thanks,
Ben
[1] http://pilhuhn.blogspot.com/2016/09/computed-metrics-for-hawkfx.html
[2] https://github.com/grafana/grafana/issues/3677
[3] https://gist.github.com/bheiskell/25af2543ee8588f70895b0311ef291d3
8 years, 10 months
OpenShift - An error occurred getting metrics.
by Anton
Hello
I have tried to run Hawkular in both `oc cluster up` and OpenShift,
different versions of both.
The documentation for `oc cluster up` says (
https://github.com/openshift/origin/blob/master/docs/cluster_up_down.md#i...)
that by using the `--metrics` parameter, metrics is installed.
Its a similar story when installing OpenShift using Openshift-ansible.
However, in both cases, when logging into the OpenShift webconsole I see an
error message saying:
An error occurred getting metrics. Open Metrics URL | Don't Show Me Again
It would seem there is more to correctly installing Hawkular metrics than
just using the parameter.
What else needs to be done? And is it possible get the additional info
added to the documentation for openshift-ansible and `oc cluster up`?
Thanks
8 years, 11 months
test
by John Mazzitelli
I'm sending this on April 11, 2017 at 4:03 PM EDT
Let's see how long it takes to get posted.
8 years, 11 months
