New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding LLM Tracking docs #8234
Merged
Merged
Adding LLM Tracking docs #8234
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
area/tracking
Tracking service, tracking client APIs, autologging
rn/documentation
Mention under Documentation Changes in Changelogs.
labels
Apr 14, 2023
Documentation preview for 47c4a26 will be available here when this CircleCI job completes successfully. More info
|
sunishsheth2009
force-pushed
the
sunish-log-llm-artifacts
branch
10 times, most recently
from
April 14, 2023 20:46
0bef6de
to
9e593a2
Compare
sunishsheth2009
changed the title
[WIP] Adding LLM Tracking docs
Adding LLM Tracking docs
Apr 14, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
BenWilson2
reviewed
Apr 17, 2023
sunishsheth2009
force-pushed
the
sunish-log-llm-artifacts
branch
from
April 18, 2023 00:28
9e593a2
to
0ff2807
Compare
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
sunishsheth2009
force-pushed
the
sunish-log-llm-artifacts
branch
from
April 18, 2023 02:29
0ff2807
to
9dab7c3
Compare
Signed-off-by: Sunish Sheth <sunishsheth2009@gmail.com>
sunishsheth2009
force-pushed
the
sunish-log-llm-artifacts
branch
from
April 18, 2023 02:29
9dab7c3
to
47c4a26
Compare
BenWilson2
approved these changes
Apr 18, 2023
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/tracking
Tracking service, tracking client APIs, autologging
rn/documentation
Mention under Documentation Changes in Changelogs.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes are proposed in this pull request?
Adding LLM Tracking docs
How is this patch tested?
Does this PR change the documentation?
Release Notes
Is this a user-facing change?
(Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change.)
What component(s), interfaces, languages, and integrations does this PR affect?
Components
area/artifacts
: Artifact stores and artifact loggingarea/build
: Build and test infrastructure for MLflowarea/docs
: MLflow documentation pagesarea/examples
: Example codearea/model-registry
: Model Registry service, APIs, and the fluent client calls for Model Registryarea/models
: MLmodel format, model serialization/deserialization, flavorsarea/recipes
: Recipes, Recipe APIs, Recipe configs, Recipe Templatesarea/projects
: MLproject format, project running backendsarea/scoring
: MLflow Model server, model deployment tools, Spark UDFsarea/server-infra
: MLflow Tracking server backendarea/tracking
: Tracking Service, tracking client APIs, autologgingInterface
area/uiux
: Front-end, user experience, plotting, JavaScript, JavaScript dev serverarea/docker
: Docker use across MLflow's components, such as MLflow Projects and MLflow Modelsarea/sqlalchemy
: Use of SQLAlchemy in the Tracking Service or Model Registryarea/windows
: Windows supportLanguage
language/r
: R APIs and clientslanguage/java
: Java APIs and clientslanguage/new
: Proposals for new client languagesIntegrations
integrations/azure
: Azure and Azure ML integrationsintegrations/sagemaker
: SageMaker integrationsintegrations/databricks
: Databricks integrationsHow should the PR be classified in the release notes? Choose one:
rn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes