Data to collect when you open a case for Microsoft Azure Automation

Gælder for: Automation

Summary


This article describes some of the basic information that you should gather before you open a case for Azure Automation with Microsoft Azure Support. This information is not required to open the case. However, it can help Microsoft resolve your problem more quickly. Also, you may be asked for this data by the support engineer after you open the case.

More Information


Before you open a case for Microsoft Azure Automation Support, we recommend that you collect the following information.

Basic data collection

Collect the data that is described in the following Knowledge Base article:

4034605 How to capture Azure Automation-scripted diagnostics
 

For issues that affect Update Management on Linux

  1. In addition to the items that are listed in KB 4034605, run the following log collection tool:

    OMS Linux Agent Log Collector
     
  2. Compress the contents of the following folder, and then send the compressed file to Azure Support:

    /var/opt/microsoft/omsagent/run/automationworker/
     
  3. Verify that the workspace ID that the OMS Linux Agent is reporting to is the same as the workspace that's monitored for updates.
     


For issues that affect Update Management on Windows

In addition to the items that are listed in KB 4034605, do the following:

  1. Export the following event logs in EVTX format:
    • System
    • Application
    • Security
    • Operations Manager
    • Microsoft-SMA/Operational
  2. Verify that the workspace ID that the agent is reporting to is the same as the workspace that's being monitored by Windows Updates.


For issues that affect a job


In addition to the items that are listed in KB 4034605, collect the following information:

  1. The JobID number (for the job that is experiencing an issue). To do this, follow these steps:
    1. At the Azure portal, go to the Automation Accounts blade.
    2. Click the Automation Account that you are troubleshooting.
    3. Click Jobs.
    4. Click the job that you are troubleshooting.
    5. Under Job Summary, look for a Job ID (GUID).

      3178510-1
  2. The account name. To do this, follow these steps:
    1. At the Azure portal, go to the Automation Accounts blade.
    2. Get the name of the Automation Account that you're troubleshooting.
  3. A sample of the script that you are running.

  4. The log files. To do this, follow these steps:
    1. At the Azure portal, go to the Automation Accounts blade.
    2. Click the Automation Account that you are troubleshooting.
    3. Click Jobs.
    4. Click the job that you are troubleshooting.
    5. Click All Logs.
    6. On the resulting blade, collect the data.


      KB 3178510-2

       

For issues that affect modules

In addition to the items under "Basic data collection," gather the following information:

  • The steps you followed so that the problem can be reproduced.
  • A screenshot of any error messages.
  • A screenshot of the current modules and their version numbers.