[Monitor] Update query package to use TypeSpec

This removes Metrics-related code/content and converts this package to
be for logs querying only.

Signed-off-by: Paul Van Eck <[email protected]>

Author: pvaneck

sdk/monitor/azure-monitor-query/CHANGELOG.md

@@ -1,17 +1,26 @@
 # Release History
 
-## 1.4.2 (Unreleased)
+## 2.0.0 (Unreleased)
 
 ### Features Added
 
 ### Breaking Changes
 
+- `MetricsClient` and `MetricsQueryClient` have been removed from the `azure-monitor-query` package. This is part of the migration to split logs and metrics functionality into separate packages.  ([#42205](https://github.com/Azure/azure-sdk-for-python/pull/42205))
+  - The `MetricsClient` has been moved to the new `azure-monitor-querymetrics`
+  - Functionality provided by `MetricsQueryClient` can be access through the `azure-mgmt-monitor` package.
+
 ### Bugs Fixed
 
 - Fixed an issue where the package version in operation user agent strings was always set to "unknown" instead of the actual package version. ([#39866](https://github.com/Azure/azure-sdk-for-python/pull/39866))
 
 ### Other Changes
 
+- Bump minimum dependencies:
+  - `azure-core` to `>=1.30.0`
+  - `isodate` to `>=0.6.1`
+  - `typing-extensions` to `>=4.6.0`
+
 ## 1.4.1 (2025-01-14)
 
 ### Other Changes

sdk/monitor/azure-monitor-query/MANIFEST.in

@@ -1,7 +1,7 @@
-recursive-include tests *.py *.yaml
-recursive-include samples *.py
 include *.md
 include LICENSE
+include azure/monitor/query/py.typed
+recursive-include tests *.py
+recursive-include samples *.py *.md
 include azure/__init__.py
 include azure/monitor/__init__.py
-include azure/monitor/query/py.typed

sdk/monitor/azure-monitor-query/README.md

@@ -6,17 +6,14 @@ This troubleshooting guide contains instructions to diagnose frequently encounte
 
 * [General Troubleshooting](#general-troubleshooting)
     * [Enable client logging](#enable-client-logging)
-    * [Troubleshooting authentication issues with logs and metrics query requests](#authentication-errors)
+    * [Troubleshooting authentication issues with query requests](#authentication-errors)
     * [Troubleshooting running async APIs](#errors-with-running-async-apis)
 * [Troubleshooting Logs Query](#troubleshooting-logs-query)
     * [Troubleshooting insufficient access error](#troubleshooting-insufficient-access-error-for-logs-query)
     * [Troubleshooting invalid Kusto query](#troubleshooting-invalid-kusto-query)
     * [Troubleshooting empty log query results](#troubleshooting-empty-log-query-results)
     * [Troubleshooting server timeouts when executing logs query request](#troubleshooting-server-timeouts-when-executing-logs-query-request)
     * [Troubleshooting partially successful logs query requests](#troubleshooting-partially-successful-logs-query-requests)
-* [Troubleshooting Metrics Query](#troubleshooting-metrics-query)
-    * [Troubleshooting insufficient access error](#troubleshooting-insufficient-access-error-for-metrics-query)
-    * [Troubleshooting unsupported granularity for metrics query](#troubleshooting-unsupported-granularity-for-metrics-query)
 * [Additional azure-core configurations](#additional-azure-core-configurations)
 
 ## General Troubleshooting
@@ -53,11 +50,7 @@ client.query_workspace(logging_enable=True)
 
 ### Authentication errors
 
-Azure Monitor Query supports Azure Active Directory authentication. Both LogsQueryClient and
-MetricsQueryClient have methods to set the `credential`. To provide a valid credential, you can use
-`azure-identity` dependency. For more details on getting started, refer to
-the [README](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/monitor/azure-monitor-query#create-the-client)
-of Azure Monitor Query library. You can also refer to
+Azure Monitor Query supports Microsoft Entra ID authentication. LogsQueryClient has methods to set the `credential`. To provide a valid credential, you can use the `azure-identity` package. For more details on getting started, refer to the [README](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/monitor/azure-monitor-query#create-the-client) of the Azure Monitor Query library. You can also refer to
 the [Azure Identity documentation](https://learn.microsoft.com/python/api/overview/azure/identity-readme)
 for more details on the various types of credential supported in `azure-identity`.
 
@@ -174,39 +167,6 @@ data = response.partial_data
 error = response.partial_error
 ```
 
-## Troubleshooting Metrics Query
-
-### Troubleshooting insufficient access error for metrics query
-
-If you get an HTTP error with status code 403 (Forbidden), it means that the provided credentials does not have
-sufficient permissions to query the workspace.
-```text
-"{"error":{"message":"The provided credentials have insufficient access to perform the requested operation","code":"InsufficientAccessError","correlationId":""}}"
-```
-
-1. Check that the application or user that is making the request has sufficient permissions:
-    * You can refer to this document to [manage access to workspaces](https://learn.microsoft.com/azure/azure-monitor/logs/manage-access#manage-access-using-workspace-permissions)
-2. If the user or application is granted sufficient privileges to query the workspace, make sure you are
-   authenticating as that user/application. If you are authenticating using the
-   [DefaultAzureCredential](https://github.com/Azure/azure-sdk-for-python/tree/main/sdk/identity/azure-identity#defaultazurecredential)
-   then check the logs to verify that the credential used is the one you expected. To enable logging, see [enable
-   client logging](#enable-client-logging) section above.
-
-For more help on troubleshooting authentication errors please see the Azure Identity client library [troubleshooting guide](https://github.com/Azure/azure-sdk-for-python/blob/main/sdk/identity/azure-identity/TROUBLESHOOTING.md).
-
-### Troubleshooting unsupported granularity for metrics query
-
-If you notice the following exception, this is due to an invalid time granularity in the metrics query request. Your
-query might have set the `granularity` keyword argument to an unsupported duration.
-
-```text
-"{"code":"BadRequest","message":"Invalid time grain duration: PT10M, supported ones are: 00:01:00,00:05:00,00:15:00,00:30:00,01:00:00,06:00:00,12:00:00,1.00:00:00"}"
-```
-
-As documented in the error message, the supported granularity for metrics queries are 1 minute, 5 minutes, 15 minutes,
-30 minutes, 1 hour, 6 hours, 12 hours and 1 day.
-
-
 ## Additional azure-core configurations
 
 When calling the methods, some properties including `retry_mode`, `timeout`, `connection_verify` can be configured by passing in as keyword arguments. See

sdk/monitor/azure-monitor-query/TROUBLESHOOTING.md

@@ -0,0 +1,3 @@
+{
+  "apiVersion": "v1"
+}

sdk/monitor/azure-monitor-query/_metadata.json

@@ -0,0 +1,6 @@
+{
+    "CrossLanguagePackageId": "MonitorQueryLogs",
+    "CrossLanguageDefinitionId": {
+        "azure.monitor.query.models._ColumnType": "MonitorQueryLogs.ColumnDataType"
+    }
+}

sdk/monitor/azure-monitor-query/apiview-properties.json

@@ -2,5 +2,5 @@
   "AssetsRepo": "Azure/azure-sdk-assets",
   "AssetsRepoPrefixPath": "python",
   "TagPrefix": "python/monitor/azure-monitor-query",
-  "Tag": "python/monitor/azure-monitor-query_79499b2a8c"
+  "Tag": "python/monitor/azure-monitor-query_5e44a95839"
 }

sdk/monitor/azure-monitor-query/assets.json

@@ -1 +1 @@
-__path__ = __import__("pkgutil").extend_path(__path__, __name__)
+__path__ = __import__("pkgutil").extend_path(__path__, __name__)  # type: ignore

sdk/monitor/azure-monitor-query/azure/__init__.py

@@ -1 +1 @@
-__path__ = __import__("pkgutil").extend_path(__path__, __name__)
+__path__ = __import__("pkgutil").extend_path(__path__, __name__)  # type: ignore

sdk/monitor/azure-monitor-query/azure/monitor/__init__.py

@@ -2,61 +2,31 @@
 # --------------------------------------------------------------------------
 # Copyright (c) Microsoft Corporation. All rights reserved.
 # Licensed under the MIT License. See License.txt in the project root for license information.
+# Code generated by Microsoft (R) Python Code Generator.
+# Changes may cause incorrect behavior and will be lost if the code is regenerated.
 # --------------------------------------------------------------------------
+# pylint: disable=wrong-import-position
 
-from ._logs_query_client import LogsQueryClient
-from ._metrics_query_client import MetricsQueryClient
-from ._metrics_client import MetricsClient
+from typing import TYPE_CHECKING
 
-from ._enums import (
-    LogsQueryStatus,
-    MetricAggregationType,
-    MetricClass,
-    MetricNamespaceClassification,
-    MetricUnit,
-)
+if TYPE_CHECKING:
+    from ._patch import *  # pylint: disable=unused-wildcard-import
 
-from ._exceptions import LogsQueryError
+from ._client import MonitorQueryLogsClient  # type: ignore
+from ._version import VERSION
 
-from ._models import (
-    LogsQueryResult,
-    LogsTable,
-    LogsQueryPartialResult,
-    LogsTableRow,
-    MetricsQueryResult,
-    LogsBatchQuery,
-    MetricNamespace,
-    MetricDefinition,
-    TimeSeriesElement,
-    Metric,
-    MetricValue,
-    MetricAvailability,
-)
+__version__ = VERSION
 
-from ._version import VERSION
+try:
+    from ._patch import __all__ as _patch_all
+    from ._patch import *
+except ImportError:
+    _patch_all = []
+from ._patch import patch_sdk as _patch_sdk
 
 __all__ = [
-    "MetricAggregationType",
-    "LogsQueryClient",
-    "LogsQueryResult",
-    "LogsQueryPartialResult",
-    "LogsQueryStatus",
-    "LogsQueryError",
-    "LogsTable",
-    "LogsTableRow",
-    "LogsBatchQuery",
-    "MetricsQueryClient",
-    "MetricsClient",
-    "MetricNamespace",
-    "MetricNamespaceClassification",
-    "MetricDefinition",
-    "MetricUnit",
-    "MetricsQueryResult",
-    "TimeSeriesElement",
-    "Metric",
-    "MetricValue",
-    "MetricClass",
-    "MetricAvailability",
+    "MonitorQueryLogsClient",
 ]
+__all__.extend([p for p in _patch_all if p not in __all__])  # pyright: ignore
 
-__version__ = VERSION
+_patch_sdk()