-
Notifications
You must be signed in to change notification settings - Fork 5.1k
[DO NOT MERGE] AzureMonitor LiveMetrics onboarding to TypeSpec #42714
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
Conversation
| /// <summary> Monitoring data point coming from SDK, which includes metrics, documents and other metadata info. </summary> | ||
| internal partial class MonitoringDataPoint | ||
| /// <summary> Monitoring data point coming from the client, which includes metrics, documents and other metadata info. </summary> | ||
| public partial class MonitoringDataPoint |
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.
this is a bug. this type MUST not be public
| { | ||
| /// <summary> An AND-connected group of FilterInfo objects. </summary> | ||
| internal partial class FilterConjunctionGroupInfo | ||
| public partial class FilterConjunctionGroupInfo |
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.
this is a bug. this type MUST not be public
|
Hi @TimothyMothra. Thank you for your interest in helping to improve the Azure SDK experience and for your contribution. We've noticed that there hasn't been recent engagement on this pull request. If this is still an active work stream, please let us know by pushing some changes or leaving a comment. Otherwise, we'll close this out in 7 days. |
DO NOT MERGE Opening this PR to discuss how to correctly use TypeSpec api.
Background
We've been using a pre-release version of a swagger to work on the beta of our new SDK.
The new TypeSpec just merged this week Azure/azure-rest-api-specs#27430.
I'm trying to onboard our project to the TypeSpec and found several unexpected changes (shown in this PR).
At this point, I don't know if this is an error with the new Typespec, an error with the .NET generator, or if I've missed an onboarding step.
Steps followed
tsp-location.yamlfile.https://github.com/Azure/azure-sdk-for-net/blob/main/doc/DataPlaneCodeGeneration/AzureSDKCodeGeneration_DataPlane_Quickstart.md
tsp-location.yamlfilehttps://github.com/Azure/azure-sdk-tools/blob/main/doc/common/TypeSpec-Project-Scripts.md#tsp-locationyaml
npm install @azure-tools/typespec-autorest.\sdk\monitor\Azure.Monitor.OpenTelemetry.LiveMetrics\src> dotnet build /t:GenerateCodeChanges
This is a summary of some of the changes I've discovered
internaltopublic.MonitoringDataPointFilterConjunctionGroupInfoDocumentFilterConjunctionGroupInfoDerivedMetricInfoCollectionConfigurationInfoDocumentStreamInfopublicclasses. How to remove these?LiveMetricsClient- we have no need for a "client" class.LiveMetricsClientOptions- we already have our own "options" class.MonitorOpenTelemetryLiveMetricsClientBuilderExtensionsMonitorOpenTelemetryLiveMetricsModelFactoryOpen Questions
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/applicationinsights/ApplicationInsights.LiveMetrics/main.tsp
https://github.com/Azure/azure-rest-api-specs/blob/main/specification/applicationinsights/data-plane/LiveMetrics/preview/2024-04-01-preview/livemetrics.json