Skip to content

Conversation

@jsquire
Copy link
Member

@jsquire jsquire commented Sep 15, 2025

The focus of these changes is to add the .NET-specific client configuration for the Monitor Query Logs service.

@jsquire jsquire self-assigned this Sep 15, 2025
@jsquire jsquire added the Monitor Monitor, Monitor Ingestion, Monitor Query label Sep 15, 2025
@github-actions
Copy link

github-actions bot commented Sep 15, 2025

Next Steps to Merge

✅ All automated merging requirements have been met! To get your PR merged, see aka.ms/azsdk/specreview/merge.

Comment generated by summarize-checks workflow run.

@github-actions github-actions bot added the TypeSpec Authored with TypeSpec label Sep 15, 2025
@github-actions
Copy link

github-actions bot commented Sep 15, 2025

API Change Check

APIView identified API level changes in this PR and created the following API reviews

Language API Review for Package
TypeSpec MonitorQueryLogs
JavaScript @azure/monitor-query-logs
Go sdk/monitor/query/azlogs

@jsquire jsquire added Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates Approved-Suppression Approved-SdkBreakingChange-Go-V2 BreakingChange-Go-Sdk-Suppression and removed Approved-OkToMerge <valid label in PR review process>add this label when assignee approve to merge the updates Approved-Suppression Approved-SdkBreakingChange-Go-V2 labels Sep 16, 2025
@jsquire jsquire merged commit 7202be8 into Azure:main Sep 16, 2025
111 of 112 checks passed
@jsquire jsquire deleted the monitor/query-logs branch September 16, 2025 22:00
markcowl pushed a commit to markcowl/azure-rest-api-specs that referenced this pull request Sep 18, 2025
* [Monitor Query Logs] .NET client updates

The focus of these changes is to add the .NET-specific
client configuration for the Monitor Query Logs service.

* Adding emitter-output-dir

* Adding clear-output-folder

* Removing clear-output-folder because its not valid

* Changing case of members because pipeline reasons?

* Changing case of members because pipeline reasons?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Monitor Monitor, Monitor Ingestion, Monitor Query TypeSpec Authored with TypeSpec

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants