You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/automation/python-packages.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -26,11 +26,11 @@ Once a package has been imported, it's listed on the Python 2 packages page in y
26
26
27
27
## Import packages with dependencies
28
28
29
-
Azure automation doesn't resolve dependencies for python packages during the import process. There are two ways to import a package with all its dependencies. Only one of the following steps needs to be used to import the packages into your Automation account.
29
+
Azure automation doesn't resolve dependencies for Python packages during the import process. There are two ways to import a package with all its dependencies. Only one of the following steps needs to be used to import the packages into your Automation account.
30
30
31
31
### Manually download
32
32
33
-
On a Windows 64-bit machine with [python2.7](https://www.python.org/downloads/release/latest/python2) and [pip](https://pip.pypa.io/en/stable/) installed, run the following command to download a package and all its dependencies:
33
+
On a Windows 64-bit machine with [Python2.7](https://www.python.org/downloads/release/latest/python2) and [pip](https://pip.pypa.io/en/stable/) installed, run the following command to download a package and all its dependencies:
@@ -40,7 +40,7 @@ Once the packages are downloaded, you can import them into your automation accou
40
40
41
41
### Runbook
42
42
43
-
Import the python runbook[Import Python 2 packages from pypi into Azure Automation account](https://gallery.technet.microsoft.com/scriptcenter/Import-Python-2-packages-57f7d509) from the gallery into your Automation account. Make sure the Run Settings are set to **Azure** and start the runbook with the parameters. The runbook requires a Run As account for the Automation account to work. For each parameter make sure you start it with the switch as seen in the following list and image:
43
+
To obtain a runbook, [import Python 2 packages from pypi into Azure Automation account](https://gallery.technet.microsoft.com/scriptcenter/Import-Python-2-packages-57f7d509) from the gallery into your Automation account. Make sure the Run Settings are set to **Azure** and start the runbook with the parameters. The runbook requires a Run As account for the Automation account to work. For each parameter make sure you start it with the switch as seen in the following list and image:
44
44
45
45
* -s \<subscriptionId\>
46
46
* -g \<resourceGroup\>
@@ -79,7 +79,7 @@ for group in groups:
79
79
80
80
## Develop and test runbooks offline
81
81
82
-
To develop and test your Python 2 runbooks offline, you can use the [Azure Automation python emulated assets](https://github.com/azureautomation/python_emulated_assets) module on GitHub. This module allows you to reference your shared resources such as credentials, variables, connections, and certificates.
82
+
To develop and test your Python 2 runbooks offline, you can use the [Azure Automation Python emulated assets](https://github.com/azureautomation/python_emulated_assets) module on GitHub. This module allows you to reference your shared resources such as credentials, variables, connections, and certificates.
When you create an Automation account, Azure Automation imports some modules by default. See [Default modules](#default-modules).
@@ -91,9 +92,13 @@ Note that the internal cmdlets differ in naming from the Az and AzureRM cmdlets.
91
92
92
93
We recommend that you use Az or AzureRM cmdlets for manipulating Azure Automation resources outside the context of a runbook.
93
94
94
-
## Module supporting Get-AutomationPSCredential
95
+
## Orchestrator.AssetManagement.Cmdlets module
95
96
96
-
The `Get-AutomationPSCredential` cmdlet is part of the module `Orchestrator.AssetManagement.Cmdlets`. This cmdlet returns a `PSCredential` object, which is expected by most PowerShell cmdlets that work with credentials. To find out more about the use of credentials in Azure Automation, see [Credential assets in Azure Automation](credentials.md).
97
+
Azure Automation supports the internal `Orchestrator.AssetManagement.Cmdlets` module for the Log Analytics agent for Windows, installed by default. The `Get-AutomationPSCredential` cmdlet in this module is commonly used in runbooks to retrieve a `PSCredential` object, which is expected by most PowerShell cmdlets that work with credentials. To find out more about the use of credentials in Azure Automation, see [Credential assets in Azure Automation](credentials.md).
98
+
99
+
## Python modules
100
+
101
+
You can create Python 2 runbooks in Azure Automation. For Python module information, see [Manage Python 2 packages in Azure Automation](../python-packages.md).
97
102
98
103
## Migrating to Az modules
99
104
@@ -112,7 +117,7 @@ Importing an Az module into your Automation account doesn't automatically import
112
117
* When a runbook invokes a cmdlet from a module
113
118
* When a runbook imports the module explicitly with the [Import-Module](https://docs.microsoft.com/powershell/module/microsoft.powershell.core/import-module?view=powershell-7) cmdlet
114
119
* When a runbook imports another dependent module
115
-
120
+
116
121
#### Testing for your runbooks and DSC configurations prior to module migration
117
122
118
123
Be sure to test all runbooks and DSC configurations carefully in a separate Automation account before migrating to the Az modules.
Copy file name to clipboardExpand all lines: articles/azure-monitor/insights/solutions-inventory.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -10,9 +10,9 @@ ms.date: 06/26/2018
10
10
---
11
11
12
12
# Inventory and data collection details for monitoring solutions in Azure
13
-
[Monitoring solutions](solutions.md)leverage services in Azure to provide additional insight into the operation of a particular application or service. Monitoring solutions typically collect log data and provide queries and views to analyze collected data. You can add monitoring solutions to Azure Monitor for any applications and services that you use. They are typically available at no cost but collect data that could invoke usage charges.
13
+
[Monitoring solutions](solutions.md)use services in Azure to gain knowledge of the operation of a particular application or service. Monitoring solutions typically collect log data and provide queries and views to analyze collected data. You can add monitoring solutions to Azure Monitor for any applications and services that you use. They're typically available at no cost but collect data that could invoke usage charges.
14
14
15
-
This article includes a list of [montioring solutions](solutions.md) available from Microsoft with links to their detailed documentation. It also provides information on their method and frequency of data collection into Azure Monitor. You can use the information in this article to identify the different solutions available and to understand the data flow and connection requirements for different monitoring solutions.
15
+
This article includes a list of [monitoring solutions](solutions.md) available from Microsoft with links to their detailed documentation. It also provides information on their method and frequency of data collection into Azure Monitor. You can use the information in this article to identify the different solutions available and to understand the data flow and connection requirements for different monitoring solutions.
@@ -22,11 +22,11 @@ The following table lists the [monitoring solutions](solutions.md) in Azure prov
22
22
23
23
Explanations of the columns are as follows:
24
24
25
-
-**Microsoft monitoring agent** - Agent used on Windows and Linux to run managements pack from SCOM and monitoring solutions from Azure. In this configuration, the agent is connected directly to Azure Monitor without being connected to an Operations Manager management group.
25
+
-**Microsoft monitoring agent** - Agent used on Windows and Linux to run managements pack from Microsoft System Center - Operations Manager (OM) and monitoring solutions from Azure. In this configuration, the agent is connected directly to Azure Monitor without being connected to an Operations Manager management group.
26
26
-**Operations Manager** - Identical agent as Microsoft monitoring agent. In this configuration, it's [connected to an Operations Manager management group](../platform/om-agents.md) that's connected to Azure Monitor.
27
-
-**Azure Storage** - Solution collects data from an Azure storage account.
27
+
-**Azure Storage** - Solution collects data from an Azure Storage account.
28
28
-**Operations Manager required?** - A connected Operations Manager management group is required for data collection by the monitoring solution.
29
-
-**Operations Manager agent data sent via management group** - If the agent is [connected to a SCOM management group](../platform/om-agents.md), then data is sent to Azure Monitor from the management server. In this case, the agent doesn't need to connect directly to Azure Monitor. If this box isn't selected, then data is sent from the agent directly to Azure Monitor even if the agent is connected to a SCOM management group. It will need to be able to communicate to Azure Monitor through the [Log Analytics gateway](../platform/gateway.md).
29
+
-**Operations Manager agent data sent via management group** - If the agent is [connected to an OM management group](../platform/om-agents.md), then data is sent to Azure Monitor from the management server. In this case, the agent doesn't need to connect directly to Azure Monitor. If this box isn't selected, then data is sent from the agent directly to Azure Monitor even if the agent is connected to an OM management group. It will need to be able to communicate to Azure Monitor through the [Log Analytics gateway](../platform/gateway.md).
30
30
-**Collection frequency** - Specifies the frequency that data is collected by the monitoring solution.
31
31
32
32
@@ -49,8 +49,8 @@ Explanations of the columns are as follows:
49
49
|[Azure SQL Analytics (Preview)](azure-sql.md)| Windows |||||| 1 minute |
50
50
|[Backup](https://azure.microsoft.com/resources/templates/101-backup-oms-monitoring/)| Azure |||||| on notification |
51
51
|[Capacity and Performance (Preview)](capacity-performance.md)|Windows |•|•|||•|on arrival |
|[System Center Operations Manager Assessment (Preview)](scom-assessment.md)| Windows |•|•|||•| seven days |
65
-
|[Update Management](../../automation/automation-update-management.md)| Windows |•|•|||•|at least 2 times per day and 15 minutes after installing an update |
65
+
|[Update Management](../../automation/automation-update-management.md)| Windows |•|•|||•|at least two times per day and 15 minutes after installing an update |
66
66
|[Upgrade Readiness](https://docs.microsoft.com/windows/deployment/upgrade/upgrade-readiness-get-started)| Windows |•||||| 2 days |
67
67
|[VMware Monitoring (Deprecated)](vmware.md)| Linux |•||||| 3 minutes |
68
68
|[Wire Data 2.0 (Preview)](wire-data.md)|Windows (2012 R2 / 8.1 or later) |•|•|||| 1 minute |
0 commit comments