Skip to content

Commit

Permalink
Merge pull request #38 from Arize-ai/move-tracing
Browse files Browse the repository at this point in the history
docs: move spec to openinference
  • Loading branch information
mikeldking authored Jan 8, 2024
2 parents d03ce2f + 1731f41 commit 32d09ca
Show file tree
Hide file tree
Showing 3 changed files with 10 additions and 1 deletion.
1 change: 1 addition & 0 deletions .gitignore
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
node_modules/
6 changes: 5 additions & 1 deletion README.md
Original file line number Diff line number Diff line change
@@ -1,9 +1,13 @@
# OpenInference

> [!IMPORTANT]
> OpenInference Tracing is now being actively worked on via: [OpenInference](https://github.com/Arize-ai/openinference)
> This repository is maintained for historical purposes only.
This is a a working draft of the specification for OpenInference - a specification that encompass two data models:

- [Inferences](./inference/README.md)
- [Traces](./trace/README.md)
- [Traces](https://github.com/Arize-ai/openinference/tree/main/spec)

Inferences are designed to capture inference logs from a variety of model types and use-cases where as traces are designed to capture the execution of an application that results in invocations of an LLM.

Expand Down
4 changes: 4 additions & 0 deletions trace/README.md
Original file line number Diff line number Diff line change
@@ -1,5 +1,9 @@
# OpenInference Tracing

> [!IMPORTANT]
> OpenInference Tracing is now being actively worked on via: [OpenInference](https://github.com/Arize-ai/openinference)
> This repository is maintained for historical purposes only.
The OpenInference Tracing specification is edited in markdown files found in the [spec directory](./spec/README.md).

OpenInference Tracing is a specification for capturing and storing LLM application executions. It's designed to provide insight into the invocation of LLMs and the surrounding application context such as retrieval from vector stores and the usage of external tools such as search engines or APIs. The specification is transport and file-format agnostic, and is intended to be used in conjunction with other specifications such as JSON, ProtoBuf, and DataFrames.
Expand Down

0 comments on commit 32d09ca

Please sign in to comment.