Add new swagger.json for Application Insights ingestion endpoint

[hectorhdzg]

MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.

Changelog

Add a changelog entry for this PR by answering the following questions:

1. What's the purpose of the update?
   • new service onboarding
   • new API version
   • update existing version for new feature
   • update existing version to fix swagger quality issue in s360
   • Other, please clarify
2. When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
   Service is in currently available
3. When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
   March 2022
4. If updating an existing version, please select the specific language SDKs and CLIs that must be refreshed after the swagger is published.
   • SDK of .NET (need service team to ensure code readiness)
   • SDK of Python
   • SDK of Java
   • SDK of Js
   • SDK of Go
   • PowerShell
   • CLI
   • Terraform
   • No refresh required for updates in this PR

Contribution checklist:

• I commit to follow the Breaking Change Policy of "no breaking changes"
• I have reviewed the documentation for the workflow.
• Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.

ARM API Review Checklist

Applicability: ⚠️

If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

• Change to data plane APIs
• Adding new properties
• All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

• Check this box if any of the following apply to the PR so that label "WaitForARMFeedback" will be added automatically to begin ARM API Review. Failure to comply may result in delays to the manifest.

  • Adding a new service
  • Adding new API(s)
  • Adding a new API version
    -[ ] To review changes efficiently, ensure you are using OpenAPIHub to initialize the PR for adding a new version. More details, refer to the wiki.

• Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

• If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist

If any of the following scenarios apply to the PR, request approval from the Breaking Change Review Board as defined in the Breaking Change Policy.

• Removing API(s) in a stable version
• Removing properties in a stable version
• Removing API version(s) in a stable version
• Updating API in a stable or public preview version with Breaking Change Validation errors
• Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.

Please follow the link to find more details on PR review process.

[openapi-workflow-bot]

Hi, @hectorhdzg Thanks for your PR. I am workflow bot for review process. Here are some small tips.

Please ensure to do self-check against checklists in first PR comment.

PR assignee is the person auto-assigned and responsible for your current PR reviewing and merging.

For specs comparison cross API versions, Use API Specs Comparison Report Generator

If there is CI failure(s), to fix CI error(s) is mandatory for PR merging; or you need to provide justification in PR comment for explanation. How to fix?

Any feedback about review process or workflow bot, pls contact swagger and tools team. vsswagger@microsoft.com

[openapi-workflow-bot]

[Call for Action] To better understand Azure service dev/test scenario, and support Azure service developer better on Swagger and REST API related tests in early phase, please help to fill in with this survey https://aka.ms/SurveyForEarlyPhase. It will take 5 to 10 minutes. If you already complete survey, please neglect this comment. Thanks.

[openapi-pipeline-app]

Swagger Validation Report

️️✔️BreakingChange succeeded [Detail] [Expand]

There are no breaking changes.

️️✔️LintDiff succeeded [Detail] [Expand]

Validation passes for LintDiff.

• Linted configuring files (Based on source branch, openapi-validator v1.12.1 , classic-openapi-validator v1.2.2 )
  • data-plane/Monitor.Exporters/readme.md tag:default
• Linted configuring files (Based on target branch, openapi-validator v1.12.1 , classic-openapi-validator v1.2.2 )
  • data-plane/Monitor.Exporters/readme.md tag:default

️❌Avocado: 2 Errors, 0 Warnings failed [Detail]

Rule	Message
❌ UNREFERENCED_JSON_FILE	The example JSON file is not referenced from the swagger file. readme: applicationinsights/data-plane/Monitor.Exporters/readme.md json: preview/2022-02-16_Preview/examples/track.json
❌ UNREFERENCED_JSON_FILE	The swagger JSON file is not referenced from the readme file. readme: applicationinsights/data-plane/Monitor.Exporters/readme.md json: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json

️️✔️~[Staging] ApiReadinessCheck succeeded [Detail] [Expand]

️❌ModelValidation: 3 Errors, 0 Warnings failed [Detail]

Rule	Message
❌ RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE	Following response status codes 401 for operation track were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. Url: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json#L64:18 ExampleUrl: preview/2022-02-16_Preview/examples/track.json#L105:16
❌ RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE	Following response status codes 403 for operation track were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. Url: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json#L78:18 ExampleUrl: preview/2022-02-16_Preview/examples/track.json#L105:16
❌ RESPONSE_STATUS_CODE_NOT_IN_EXAMPLE	Following response status codes 408 for operation track were present in the swagger spec, however they were not present in x-ms-examples. Please provide them. Url: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json#L85:18 ExampleUrl: preview/2022-02-16_Preview/examples/track.json#L105:16

️️✔️SemanticValidation succeeded [Detail] [Expand]

Validation passes for SemanticValidation.

️❌Cross-Version Breaking Changes: 3 Errors, 0 Warnings failed [Detail]

• Compared Swaggers (Based on Oad v0.9.3)
  • current:preview/2022-02-16_Preview/swagger.json compared with base:preview/2020-09-15_Preview/swagger.json

The following breaking changes are detected by comparison with latest preview version:

Rule	Message
❌ 1011 - AddingResponseCode	The new version adds a response code '401'. New: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json#L64:11
❌ 1011 - AddingResponseCode	The new version adds a response code '403'. New: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json#L78:11
❌ 1011 - AddingResponseCode	The new version adds a response code '408'. New: Monitor.Exporters/preview/2022-02-16_Preview/swagger.json#L85:11

️️✔️CredScan succeeded [Detail] [Expand]

There is no credential detected.

️️✔️SDK Track2 Validation succeeded [Detail] [Expand]

Validation passes for SDKTrack2Validation

️️✔️PrettierCheck succeeded [Detail] [Expand]

Validation passes for PrettierCheck.

️️✔️SpellCheck succeeded [Detail] [Expand]

Validation passes for SpellCheck.

️️✔️Lint(RPaaS) succeeded [Detail] [Expand]

Validation passes for Lint(RPaaS).

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-pipeline-app]

Swagger Generation Artifacts

️️✔️ApiDocPreview succeeded [Detail] [Expand]

 Please click here to preview with your @microsoft account. 

️️✔️SDK Breaking Change Tracking succeeded [Detail] [Expand]

Breaking Changes Tracking

_{Posted by Swagger Pipeline | How to fix these errors?}

[openapi-workflow-bot]

Hi @hectorhdzg, Your PR has some issues. Please fix the CI sequentially by following the order of Avocado, semantic validation, model validation, breaking change, lintDiff. If you have any questions, please post your questions in this channel https://aka.ms/swaggersupport.

Task	How to fix	Priority
Avocado	Fix-Avocado	High
Semantic validation	Fix-SemanticValidation-Error	High
Model validation	Fix-ModelValidation-Error	High
LintDiff	Fix-LintDiff	high

If you need further help, please feedback via swagger feedback.

[hectorhdzg]

We need new an updated file for Breeze endpoint used by Application Insights and Azure Monitor OpenTelemetry exporters, this mainly to call v2.1/track instead of v2/track defined before, some features in Breeze are only available in 2.1 like Authentication support that we want to have in exporters.

[hectorhdzg]

Duplicated
#14461