Debugging the discovery component - AWS Perspective

Debugging the discovery component

If you have imported an account and Region that does not show resources within the AWS Perspective UI, check the following items to ensure you have everything set up.

  1. Check that you have deployed the CloudFormation template in the AWS Region of the account you are importing and that it created successfully. Ensure you have followed the steps for importing a Region.

  2. Double check the account ID that you have imported is correct. Follow the steps in verify the Region was imported correctly to verify the import details.

  3. If resources are still not appearing, then there could be a problem with the discovery component. Check this by following these steps:

    To retrieve the logs for the API that the discovery service uses:

    1. Sign in to the AWS Management Console in the account you deployed AWS Perspective in.

    2. Choose Services.

    3. From the collection of services, choose Lambda.

    4. Search for GremlinFunction and select it.

    5. Choose the Monitoring tab.

    6. Choose View logs in CloudWatch.

    7. In the Log streams section, select the latest log file link in the table (usually the top entry). This opens up the log file.

    8. Search for "400" or "500". This searches for HTTP 400 or 500 error codes in the log file. If it returns any entries, then it means that there is a problem in the discovery component.

    To retrieve the logs for the discovery component:

    1. Sign in to the AWS Management Console in the account you deployed AWS Perspective in.

    2. Choose Services.

    3. From the collection of services, choose CloudWatch.

    4. Under the Log section, select Log Groups.

    5. Search for the log group /ecs/aws-perspective--<account-ID>--task.

    6. Select the latest Log Stream tab.

    7. Scroll to the top of the page and choose Load More until the No older events at this moment message appears.

    8. Select Actions and then Download search results from the menu.

    9. Save the file locally.

To request assistance from AWS, raise an issue in our GitHub repository. Select create an issue and follow the prompts and include the logs from both the API and the discovery process.