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.
9 years, 2 months
Hawkular web site and tags
by Heiko W.Rupp
On 24 Mar 2017, at 12:10, Heiko W.Rupp wrote:
Recently I made a change to the web site to enable tags, and have
a "tag cloud".
The tag cloud is now also at the bottom of
http://www.hawkular.org
Please make sure when writing blog post and/or
pages to (re) use those. Tags with only one page/article
don't really add value. But don't leave them out when
you write about something completely new.
Example "Apache camel" should of course
be mentioned the 1st time someone writes about
Camel integration.
As you see with Apache Camel, it is possible to
create multi word tags
https://github.com/hawkular/hawkular.github.io/blame/pages/src/main/jbake...
they fail to correctly link when running jbake locally,
but work fine on GitHub pages.
Also for e.g. distributed tracing the multi word
tag "distributed tracing" is better than distributed, tracing.
also please try to consistently use the same spelling
and upper/lower case for a tag. apm != APM
--
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
9 years, 2 months
agent release
by John Mazzitelli
Hawkular Agent release 0.29.4.Final is out. This includes both HWFA and HJA. The main reason for this release is to put out the feature that Tom Cunningham wanted - the ability for the agent to wait for certain resources to be available before the agent starts monitoring things. See https://issues.jboss.org/browse/HWKAGENT-165.
This release also includes feature packs for HJA (EAP6 and EAP7/WF10+) and a distro that includes WF10+Java Agent (thanks josejulio for that stuff)
9 years, 2 months
agent "new server" event
by John Mazzitelli
<tl;dr>
Need ideas on how we are to implement the following two things in the agent:
1. At startup, agent needs to ask H-Metrics "what top-level servers have I told you about in an earlier life?"
2. When a new server is discovered, the agent should send an event to the server about the new server EXCEPT if the server isn't really new at all (see 1. above)
</tl;dr>
===
This post is to open up a discussion on how we want to implement a new features in the agent.
Joel is developing a new "inventory in metrics" feature: https://github.com/hawkular/hawkular-agent/pull/303
This means the agent will be storing inventory directly into Hawkular-Metrics. Because of this, we need to figure out how to get events sent based on things happening in H-Metric's inventory so MiQ can do things with it (like put things in the timeline such as "new server discovered" or "new WAR was deployed").
Jay looked at the code and the only thing that would be "missing" after this move of inventory into metrics is an event triggered when a new server is added to inventory. (When a new deployment is added, or a deployment is removed, the server is looking at command responses and generating events from that - so we don't lose anything by moving inventory into metrics).
By "new server", what we mean is a new resource that has no parent resources (i.e. a "root resource"). This includes standalone WildFly Servers and domain Host Controllers.
Right now, the agent starts with a "clean slate" when it starts up for the first time, or restarts. That means the agent's in-memory inventory graph is completely empty at startup - when discovery is run, the agent's internal inventory graph is filled in. After that, the agent just keeps the inventory graph up to date as it discovers new things coming and old things going away.
We need the agent to know if it already stored its top level servers into H-Metrics inventory and if it did, not to generate any "new server event". But if the agent is brand new, and it never sent any top-level resources to H-Metrics inventory yet, it should now send a "new server" event to the server (the agent never sent events like this before).
So there are two new things (assuming we keep the stuff Joel is doing - that is, we store inventory into H-Metrics):
1. At startup, agent needs to ask H-Metrics "what top-level servers have I told you about in an earlier life?"
2. When a new server is discovered, the agent should send an event (whatever this means - probably a REST API call somewhere) about the new server EXCEPT if the server isn't really new at all (see 1. above)
We need to figure out how to implement 1. and 2. So we are soliciting thoughts on those two subjects.
9 years, 2 months