[Hawkular-dev] the name of our hawkular agent/wildfly monitor/feed is confusing - I'm fixing it

Thomas Segismont tsegismo at redhat.com
Wed Nov 4 15:01:42 EST 2015


In case it was not obvious, a feed could also be the application itself, 
or an embedded agent.

Le 02/11/2015 19:24, John Mazzitelli a écrit :
> We still call things "feeds". To me, feeds are a superset - they are ANYTHING that are clients to Hawkular (shell scripts, python apps, cron jobs) and this includes more fully-featured agents.
>
> The Hawkular WildFly Agent is something that runs inside of Wildfly as an extension subsystem. Its a type of feed. We could have called it Hawkular WildFly Feed, but frankly, I think that would have made people look at it crosseyed too. People know what a management agent is; "feed" not so much.
>
> So, an agent is a type of feed - its a more fully featured hawkular feed.
>
> That's my story and I'm sticking to it. :)
>
> ----- Original Message -----
>> So does this mean the "feeds" in inventory should be renamed to "agents",
>> too?
>>
>> I thought that we wanted to move away from using the word agent but frankly I
>> don't care too much.
>>
>> On Monday, November 02, 2015 10:06:13 Thomas Heute wrote:
>>> +1
>>>
>>> On Sat, Oct 31, 2015 at 12:02 AM, John Mazzitelli <mazz at redhat.com> wrote:
>>>> As I'm writing code and docs and javadocs all around, I realize that the
>>>> name of our "agent" is utterly confused. We need to fix this or we will
>>>> eventually confuse users/customers.
>>>>
>>>> Right now in code, or comments, or docs, or just in talking, the names of
>>>> the "agent" have been at one time or another:
>>>>
>>>> agent
>>>> wildfly monitor
>>>> wildfly hawkular feed
>>>> wildfly monitor agent
>>>> wildfly extension
>>>> wildfly agent module
>>>> wildfly agent
>>>> etc. etc. etc.
>>>>
>>>> Over the weekend, I'm going to start renaming this so it is consistent
>>>> across the board.
>>>>
>>>> It will be called "Hawkular WildFly Agent"
>>>>
>>>> This will affect maven artifact names moving forward. But we need to fix
>>>> this now, because its confusing ME. I can only imagine the confusion when
>>>> people start to ask "what do you call the hawkular thing that monitors
>>>> Wildfly?"
>>>> _______________________________________________
>>>> hawkular-dev mailing list
>>>> hawkular-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
>> _______________________________________________
>> hawkular-dev mailing list
>> hawkular-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>>
> _______________________________________________
> hawkular-dev mailing list
> hawkular-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hawkular-dev
>



More information about the hawkular-dev mailing list