Just FYI, I put a PR up for this feature:
https://github.com/apache/metron/pull/1250. I believe I've addressed
everyone's questions either in the PR description or the code itself. I'm
think we can continue the discussion there.
On Fri, Oct 19, 2018 at 12:02 PM Otto Fowler
wrote:
> I believe
I believe the issue of introducing and supporting higher latency
enrichments is a systemic one, and should be solved as such,
with the rest and other higher latency enrichments build on top of that
framework.
On October 19, 2018 at 12:22:28, Ryan Merriman (merrim...@gmail.com) wrote:
Thanks
Thanks Casey, good questions.
As far as the verbs go, just thinking we might want to support calls other
than GET at some point. For the use case stated (enriching messages from
3rd party services) GET is all we need. Probably a moot point anyways
since every http library will support the
I think it makes a lot of sense. A couple of questions:
- What actions do you see the REST verbs corresponding to? I would
understand GET (which is in effect "evaluate an expression", right?), but
I'm not sure about the others.
- We should probably be careful about caching stellar
I want to open up discussion around adding a Stellar REST client function.
There are services available to enrich security telemetry and they are
commonly exposed through a REST interface. The primary purpose of this
discuss thread to collect requirements from the community and agree on a
general
