[
https://issues.apache.org/jira/browse/TS-4032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15023256#comment-15023256
]
ASF GitHub Bot commented on TS-4032:
------------------------------------
Github user jpeach commented on the pull request:
https://github.com/apache/trafficserver/pull/343#issuecomment-159090606
> I thought I saw a comment from James but it doesn't seem to be there now.
I think I made them on the JIRA.
> 1) I'm open to using a term other than "alert", if there are any specific
suggestions.
We should definitely not overload "alert" here. I think "message" is
sufficient.
> 2) I will be working on updating the P.R. with additional example code of
the utility of this mechanism which will also illustrate use cases.
Great, looking forward to that!
Also, I think that the default mode of this feature should be to send a
message to a specific, named plugin. Maybe you could optionally broadcast the
message to all plugins, but it seems most useful to message a specific plugin.
The message itself should be a opaque bag of bytes. This would let you send
things like serialize protobuf messages (for example).
> Provide command line alert feature for plugins
> ----------------------------------------------
>
> Key: TS-4032
> URL: https://issues.apache.org/jira/browse/TS-4032
> Project: Traffic Server
> Issue Type: New Feature
> Components: Plugins
> Reporter: Alan M. Carroll
> Assignee: Alan M. Carroll
>
> Add another event to the lifecycle hook, ALERT. This will be sent only from
> an external API, e.g. {{traffic_ctl}}. Any plugin that wants to be alertable
> from the command line can attach to this hook and watch for the event
> {{TS_EVENT_LIFECYCLE_ALERT}}. The data for the event wil be a string that is
> provided by the external agent.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
