henrikingo commented on issue #101: URL: https://github.com/apache/otava/issues/101#issuecomment-3589345129
Hi @radove That's a good observation and in fact I also use otava as an imported python module, I never used the CLI myself. Nyrkiö is a bit behind on versions and in fact I've been waiting to get to the post 0.7.x world which is today! So with that caveat, let me link to how I've used Otava the past 2 years: https://github.com/nyrkio/nyrkio/blob/ecc4b6f5f8c6369f900fafbbfc5533220888eefc/backend/core/core.py#L12-L18 https://github.com/nyrkio/nyrkio/blob/ecc4b6f5f8c6369f900fafbbfc5533220888eefc/backend/api/changes.py#L4 Notably: * In the Nyrkiö code, Otava (née Hunter) is not connected to any database, I feed it Series() objects from the outside. * For incremental otava, I also store and return the (weak) change points. Wishlist: * Currently the input data is well defined, we have our own PerformanceTestResultSeries that generates the Otava Series() class. But AnalyzedSeries() is more hacky and in the end we descned into just holding the change points in a large dict. * Would like to better define a structure/schema for the input and output data. It's timeseries data with SI units, everyone ends up doing roughly the same thing. * Adopting Pydantic on Nyrkio side is a step in that direction. * Probably should merge the Slack/Github/Email reporting between Nyrkio and Otava. We could define a proper API in the __init__.py file, or some other similar mechanism (Sorry for expanding your ticket, but wanted to share relevant context. Most of what I write here should be new tickets of their own.)) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
