-
Notifications
You must be signed in to change notification settings - Fork 5.5k
Observabilities Data plane API Specs #37357
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
Open
risinh
wants to merge
17
commits into
main
Choose a base branch
from
observability/features-2025-10-15-preview
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or 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
Next Steps to MergeNext steps that must be taken to merge this PR:
Comment generated by summarize-checks workflow run. |
API Change CheckAPIView identified API level changes in this PR and created the following API reviews
|
* Insights API * Fix based on feedback * Remove modelParameters * Fix descriptions * Fix query parameter for GET API * fixing names * Fix model * Fix types to be more intuitive * Fix name * using property directly * Using separate model for modelconfiguration * Putting model configuration within individual request types * Examples added * Prettier fix --------- Co-authored-by: Ritesh Kumar Sinha <risinh@microsoft.com>
* Added schedules API * Updated * updated * updated * Updated per review * updated * Updated schedules
* chore: Add an typespec for evaluator * style: Run typespec formatter * refactor: Remove evaluator subtype * refactor: Renamed "Safety" to "Risk and Safety" * refactor: Drop version and name from EvaluatorCreateResult * refactor: Add init_params * refactor: Add EvaluatorVersion.provider * refactor: Change updateVersion verb to PATCH * feat: Add routes to main.tsp * debug: Add todos * chore: Updates from typespec review * refactor: Lower case EvaluatorConfigType values * refactor: Rename CodeEvaluatorConfig -> Container and add CodeConfig * refactor: Remove container_deployment_config * refactor: type -> config_type * feat: Add RegistryScope * refactor: Add container based evaluator * refactor: InitParams -> InputParams + add OutpuParams * refactor: Remove prompty config * refactor: Remove scope * refactor: displayName to display_name * refactor: Add {in,out}put_params to container config * fix * updates * updates * updates * updates * updates * added startPendingUpload and fix * spell * created_at * created_at * created_at * adding pendingUpload Credentials * remove pendingUpload * added prompty and code * added tsv * added tsv * fix after review * fix for 10-15 * resolved conflicts again * fix after Johans comments * fix after Johans comments * fix after Johans comments * fix after Johans comments * fix after Johans comments * fix after Johans comments * updated metrics * updated metrics * Update specification/ai/Azure.AI.Projects/evaluators/models.tsp Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com> * Update specification/ai/Azure.AI.Projects/evaluators/models.tsp Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com> * Update specification/ai/Azure.AI.Projects/evaluators/models.tsp Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com> * Update specification/ai/Azure.AI.Projects/evaluators/models.tsp Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com> * Update specification/ai/Azure.AI.Projects/evaluators/models.tsp Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com> * Update specification/ai/Azure.AI.Projects/evaluators/models.tsp Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com> * fix paging * remove sorting * remove sorting --------- Co-authored-by: kdestin <101366538+kdestin@users.noreply.github.com> Co-authored-by: aprilk-ms <55356546+aprilk-ms@users.noreply.github.com>
* Compare insights models * Update
Co-authored-by: Ritesh Kumar Sinha <risinh@microsoft.com>
* sync API definition * add testing criteria * add Azure AI evaluator type * add property bag * commit to @docs since its pre-existing convention * update based on comments * clean-up versioning * switch @doc to comments * spelling fix * expected input/output schema * add type for input data * tools to generic object * response optional * latest changes
* Added examples * Updated examples * updated * Updated * Updated per API design change * updated prettier checks * updated to use right routes and methods * Updated npx prettier checks * updated new prettiers * updated * updated taxonomy api * updated * prettified * updated
…37908) * Add new field * Move evaluators back to Azure style * Update description * Update operationId * Updated azure-ai-projects.json * update cspell * Add examples * fixed spec * prettier * fixes * fix * fix * Fix create parameters
dargilco
approved these changes
Oct 10, 2025
* WIP * update * Update to 1 event type * Updated typespec * minor * Added examples * prettier * Update * update operation Id and examples * revert unwanted update * minor fixes
* Update examples * Fixed model * Another fix
* Preview version update 10-15 -> 11-15 * Update remaining places * Fix prettier * Fix prettier across all examples --------- Co-authored-by: Ritesh Kumar Sinha <risinh@microsoft.com>
Co-authored-by: Ritesh Kumar Sinha <risinh@microsoft.com>
* updated examples for taxonomies and schedules * updated * updated * updated
* Fixing Lint diff failures * prettier fix --------- Co-authored-by: Ritesh Kumar Sinha <risinh@microsoft.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
data-plane
new-api-version
PublishToCustomers
Acknowledgement the changes will be published to Azure customers.
TypeSpec
Authored with TypeSpec
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.
Data Plane API Specification Update Pull Request
Tip
Overwhelmed by all this guidance? See the
Getting help
section at the bottom of this PR description.PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.
API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.
Is this review for (select one):
Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified.
Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.
Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the
Generated ApiView
comment added to this PR. You can use ApiView to show API versions diff.Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
Release planner
A release plan should have been created. If not, please create one as it will help guide you through the REST API and SDK creation process.
❔Got questions? Need additional info?? We are here to help!
Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.
Click here for links to tools, specs, guidelines & other good stuff
Tooling
Guidelines & Specifications
Helpful Links
Getting help
write access
per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositoriesNext Steps to Merge
comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.and https://aka.ms/ci-fix.
queued
state, please add a comment with contents/azp run
.This should result in a new comment denoting a
PR validation pipeline
has started and the checks should be updated after few minutes.