Skip to content

{Monitor} Fix CloudEndpointNotSetException error - #10320

Merged
Ethan Yang (necusjz) merged 5 commits into
Azure:mainfrom
yanzhudd:fix-monitor
Sep 10, 2026
Merged

Ethan Yang (necusjz) merged 5 commits into
Azure:mainfrom
yanzhudd:fix-monitor

Conversation

@yanzhudd

@yanzhudd Julie Zhu (yanzhudd) commented Sep 10, 2026

Copy link
Copy Markdown
Contributor

🤖 PR Validation — ️✔️ All clear

Breaking Changes
️✔️ None

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

General Guidelines

  • Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
  • Have you run python scripts/ci/test_index.py -q locally? (pip install azdev required)
  • My extension version conforms to the Extension version schema

For new extensions:

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

@yanzhudd Julie Zhu (yanzhudd) self-assigned this Sep 10, 2026
Copilot AI lite review requested due to automatic review settings September 10, 2026 05:47
@azure-client-tools-bot-prd

Copy link
Copy Markdown

Hi Julie Zhu (@yanzhudd),
Please write the description of changes which can be perceived by customers into HISTORY.rst.
If you want to release a new extension version, please update the version in pyproject.toml (or setup.py, if the extension has not migrated yet) as well.

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

The change is a targeted string-key correction that aligns with existing Azure cloud endpoint metadata keys and has low risk.

Pull request overview

Fixes the Log Analytics AAZ data-plane client’s cloud endpoint metadata lookup by correcting the _CLOUD_HOST_METADATA_INDEX key so the client can resolve the proper Log Analytics endpoint from ctx.cli_ctx.cloud.endpoints and avoid CloudEndpointNotSetException.

Changes:

  • Corrected the cloud endpoint metadata index from logAnalyticslogAnalyticsResourceId to logAnalyticsResourceId in the Log Analytics AAZ client.
File summaries
File Description
src/log-analytics/azext_loganalytics/aaz/latest/_clients.py Fixes the cloud endpoint metadata key used to resolve the Log Analytics data-plane base URL.
Review details
  • Files reviewed: 1/1 changed files
  • Comments generated: 0
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@yonzhan

Copy link
Copy Markdown
Collaborator

Monitor

Comment thread src/log-analytics/HISTORY.rst Outdated
Comment thread src/log-analytics/setup.py Outdated
Co-authored-by: Ethan Yang <necusjz@gmail.com>
Co-authored-by: Ethan Yang <necusjz@gmail.com>
@necusjz
Ethan Yang (necusjz) merged commit 42e7668 into Azure:main Sep 10, 2026
24 checks passed
@azclibot

Copy link
Copy Markdown
Collaborator

[Release] Update index.json for extension [ log-analytics-1.0.0b2 ] : https://dev.azure.com/msazure/One/_build/results?buildId=180508096&view=results

@yanzhudd
Julie Zhu (yanzhudd) deleted the fix-monitor branch September 14, 2026 04:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants