7:15 a.m.
With the latest update of metrics, it seems that the Pinger is now
broken: Metrics is now protected via Accounts, meaning that REST calls
would need to include auth data, which are not available to pinger.
Pinger is a process that runs on Hawkular server, so, either we would
need to get a token from users when they first request an URL to be
monitored, or we would need to somehow send data to Metrics "directly".
Of course, the bus comes to my mind. I'm sure this was discussed at
length before, but I just want to catch up on the current state of things.
My understanding is that Pinger would send a "PingerResult" to a topic,
where interested parties would be listening. Inventory and Metrics would
be such parties: a Topic Listener on each of those components would be
responsible for doing inventory-specific and metrics-specific logic.
The question, though, is: where would this code reside? Heiko's idea is
that this would be part of a "glue", ie, a code "somewhere inside
Hawkular". In my view, the glue is the bus, so, this should reside
within the component itself. In metrics case, the listener would
probably be inside the "hawkular-component" module. The code on
"hawkular-component" would just listen to this topic and call
MetricsService.
What would be the most appropriate way to have the pinger's results
stored in metrics?
- Juca.
7:39 a.m.
If we are now going to allow metrics and inventory data to be sent over the bus for
storage (in addition to REST) we should consider then also updating the wildfly agent to
use the bus WHEN EMBEDDED in the server. This would avoid the agent making REST calls to
itself (that is, to the same WF server it is running in). Since the agent would be
embedded in a full hawkular container, it could just put message on the bus rather than
send REST messages. Only when the agent is running standalone or in another external WF
should it send REST messages.
BTW: I thought the pinger was throw-away code and was to be re-implemented the
"correct" way by the time hawkular GA is released ;-)
----- Original Message -----
With the latest update of metrics, it seems that the Pinger is now
broken: Metrics is now protected via Accounts, meaning that REST calls
would need to include auth data, which are not available to pinger.
Pinger is a process that runs on Hawkular server, so, either we would
need to get a token from users when they first request an URL to be
monitored, or we would need to somehow send data to Metrics "directly".
Of course, the bus comes to my mind. I'm sure this was discussed at
length before, but I just want to catch up on the current state of things.
My understanding is that Pinger would send a "PingerResult" to a topic,
where interested parties would be listening. Inventory and Metrics would
be such parties: a Topic Listener on each of those components would be
responsible for doing inventory-specific and metrics-specific logic.
The question, though, is: where would this code reside? Heiko's idea is
that this would be part of a "glue", ie, a code "somewhere inside
Hawkular". In my view, the glue is the bus, so, this should reside
within the component itself. In metrics case, the listener would
probably be inside the "hawkular-component" module. The code on
"hawkular-component" would just listen to this topic and call
MetricsService.
What would be the most appropriate way to have the pinger's results
stored in metrics?
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
7:52 a.m.
On 11.02.2016 14:39, John Mazzitelli wrote:
If we are now going to allow metrics and inventory data to be sent
over the bus for storage (in addition to REST) we should consider then also updating the
wildfly agent to use the bus WHEN EMBEDDED in the server. This would avoid the agent
making REST calls to itself (that is, to the same WF server it is running in). Since the
agent would be embedded in a full hawkular container, it could just put message on the bus
rather than send REST messages. Only when the agent is running standalone or in another
external WF should it send REST messages.
+1 . I know you didn't mean otherwise, but just to make it clear: tenant
information (aka, persona ID) is would still be required, so that the
agent knows to which account this data belongs to.
BTW: I thought the pinger was throw-away code and was to be
re-implemented the "correct" way by the time hawkular GA is released ;-)
I guess it still is. But right now, it's not working :) So, a "minimal
effort" is required to get it back into the working state.
- Juca.
12:42 p.m.
It seems there's a PR for that already:
https://github.com/hawkular/hawkular-metrics/pull/445
Once this is merged, I think I'll be able to change the pinger to send
data to this "java:/queue/hawkular/metrics/gauges/new" queue. It seems
it works the other way around as I imagined (ie: metrics queue, instead
of pinger topic), but that works too :)
- Juca.
On 11.02.2016 14:15, Juraci Paixão Kröhling wrote:
With the latest update of metrics, it seems that the Pinger is now
broken: Metrics is now protected via Accounts, meaning that REST calls
would need to include auth data, which are not available to pinger.
Pinger is a process that runs on Hawkular server, so, either we would
need to get a token from users when they first request an URL to be
monitored, or we would need to somehow send data to Metrics "directly".
Of course, the bus comes to my mind. I'm sure this was discussed at
length before, but I just want to catch up on the current state of things.
My understanding is that Pinger would send a "PingerResult" to a topic,
where interested parties would be listening. Inventory and Metrics would
be such parties: a Topic Listener on each of those components would be
responsible for doing inventory-specific and metrics-specific logic.
The question, though, is: where would this code reside? Heiko's idea is
that this would be part of a "glue", ie, a code "somewhere inside
Hawkular". In my view, the glue is the bus, so, this should reside
within the component itself. In metrics case, the listener would
probably be inside the "hawkular-component" module. The code on
"hawkular-component" would just listen to this topic and call
MetricsService.
What would be the most appropriate way to have the pinger's results
stored in metrics?
- Juca.
_______________________________________________
hawkular-dev mailing list
hawkular-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hawkular-dev
3600
days inactive
3600
days old
3 comments
2 participants
participants (2)
-
John Mazzitelli -
Juraci Paixão Kröhling