Think of projects like repositories in GitHub—they’re the top-level organizational unit that keeps everything organized and separate.
What Is a Project?
A project groups together:Traces
Traces
All execution records for this application or environment
Datasets
Datasets
Vector databases and knowledge bases connected to this project
Policies
Policies
Governance rules that apply to data usage
Team members
Team members
Who has access to view and modify this project
Why Use Projects?
- Separate Environments
- Organize Applications
Keep production data separate from staging and development:Each environment gets its own project, preventing cross-contamination.
Production
Live user traffic, real data
Staging
Pre-release testing, safe experimentation
Development
Local testing, rapid iteration
Project Structure
Each project has:Basic Information
- Name - Human-readable identifier (“Production Customer Support”)
- ID - Unique identifier used in API calls
- Description - What this project is for
- Created date - When it was set up
Connected Resources
- Datasets - Which vector databases are linked
Metrics
- Total traces - How many traces have been captured
- Active datasets - How many data sources are connected
- Usage - Token counts, costs, trace volume over time
Default Project
When you first set up your AI platform, a Default Project is typically automatically created. You can:- Use it immediately for quick testing
- Rename it to match your main application
- Create additional projects and delete the default
Creating a Project
- Via UI
- Via API
Using a Project
Send Traces to a Project
When instrumenting your application, specify the project ID in your observability connector configuration:Project Dashboard
Each project has a dashboard showing:Trace Activity
- Recent traces - Latest executions with status, cost, duration
- Trace volume over time - Chart showing activity trends
- Error rate - Percentage of failed traces
- Average latency - Response time trends
Cost Tracking
- Total spend - Cumulative cost for this project
- Cost over time - Spending trends
- Cost by model - Which models cost the most
- Most expensive traces - Outliers to investigate
Data Usage
- Active datasets - Number of connected data sources
- Documents retrieved - Total retrieval count
- Usage by dataset - Which datasets are used most
- Unused documents - Percentage of docs never retrieved
Collections
- Active collections - Curated trace groups for review
- Shared collections - What’s been shared with stakeholders
- Recent activity - Latest collection updates
Managing Projects
Rename a Project
Update the name or description:- Open project settings
- Edit name/description
- Save changes
Delete a Project
Permanently remove a project and all its data:- Open project settings
- Click Delete Project
- Type project name to confirm
- Click Delete Permanently
Best Practices
Use Descriptive Names
Use Descriptive Names
Help team members understand what each project is:
Set Up Projects Before Instrumentation
Set Up Projects Before Instrumentation
Create and configure projects before sending traces. This ensures traces go to the right place from the start.
Monitor Project Metrics Regularly
Monitor Project Metrics Regularly
Check the dashboard weekly:
Are error rates increasing?
Is cost trending up unexpectedly?
Are datasets being used effectively?
Common Workflows
- Setting Up a New Application
- Debugging Environment-Specific Issues
