[Feature Request]: Add chroma.enviornment for debugging

[HammadB]

Describe the problem

users run into issues and we don't know their build environments

Describe the proposed solution

We should add a chroma.enviornment or equivalent that emits relevant info (version, platform, deps etc) so we can better debug.

Alternatives considered

No response

Importance

nice to have

Additional Information

No response

[jeffchuber]

Trayan is working on this

[jeffchuber]

examples to study:

https://redis.io/commands/info/ https://docs.pinecone.io/docs/manage-indexes#checking-the-status-of-a-pod-size-change things we may want to expose that we dont yet have:

class labels size in GB? memory utilization? wild ideas p50/p99 read/write load p50/p99 latency i know this would normally be caught in an observability setup but itd be really nice if chroma tracked this top info and it was easy to query any meta info that would help a DBA or someone programmatically managing a Chroma instance...

[tazarov]

Let's revisit this and see how it fits in distributed - https://github.com/chroma-core/chroma/pull/1144

[jeffchuber]

this could be a nice CLI command too