Operational insights data export#8128
Conversation
|
You don't have permission to trigger SDK Automation. |
|
Can one of the admins verify this patch? |
|
Azure Pipelines successfully started running 1 pipeline(s). |
1 similar comment
|
Azure Pipelines successfully started running 1 pipeline(s). |
azure-sdk-for-go - Release
|
azure-sdk-for-java - Release
No readme.md specification configuration files were found that are associated with the files modified in this pull request, or swagger_to_sdk section in readme.md is not configured
|
azure-sdk-for-js - Release
|
azure-sdk-for-python - Release
|
azure-sdk-for-net - Release
|
...ce-manager/Microsoft.OperationalInsights/preview/2019-08-01-preview/OperationalInsights.json
Show resolved
Hide resolved
...ce-manager/Microsoft.OperationalInsights/preview/2019-08-01-preview/OperationalInsights.json
Outdated
Show resolved
Hide resolved
| }, | ||
| "DataExportProperties": { | ||
| "properties": { | ||
| "dataExportId": { |
There was a problem hiding this comment.
dataExportId [](start = 9, length = 12)
If this is a fixed set, consider defining as enum and modelAsString=true for flexibility to add a new one without breaking clients
There was a problem hiding this comment.
It's not a fixed set. It a unique guid generator identifier
| "StorageAccount", | ||
| "EventHub" | ||
| ] | ||
| }, |
There was a problem hiding this comment.
i suppose type can be derived from the resourceId..
Also, you may consider making destination as an array if you envision supporting export to multiple destinations
There was a problem hiding this comment.
We want the type explicitly to avoid customer's mistakes.
It we will always one destination to export.
| "properties": { | ||
| "eventHubName": { | ||
| "type": "string", | ||
| "description": "event hub name." |
There was a problem hiding this comment.
isn't this evident from the resourceId provided .. ?
There was a problem hiding this comment.
No, Event hub is tracked resource. His main resource is namespace.
it's the same scenario like diagnostic settings.
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…hohershk/azure-rest-api-specs into OperationalInsights_data_export
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 3 pipeline(s). |
* microsoft.operationalinsights_add_data_export * fix * fix * fix readmfile + fix cSpell * fix * Revert "fix" This reverts commit a23f53b. * Fix azure-rest-api-specs-tests * format * Revert "format" This reverts commit f39f5e4. * Revert "Fix azure-rest-api-specs-tests" This reverts commit 50cf6aa. * prettifer * Code review fixes * Update OperationalInsights.json * Make Destination type "readonly" Co-authored-by: Arik Olsh <47111029+arolshan@users.noreply.github.com>
* microsoft.operationalinsights_add_data_export * fix * fix * fix readmfile + fix cSpell * fix * Revert "fix" This reverts commit a23f53b. * Fix azure-rest-api-specs-tests * format * Revert "format" This reverts commit f39f5e4. * Revert "Fix azure-rest-api-specs-tests" This reverts commit 50cf6aa. * prettifer * Code review fixes * Update OperationalInsights.json * Make Destination type "readonly" Co-authored-by: Arik Olsh <47111029+arolshan@users.noreply.github.com>
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub - one location for using our validation tools and finding your workflow.
Contribution checklist:
ARM API Review Checklist
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.
Please follow the link to find more details on API review process.