Temperstack
Main WebsiteFeaturesPricingBlogAbout usRequest a Demo
  • Overview
    • What is Temperstack?
    • Use Cases
  • User Managment
    • Getting started as Admin
      • Inviting Users
      • Mapping multiple services to a Team
      • Single Sign-On (SSO)
      • Customising ALCOM Audit & scanning
    • Getting Started as a User /Responder
    • Managing profile & contact details
  • Integrations
    • Integrating your Observability tools
      • Setting up AWS Integration
        • Multiple AWS Account Integration
        • IAM Setup Guide
          • Creating IAM User: Temperstack with Policy
          • Creating IAM Role: Temperstack with Policy
      • Setting up Microsoft Azure Integration
        • Creating Access for Temperstack in Azure
      • Setting up Google Cloud Platform Integration
        • Creating Access for Temperstack in GCP
      • Setting up Datadog Integration
        • Creating Access for Temperstack in Datadog
        • Managing resources with Datadog
      • Setting up NewRelic Integration
        • Creating Access for Temperstack in NewRelic
        • Managing resources with New Relic
      • Setting up Splunk Integration
        • Creating Access for Temperstack in Splunk
        • Managing resources with Splunk
      • Setting up Appdynamics Integration
        • Creating Access for Temperstack in Appdynamics
        • Managing resources with Appdynamics
      • Setting up Dynatrace Integration
        • Creating Access for Temperstack in Dynatrace
        • Managing resources with Dynatrace
      • Setting up Oracle Cloud Infrastructure
        • Creating Access for Temperstack in OCI
    • Integrating Custom Alerts & Other Alerting sources
      • Webhook Integration
      • Ingesting Emails as alerts
      • Integrating alert listeners from other observability tools
  • Alert routing & Response Managment
    • On-call scheduling and Escalation Policies
    • Setting up Services
    • Alert notification channels
      • Integrating Slack channels
      • Integrating MS Team
    • Mapping resources to Services
      • Rule based resource to Service Mapping
      • Using AI suggested mapping rules
    • Testing Alerting and Notifications
    • Responding to Alerts
  • Monitoring
    • Setting up and maintaining Comprehensive alerting
      • Alerting Templates- metrics & customisation
      • ALCOM and identifying monitoring gaps
      • Programmatically setting up missing alerts in your Observability tool
      • Alert noise Reduction & Optimisation
  • Uptime Monitoring
    • Real time Availability Monitoring
  • Incident analysis & communication
    • External and Internal service Status Pages
      • Instruction to migrate subscribers from Statuspage
  • AI-Powered Issue Resolution
    • AI powered contextual Runbooks
    • Incident command - alert grouping by incident
    • AI Powered Root cause Identification
  • Reporting & Governance
    • Temperstack Dashboard
    • SLO Dashboard
    • MTTA MTTR
  • Billing & Help
    • FAQs
    • Support
Powered by GitBook
On this page
  • APM in AppDynamics
  • Business Transactions in APM
  • Key Business Transaction Metrics Monitored
  • Setting Up Alerts on Business Transactions
  • External Services and Database in AppDynamics
  • Key metrics monitored for both external services and databases
  • Setting Up Alerts on External Services and Database
  1. Integrations
  2. Integrating your Observability tools
  3. Setting up Appdynamics Integration

Managing resources with Appdynamics

Last updated 5 months ago

Temperstack enhances AppDynamics' Application Performance Management (APM) capabilities by simplifying the process of managing and monitoring key business transactions within your application. By integrating with AppDynamics, Temperstack streamlines performance monitoring and helps ensure critical transactions are closely observed and managed effectively.

APM in AppDynamics

AppDynamics' Application Performance Management (APM) is a comprehensive suite of tools designed to help developers and operations teams monitor and improve the performance of their applications. APM provides detailed insights into application performance by tracking various metrics and business transactions.

Business Transactions in APM

In the context of AppDynamics APM, business transactions refer to the series of operations or requests that your application handles. These can be individual user requests, background jobs, API calls, or any unit of work that your application processes. AppDynamics APM monitors these business transactions to provide detailed performance data.

Key Business Transaction Metrics Monitored

  • Average Response Time (ms)

  • Calls per Minute

  • Errors per Minute

  • Average CPU Consumption (ms)

  • Average Wait Time (ms)

Setting Up Alerts on Business Transactions

  1. Log in to Temperstack Dashboard: Start by logging in to your Temperstack dashboard using your credentials.

  1. Navigate to Appdynamics Resources: Once logged in, go to the Appdynamics resources section. This is where you can manage and monitor your application performance.

  1. Find the Application Section: In the Appdynamics resources, scroll down to locate the "Type" column. Look for the "Application" entry in this column.

  1. Access Transactions: - In the same row as "Application," find the "Action" column. - Click on "Transactions" in this column. This will display all the transactions that have been automatically configured and added by Temperstack.

  1. Set Up Alerts: Use the provided options to set up alerts on the desired Business Transactions

External Services and Database in AppDynamics

External services in AppDynamics refer to third-party APIs and databases that are not part of your core application but are essential for its functionality. These include various third-party services like Slack channels, APIs, other external integrations, and databases.

Temperstack enhances AppDynamics' capabilities by automatically identifying and fetching information about all external services and databases that your application interacts with. This information is displayed in the External Services section of AppDynamics, providing a comprehensive view of all third-party interactions and database operations.

Key metrics monitored for both external services and databases

  • Average Response Time (ms)

  • Calls per Minute

  • Errors per Minute

These metrics allow you to track the performance and reliability of your external dependencies and database operations, ensuring optimal application performance.

You can also set up alerts on these services and databases to ensure that any issues with third-party integrations or database operations are quickly identified and addressed. This proactive approach helps maintain the overall health and performance of your application ecosystem.

Setting Up Alerts on External Services and Database

  1. Navigate to the Resources -> Appdynamics Resources.

  2. Scroll down to locate the "Type" column.

  3. Look for the "Application" entry in this column.

  4. Click on "External Services."

  1. Select any service for which you need to set up alerts.

Dashboard
Navigate to AppDynamics Resources