Authored by Cory_Matieyshen, this article addresses alternatives to the now-retired Azure Dependency Agent, sharing suggestions and key features of recommended solutions.

Summary

Cory_Matieyshen addresses the retirement of the Azure Dependency Agent, a tool previously used for application dependency mapping and insights within Azure environments. The official guidance suggests turning to Azure Marketplace products but does not specify suitable replacements, prompting community discussion for more actionable recommendations.

Community Suggestions

A response by community member Kidd_Ip provides a list of potential alternatives, each with different strengths:

  • Device42: Provides full-stack discovery, detailed app dependency mapping, and supports both hybrid and cloud environments.
  • Datadog: Known for comprehensive infrastructure monitoring, application performance management (APM), log management, and real-time observability.
  • Faddom: Offers passive mapping via network traffic, hybrid visibility capability, and requires no credentials to operate.
  • Dynatrace: Delivers unified observability, process automation, distributed tracing, and utilizes AI-powered insights.
  • AppDynamics: Focuses on full-stack monitoring with a business-centric perspective, backed by Cisco.

Main Topics Covered

  • The impact of Azure Dependency Agent retirement on monitoring and mapping needs.
  • Azure-specific challenges when selecting a comparable replacement.
  • Feature highlights of suggested alternative products.
  • Ongoing community engagement to gather real-world experiences and informed recommendations.

Takeaways

  • Azure users impacted by the retirement of the Dependency Agent should evaluate commercial tools on the Azure Marketplace for their specific monitoring and dependency mapping needs.
  • Important criteria include feature breadth, ease of integration with Azure, support for hybrid environments, and credential requirements.
  • Community feedback can be instrumental in selecting the right solution.

References

This post appeared first on “Microsoft Tech Community”. Read the entire article here