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
  • Service as defined in Temperstack
  • Create a service
  • Example Scenario
  1. Alert routing & Response Managment

Setting up Services

Last updated 4 months ago

Service as defined in Temperstack

In Temperstack's context, a service is a collection or group of linked resources, micro-services, and team members.

Think of service as a unique key that connects a micro-service (one or multiple APIs / apps ), to its resources (EC2, databases, load balancers), cache, and the team that manages it.

Example :

In the above figure, you can see multiple services listed; for example: Payments is a service

Each service has the following attributes visible in the service listing.

  1. Service Name: The name that allows the team to easily identify the microservice group and its corresponding team.

  2. Group Email: The email address where notifications related to this service should be sent.

  3. Slack Channel: The channel where notifications related to the service will be posted.

  4. On-Call Policy: This refers to the rotation and escalation roster of team members used for making phone calls and handling escalations when an incident occurs.

You can learn more about creating and editing a service here : Setting up Services

The service listing enables you to change notification channels on Slack, change the group email ID/change rotation and escalation policy all in one place without needing to edit individual alerts.

  1. Navigate to "Temperstack Notifications" at the top menu in your dashboard.

  2. From there, select "Application Services."

Create a service

  1. Navigate to “Add Service”: Click on the "Add Service" button located at the top right corner of the interface.

  2. Provide Service Details: Enter the required service name and group email ID as per the specific requirements.

  3. Assign a Slack Channel: Specify the Slack channel where notifications will be sent for this service.

  4. Select On-Call Policy: Choose the appropriate on-call policy for handling alerts related to this service.

  5. Notification Preferences: Check the desired notification channels - email, Slack, voice and WhatsApp- by selecting the corresponding checkboxes and then click on "Save Changes". This ensures that alerts are sent through the preferred communication channels for effective incident management.


Example Scenario

In this scenario, a service named "alert_setup" is configured with the following details:

  1. E-mail ID: Notifications related to this service will be sent to "zaSa@gmail.com" via email.

  2. Slack Channel Name: Alerts for this service will be posted in the "#alerts" Slack channel.

  3. Temperstack On-Call Name: The on-call policy designated for handling alerts related to this service is "Demo Policy."

  4. Updated At: The service details were last updated on May 1, 2024, at 7:48:35 PM.

  5. Receive Notification On: Notifications for this service will be received through email, Slack, voice and WhatsApp channels.

This configuration ensures efficient alert distribution across multiple channels, facilitating prompt notification and response by on-call teams.

Illustrative schematic of a service
Application Services > Add Service