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
  • Map Service to a Resource
  • Mapping Resources to a Service (Bulk Action)
  1. Alert routing & Response Managment

Mapping resources to Services

Last updated 6 months ago

There are two different ways to map services to resources:

  • Map a service to a resource.

  • Map resources to a service (Bulk Action).

Map Service to a Resource

Step 1: Navigate to the Dashboard → Click on Resources → AWS Resources

Here, you'll find information about various resources along with any missing alerts that need to be set up. Map these services to their respective teams or application services to ensure alerts are raised effectively.

Step 2: Navigate to the "Resource Name" column on the left side of the table below, then click on one of the resource names.

Step 3: Click on "Map Service" to select the "Application Service" name and "Environment". This action will assign the team to whom alerts will be raised for the specific service and on the selected Slack channels.

Step 4: After selecting the required service and environment, click on "Map Service" to save the changes.


Mapping Resources to a Service (Bulk Action)

Step 1: Select multiple resources with missing application service by ticking the boxes on the left side of the table.

Step 2: After making your selection, navigate to the "Bulk Actions" menu and click on "Map Service." Then, select an application service and an environment.

Step 3: Finally click on "Map". This action will automatically map the services to the selected resources within a moment.

Navigate to AWS Resources
AWS Resources
Check required boxes
Bulk Action > Map to Service
Select Application Service & Select on Environment