how to use the installer from command line
by John Mazzitelli
I'm just sending this to document it for myself :) but this could be useful to others...
This is a quick way you can download the agent installer and install it in a WildFly server instance from a console:
1) Download the installer from a running Hawkular instance, using curl's --user option to pass in the Hawkular credentials:
curl --user jdoe:password --data 'managed-server-name=YourManagedServerName&username=jdoe&password=password' --remote-name --remote-header-name --url http://localhost:8080/hawkular/wildfly-agent/installer
This connects to the Hawkular Server with the --user credentials and downloads a pre-configured installer and stores it under the file name "hawkular-wildfly-agent-installer.jar" (that's what --remote-name and --remote-header-name magically does). When you run the installer, it will install an agent that will connect to Hawkular using jdoe/password credentials as specified by username=X&password=X (those credentials are stored inside the installer; there is a way to ask the installer to encrypt those credentials so it isn't stored in plain text, but I won't get into that here). It will use the name "YourManagedServerName" when identifying WildFly resources that it stores in inventory (see managed-server-name=)
To run the installer, get the absolute directory name of your installed WildFly server where you want the agent installed (for example: /opt/wildfly) and pass that in as a command line option to the installer like this:
java -jar hawkular-wildfly-agent-installer.jar --target-location=/opt/wildfly
That's it. Your agent is installed. Next time you run that WildFly instance, the agent should run, connect to Hawkular Server, and begin monitoring and reporting inventory.
There is more that can be done. I won't get into details here but you can download the installer with that target-location already preconfigured (if your agents are all stored in the same location like /opt/wildfly, it might be easier to just preconfigure the installer to always use that and not have to pass it in each time when executing the installer). You can encrypt the passwords so they are stored in the installer in an encrypted form. You can use hawkular-account tokens rather than username/passwords for the agent (so the agent can connect to hawkular server using a token and not a user/pass). You can have the agent disabled by default when installed in case you don't want it running yet. You can define SSL credentials if you want the agent to talk to hawkular server over SSL/https. The installer can be configured in all these ways either when you download or even afterwards (you can pass in your own installer configuration file so customize it however you want).
8 years, 3 months
agent can now report when the server needs to be reloaded/restarted
by John Mazzitelli
I released a new command-gateway and wildfly-agent today. The agent can now report when a WildFly server needs to be restarted or reloaded in order to pick up changes. There is a server-state resource config property on the WildFly server resource, and when the UI sends a websocket request to do something, it will get back a server-refresh-indicator in the websocket response if a restart or reload is required.
8 years, 3 months
Hawkular Metrics 0.11.0 - Release
by Stefan Negrea
Hello Everybody,
I am happy to announce release 0.11.0 of Hawkular Metrics. This is a large release anchored by query API enhancements, large under-the-cover refactoring of the metric models, and support for deploying the project on Wildfly 10.
Here is a list of major changes in this release:
1) Query API Updates
* Limit and Sort Order for raw data queries (HWKMETRICS-334, HWKMETRICS-62, HWKMETRICS-51)
- limit and order parameters are now available for raw data queries on all metric types
- limit - integer representing the maximum number of raw data points to be returned
- order - either ASC or DESC and based on the timestamp of the data point
- if both are specified than limit is applied from the start of the sorted list
- for defaults and additional details please visit:
https://github.com/hawkular/hawkular-metrics/blob/release/0.11.0/api/metr...
* Ability to query all metric raw or aggregate metric data (HWKMETRICS-331)
- fromEarliest query parameter was added to allow querying for all available data for a metric
- this allows querying all data without specifying start and end
- data retention for the metric is taken account, so the max time span is from `now` to `now - data retention`
* Fixed the url for querying rate data across multiple metrics (HWKMETRICS-332)
* Filtering metrics by id (HWKMETRICS-234)
- with tag filtering enabled, it is now possible add id filtering via id parameter
- id parameter supports regex
2) Internal Updates
* Model refactoring (HWKMETRICS-326, HWKMETRICS-323)
- this was a large effort to consolidate the internal domain model without changing any of the user APIs
- this change will help the documentation efforts for future releases as well as a consistent data structure for the REST APIs
3) Hawkular Integration
* The integration with Hawkular has now been updated to use asynchronous messages (HWKMETRICS-337)
4) Wildfly 10 - Deploying & Running
* Deploying and running the project on Wildfly 10 is now fully supported
* IMPORTANT - Support for Wildfly 9 is deprecated and will be completely dropped in the next release
Github Release:
https://github.com/hawkular/hawkular-metrics/releases/tag/0.11.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/12328918
Hawkular Metrics Clients
* Ruby: https://github.com/hawkular/hawkular-client-ruby
* Python: https://github.com/hawkular/hawkular-client-python
* Go: https://github.com/hawkular/hawkular-client-go
A big "Thank you" goes to John Sanda, Thomas Segismont, Mike Thompson, Matt Wringe, Michael Burman, Libor Zoubek, and Heiko Rupp for their project contributions.
Thank you,
Stefan Negrea
Software Engineer
8 years, 3 months
Agent installer
by Thomas Heute
So far we have an agent installer download page as an experimental feature.
I would be in favor of:
- moving the form to the application server list
- the whole form should be rendered when the list is empty to add a
first server
- When the server list is not empty, there should be a link to a popup
- we shouldn't force a wildfly home location, I would simplify to just
username and password as optional parameters.
WDYT ?
PS: I see 2 bugs at the moment:
- It downloads hawkular-wildfly-agent-wf-extension.zip instead of the
agent installer jar
- the instruction for command line doesn't include the right version,
it says: $ java -jar hawkular-wildfly-agent-installer-0.13.1.Final.jar
while the cirrect version is 0.15.1 I think
8 years, 3 months
Data store migration
by Juraci Paixão Kröhling
Team,
What's the recommended approach for handling data migrations? Is there a
library similar to liquibase?
- Juca.
8 years, 3 months
hawkular wildfly agent - feed ID
by John Mazzitelli
There was some concern that the feed ID autogenerated by the agent might not be what a person always wants (e.g. feed ID for WF10 agents will be the unique UUID of the wildfly server).
So, if you want to define your own feed ID, you can configure it now. In the agent's standalone.xml <storage-adapter> you can specify a feedId attribute if you want. By default, it isn't specified, so the agent will autogenerate a unique feed ID for itself (this should really be the normal mode of operation, but some people like to complain, so I made it easy to shut them up :-)
This is in master. Will be in the next release.
8 years, 3 months
[UI] Proposed New typescript tslint settings
by mike thompson
Please disregard if you don’t care about typescript linting or formatting.
I have a proposal for some changes to the tslint settings(hawkular/console/src/main/scripts/tslint.json). There are lots of little changes that need to be done to the code because of this tslint policy change. However, these changes produce more consistent, readable code that is better for long term maintenance.
For further reference on tslint rules see:
http://palantir.github.io/tslint/rules/ <http://palantir.github.io/tslint/rules/>
The second question I have is if this changes are agreed upon. When should it get put in? I’m of the mindset that it should be put in now, but happy to hear any other arguments against it.
HINT: With Webstorm 11, it can read in the tslint file and interactively show all the tslint hints in the code.
Sorry, I didn’t include the diff file.
hawkular/console/src/main/scripts/tslint.json:
{
"rules": {
"class-name": true,
"curly": true,
"eofline": true,
"forin": true,
"indent": [true, "spaces"],
"label-position": true,
"label-undefined": true,
"max-line-length": [true, 120],
"member-access": true,
"no-arg": true,
"no-bitwise": true,
"no-console": [true,
"trace"
],
"no-construct": true,
"no-debugger": false,
"no-duplicate-key": true,
"no-duplicate-variable": true,
"no-empty": true,
"no-eval": true,
"no-require-imports": true,
"no-string-literal": false,
"no-switch-case-fall-through": true,
"no-shadowed-variable": true,
"no-trailing-comma": true,
"no-trailing-whitespace": false,
"no-unused-expression": true,
"no-unused-variable": true,
"no-unreachable": true,
"no-use-before-declare": true,
"no-var-keyword": true,
"one-line": [true,
"check-open-brace",
"check-whitespace",
"check-catch",
"check-else"
],
"quotemark": [true, "single"],
"radix": false,
"semicolon": true,
"triple-equals": [true, "allow-null-check"],
"typedef-whitespace": [true],
"variable-name": [true, "ban-keywords", "check-format", "allow-leading-underscore"],
"whitespace": [true,
"check-decl",
"check-operator",
"check-type"
],
"license-header": [ true,
"/// Copyright 2014-2016 Red Hat, Inc. and/or its affiliates\n/// and other contributors as indicated by the @author tags.\n///\n/// Licensed under the Apache License, Version 2.0 (the \"License\");\n/// you may not use this file except in compliance with the License.\n/// You may obtain a copy of the License at\n///\n/// http://www.apache.org/licenses/LICENSE-2.0\n///\n/// Unless required by applicable law or agreed to in writing, software\n/// distributed under the License is distributed on an \"AS IS\" BASIS,\n/// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.\n/// See the License for the specific language governing permissions and\n/// limitations under the License."
]
}
}
8 years, 3 months
Inventory 0.12.0.Final released
by Lukas Krejci
Hi all,
Inventory 0.12.0.Final has been released.
The new features include:
* /ws/events endpoint to listen to inventory events over web sockets
* detection of identical resource and metric types across feeds (this is
currently not very useful but will become more handy in the future)
* several bugfixes and improvements to the build infrastructure
The big part that didn't make it to this release is inventory sync which is
well underway and should be ready in hopefully not more than a week.
Nevertheless, we released an inventory without it so that the other
improvements are available if inventory sync slips further.
Thanks to Peter Palaga, Pavol Loffay and Jirka Kremser for their contributions
to the release!
Regards,
Lukas
8 years, 3 months
