Metric under Resource Type
by Austin Kuo
Hi,
I posted my feed, resources and metrics to inventory with /bulk api.
But the errors shows:
"errorMsg" : "Entity of type 'Metric' cannot be created under an entity of
type 'Resource'."
Why is this not allowed since I can do it with normal create entity api?
How can I create a metric under a certain resource with bulk api?
Thanks!
10 years
deploy / undeploy / remove
by John Mazzitelli
(This is a long email - it is for people involved in deploying applications via the Hawkular WildFly Agent. If you are writing UI code to deploy/undeploy, I suggest you read it. Send questions/comments - because I'm not even sure if I understand everything 100%)
I just realized why there is confusion regarding how to tell the agent to deploy/undeploy/remove applications.
There are different operations on different resources that do apparently the same thing. But I think this is mainly due to the fact the agent is trying to support both standalone and domain modes and to make it easier on the clients.
On the "WildFly Server" resource (which is the standalone server), these operations are defined by the agent:
<operation-dmr name="Deploy" internal-name="deploy"/>
<operation-dmr name="Undeploy" internal-name="undeploy"/>
On the "Host Controller" resource (which is only in domain mode), there are these same two operations defined.
So, you can deploy an application through the "WildFly Server" (standalone mode) and "Host Controller" (domain mode) - you need to pass in content when you do this, hence why DeployApplicationRequest JSON has to be used.
But notice you can also undeploy an application through those top level resources as well. You do this via UndeployApplicationRequest JSON.
Why don't we use ExecuteOperationRequest JSON here but instead require these two special JSON commands? Because there is no "deploy" or "undeploy" DMR operations on those wildfly resources (i.e. the top level server or host controller). However, there are several deploy/undeploy related DMR operations - like full-replace-deployment, upload-deployment-bytes, replace-deployment, etc. But rather than force the UI clients to have to know about all of these, the agent provides just the simple "Deploy" and "Undeploy" which do what you'd expect them to do. We make it easy by providing some flags in the DeployApplicationRequest JSON to let you say if you want it enabled or not and the agent will always force the deployment (that means, if there was already a deployment, the new deployment replaces the old). So the client doesn't have to fool around with the different combinations ("does this deployment already exist? No? Then just send in the content. Do you want it enabled? Deploy it, too. Yes, deployment already exists? Then send a undeploy command first, then send a remove command, then send a deploy command - or whatever WildFly wants you to do, I'm not even sure").
The agent is using the new wildfly maven core API to do the deploy and undeploy - so its very easy to wrap that stuff around our Deploy/Undeploy stuff - we let that library deal with all the details on how to do this. This, again, is why we don't use ExecuteOperationRequest - because if we did, the CLIENT would have to do all the stuff this wildfly maven core API does to get content to be deployed.
OK, but it gets more confusing because now if you look at the deployment resources, there are ANOTHER set of operations dealing with deploy/undeploy and these DO USE ExecuteOperationRequest JSON to invoke them (because these really do just pass through to the WildFly management controller and execute as is).
For example, on any deployment inside a standalone server you will see these:
/deployment=hawkular-rest-api.war/:read-operation-names
{
"deploy",
"redeploy",
"remove",
"undeploy",
}
Very confusing to have "deploy" on an deployment!! It is already deployed! I don't fully understand this, but I think this is to deploy an application whose content is uploaded but is NOT enabled. You'll see that deployment resource exists in the server but its not "enabled" because it isn't deployed. You "enable" it by deploying it.
And you'll see here you can redeploy the app, remove it (that removes the content entirely I believe - I think the entire deployment resource goes away when you do this), and undeploy (which to me means "disable").
This is why you will see a separate set of deployment related operations defined in the agent's "Deployment" resource type:
<operation-dmr name="Redeploy" internal-name="redeploy"/>
<operation-dmr name="Remove" internal-name="remove"/>
<operation-dmr name="Undeploy" internal-name="undeploy"/>
Very confusing indeed, but these are meant to be executed via the ExecuteOperationRequest JSON and they map one-to-one to the WildFly's operations that I showed above. Note there is no "Deploy" that we map - there is no reason for that other than it probably didn't make sense to us to add it. And I'm not even sure if the client should be executing these operations IF IN DOMAIN MODE! You should be going through the host controller to deploy and undeploy applications when in domain mode.
Clear as mud?
So the next question is - which ones should we be using? Send ExecuteOperationRequest JSON to the "Deployment" resource itself? Or (Un)DeployApplicationRequest JSON to the top level Server/HostController?
To my mind, we should be using the (Un)DeployApplicationRequest JSON on the top level servers. I am almost thinking we should remove the <operation-dmr> definitions for the Redeploy/Remove/Undeploy on the Deployment resources themselves - you really should only be using those when in standalone mode (so your client now has to know to only call them if the server is in standalone mode) and it just adds a second way to do something which makes it confusing to know which to use.
I think there should be a design meeting with all the involved parties (developers, UI design, requirement authors) so we can figure out what we really need. I know this is in the PRD but quite honestly that's like reading the fine print of a legal document and my eyes glaze over before I finish the first paragraph.
10 years
Hawkular Metrics 0.18.0 - Release
by Stefan Negrea
Hello Everybody,
I am happy to announce release 0.18.0 of Hawkular Metrics. This release is
anchored by performance enhancements and a new internal job scheduler.
Here is a list of major changes:
1.
*InfluxDB API - REMOVED*
- The InfluxDB compatibility API has been removed from the code base.
- This was an addition to make project integrations easier. As the
REST interface matured, the role of the InfluxDB compatibility interface
was reduced only serve as the Grafana interface. With the release of the
native Grafana plugin, this was no longer needed.
- For more details: HWKMETRICS-431
<https://issues.jboss.org/browse/HWKMETRICS-431>
2.
*Fetching Stats Data - Multiple Metrics - Experimental*
- Prior to this release, it was possible to only fetch stats for a
single metric type at a time. This release added POST
/metrics/stats/query endpoint that allows querying for mixed type
stats for multiple metrics.
- The endpoint accepts a list of metrics ids and allows filtering by
providing start time, end time, sort order and limit, as well as the
typical stats options such as bucket duration, number of buckets, or
percentiles.
- For more details: HWKMETRICS-424
<https://issues.jboss.org/browse/HWKMETRICS-424>
3.
*Performance Enhancements*
- All the JAX-RS handlers are now singletons. This reduces the GC
pressure and was relatively simple change since the code was completely
stateless. The change lead to a significant performance
increase. For more
details: HWKMETRICS-437
<https://issues.jboss.org/browse/HWKMETRICS-437>
4.
*Job Scheduler - New Implementation - Experimental*
- The new internal job scheduler is by far the biggest contribution in
this release.
- This is the foundation for a number of features that will make
their way into upcoming releases; a few examples are metric aggregates,
adjustable data retention, or complex data purges.
- The implementation keeps the Hawkular Metrics server stateless so
scaling will be just as easy going forward, with zero additional
configuration.
- The job scheduler will be used only for internal tasks.
- For more details: HWKMETRICS-360
<https://issues.jboss.org/browse/HWKMETRICS-360>, HWKMETRICS-375
<https://issues.jboss.org/browse/HWKMETRICS-375>
*Hawkular Metrics Clients*
- Python: https://github.com/hawkular/hawkular-client-python
- Go: https://github.com/hawkular/hawkular-client-go
- Ruby: https://github.com/hawkular/hawkular-client-ruby
- Java: https://github.com/hawkular/hawkular-client-java
Release Links
Github Release:
https://github.com/hawkular/hawkular-metrics/releases/tag/0.18.0
JBoss Nexus Maven artifacts:
http://origin-repository.jboss.org/nexus/content/repositories/public/org/...
Jira release tracker:
https://issues.jboss.org/browse/HWKMETRICS/fixforversion/12330870
A big "Thank you" goes to John Sanda, Thomas Segismont, Mike Thompson, Matt
Wringe, Michael Burman, and Heiko Rupp for their project contributions.
Thank you,
Stefan Negrea
10 years
inventory sync and resource configuration
by John Mazzitelli
(sending to hawkular-dev in case anyone is or planning to use inventory sync):
Lukas,
I found the problem I was having with inventory sync:
https://issues.jboss.org/browse/HWKINVENT-195?focusedCommentId=13274699&p...
If you have resource config in the json, it fails.
Can you look at that Java code I'm using and make sure its right? The Blueprints all create fine and the JSON is generated without problems, so I assume it is all correct. But maybe the server-side is expecting a different way of specifying it??
--John Mazz
10 years
Approach for firebase push notification
by Anuj Garg
Hello all,
I was doubtful if we gonna provide apk of android client of hawkular
through Google play store or user will have to compile for themselves. I
assume the case to be of play store.
And if that is the case then clients can not use their own google account
to setup push notifications for alerts as configration file is needed to be
inside apk.
I suggest that hawkular can provide one instance of firebase account for it
and all the hawkular servers will use the same.
With the workflow I suggest, there will not remain the need of setting up
unified push server to provide notification.
Steps :-
- With any user creation on any hawkular serve, there will be created a
32 Byte ID that we can assume to be unique.
- Any client that sign in to that user will retrieve that string and
will register to that as topic subscription.
- When ever a new alert is created. It will fire a HTTP request to
Firebase with unique id as toopic and Server key provided by hawkular
inbuilt.
- Rest work of manupulating the recieved alert will be handled on client
side.
Please write your views on this.
Thanks
Anuj Garg
10 years
Hawkular Services 0.0.7.Final released
by Juraci Paixão Kröhling
Team,
Hawkular Services 0.0.7.Final has just been released.
This version contains updates for Alerts, Commons, Inventory and Metrics.
As the previous distributions, the Agent has to be configured with an
user. This can be accomplished by:
- Adding an user via bin/add-user.sh like:
./bin/add-user.sh \
-a \
-u <theusername> \
-p <thepassword> \
-g read-write,read-only
- Changing the Agent's credential on standalone.xml to the credentials
from the previous step or by passing hawkular.rest.user /
hawkular.rest.password as system properties (-Dhawkular.rest.user=jdoe)
You can find the release packages, sources and checksums at GitHub, in
addition to Maven:
https://github.com/hawkular/hawkular-services/releases/tag/0.0.7.Final
Shortcuts for the downloads:
Zip - https://git.io/v6Jxg
tar.gz - https://git.io/v6Jpk
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
10 years
