Re: Exploring Telemetry for Lucene
Chris Hostetter <[email protected]>
| Newsgroups | gmane.comp.jakarta.lucene.devel |
|---|---|
| Message-ID | <alpine.DEB.2.21.2510071059280.29544@slate> |
: > > IMO Lucene should just be a library with ~no dependencies. It just : > needs to expose the right callbacks to allow for easy observability higher : > up the stack. : > ++ This makes sense to me. I’d rather make telemetry more straightforward : > to capture, rather than try to capture it. : To this end I think it would be nice if there was an observer pattern for : these kinds of callbacks rather than extend-and-override. This would also : make it easier to build integrations for different observability frameworks. This is where a lucene module that provides telemetry for major "core" lucene clases could be useful -- something completley optional that uses the underlying callbacks (or extend-and-override pattern) to add some basic telemetry using a third-party library w/an ASF compatible license -- that way lucene offers the best of all worlds: 1) a sleek core that doesn't have any external deps ... 2) but does offer hooks for adding in external functionality ... 3) which are tested and demonstrated by a module ... 4) which can be used out of the box by people who find it useful ... 5) or can serve as an example/tutorial for writing your own using a different third-party library. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]