seldon-core VS whylogs

ZenML is an extensible, open-source MLOps framework to create production-ready machine learning pipelines. Built for data scientists, it has a simple, flexible syntax, is cloud- and tool-agnostic, and has interfaces/abstractions that are catered towards ML workflows. Seldon Core is a production grade open source model serving platform. It packs a wide range of features built around deploying models to REST/GRPC microservices that include monitoring and logging, model explainers, outlier detectors and various continuous deployment strategies such as A/B testing, canary deployments and more.

I am using BentoML to build the docker container for a BERT model, and then deploy that using Seldon on GKE. The model's REST API endpoint works fine. at terms of compatibility with Seldon, the metrics are being scraped by Prometheus and visualized on Grafana. The only Seldon component that doesn't appear to be working is the request logging, which I have working for other applications that were deployed on Seldon. I am using the elastic stack from here. From my understanding, request logging should still be compatible and the ⠀only lost functionality should be Seldon's model metadata. Any insight on how to get the centralized request logging working? No errors were shown; it's just that the logs aren't being captured and sent to ElasticSearch. Anyone have any success using BentoML with Seldon and not losing any of Seldon's features?

While tools in the model experimentation space normally include diagnostic charts on a model's performance, there are also specialised solutions that help ensure that the deployed model continues to perform as they are expected to. This includes the likes of seldon-core, why-labs and fiddler.ai.

Seldon | Multiple positions | London/Cambridge UK | Onsite/Remote | Full time | seldon.io

At Seldon we are building industry leading solutions for deploying, monitoring, and explaining machine learning models. We are an open-core company with several successful open source projects like:

* https://github.com/SeldonIO/seldon-core

* https://github.com/SeldonIO/mlserver

* https://github.com/SeldonIO/alibi

* https://github.com/SeldonIO/alibi-detect

* https://github.com/SeldonIO/tempo

We are hiring for a range of positions, including software engineers(go, k8s), ml engineers (python, go), frontend engineers (js), UX designer, and product managers. All open positions can be found at https://www.seldon.io/careers/

Also note our github repo has a link to our slack where you can ask active users: https://github.com/SeldonIO/seldon-core

If you want to serve your model at scale, with a bunch of production features you should have a look at the open-source framework Seldon Core. It does what you're asking for plus a bunch of other cool stuff like routing, logging and monitoring.

Seldon ticks most of those boxes if you already have some experience with kubernetes. You can set up a/b tests, do payload logging to elastic and then do monitoring on top of that, and it has drift detection and model explainer modules too. Idk about great expectations integration, but you could probably do something with a custom transformer module as part of the inference graph.

whylogs — model monitoring

Have a look at whylogs. Nice profiling functionality incl. definition of constraints on profiles: https://github.com/whylabs/whylogs

WhyLabs has an open-source first approach. We maintain an open standard for data and ML logging https://github.com/whylabs/whylogs, which allows anybody to begin logging statistical properties of data in their data pipeline, ML inference, feature stores, etc. These statistical profiles capture all the key signals to enable observability in a given component. This unique approach means that we can run a fully SaaS service, which allows for huge scalability (in both the size of models and their number), and ensures that our customers are able to maintain their data autonomy. We maintain a huge array of integrations for whylogs, including Python, Spark, Kafka, Ray, Flask, MLflow, Kubeflow, etc… Once the profiles are captured systematically, they are centralized in the WhyLabs platform, where we organize them, run forecasting and anomaly detection on each metric, and surface alerts to users. The platform itself has a zero-config design philosophy, meaning all monitoring configurations can be set up using smart baselines and require no manual configuration. The TL;DR here is the focus on open source integrations, working with data at massive/streaming scale, and removing manual effort from maintaining configuration.

This is why we've been trying to encourage people to think about lightweight data logging as a mitigation for data quality problems. Similar to how we monitor applications with Prometheus, we should approach ML monitoring with the same rigor.

Disclaimer: I'm one of the authors. We spend a lot of effort to build the standard for data logging here: https://github.com/whylabs/whylogs. It's meant to be a lightweight and open standard for collecting statistical signatures of your data without having to run SQL/expensive analysis.