whylogs VS graphsignal-python

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.

We've built it for apps that use LLMs and other ML models. The lightweight Python agent autoinstruments OpenAI, LangChain, Banana, and other APIs and frameworks. Basically by adding one line of code you'll be able to monitor and analyze latency, errors, compute and costs. Profiling using CProfile, PyTorch Kineto or Yappi can be enabled if code-level statistics are necessary.

Here is a short demo screencast for a LangChain/OpenAI app: https://www.loom.com/share/17ba8aff32b74d74b7ba7f5357ed9250

In terms of data privacy, we only send metadata and statistics to https://graphsignal.com. So no raw data, such as prompts or images leave your app.

Hi HN. I'm excited to share our AI-focused application monitoring and analytics for Python!

We've built it for apps that use LLMs and other ML models. The lightweight Python agent autoinstruments OpenAI, LangChain, Banana, and other APIs and frameworks. Basically by adding one line of code you'll be able to monitor and analyze latency, errors, compute and costs. Profiling using CProfile, PyTorch Kineto or Yappi can be enabled if code-level statistics are necessary.

Here is a short demo screencast for a LangChain/OpenAI app: https://www.loom.com/share/17ba8aff32b74d74b7ba7f5357ed9250

In terms of data privacy, we only send metadata and statistics to https://graphsignal.com. So no raw data, such as prompts or images leave your app.

We'd love to hear your feedback or ideas!

Here is a blog post with more info and screenshots: Monitor OpenAI API Latency, Tokens, Rate Limits, and More. And the GitHub repo.

Relying on hosted inference with LLMs, such as via OpenAI API, in production has some challenges. The use of APIs should be designed around unstable latency, rate limits, token counts, costs, etc. To make it observable we've built tracing and monitoring specifically for AI apps. For example, the OpenAI Python library is monitored automatically, no need to do anything. We'll be adding support for more libraries. If you'd like to give it try, see https://github.com/graphsignal/graphsignal or the docs.

We've added a simple way to profile any model serving endpoint, including FastAPI, to identify bottlenecks and make inference (incl. data processing) faster, especially for big models and data. Wanted to share it here in case someone is struggling with profiling and monitoring of deployed code and models. By default, generic Python profiler will automatically profile some of the inferences (and measure all inferences). You can also specify other profilers for PyTorch, TensorFlow, Jax and ONNX Runtime. All profiles and metrics will be available on the SaaS dashboard, no need to setup anything. A couple of links to get started: Repo: https://github.com/graphsignal/graphsignal FastAPI example: https://graphsignal.com/docs/integrations/fastapi/ Happy for any feedback!

Thanks for sharing! That's a very timely topic. I've actually created a profiler to track and analyze inference optimizations, i.e. enable the optimize-verify-evaluate loop.

To address all these problems, we've built a tool to track inference optimizations, see how accuracy is affected, verify that the optimizations were applied and locate any bottlenecks for further improvements. All in one place.