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 Splunk
  • API Endpoints in APM
  • Setting Up Alerts on API Endpoints
  • Splunk Service Dependencies
  1. Integrations
  2. Integrating your Observability tools
  3. Setting up Splunk Integration

Managing resources with Splunk

Last updated 5 months ago

Temperstack enhances Splunk's APM capabilities by simplifying the process of managing and monitoring API endpoints within your Temperstack application. This unique feature allows organizations to automatically identify important API endpoints, enabling the setup of alerts and monitoring without manual intervention. By integrating with Splunk, Temperstack streamlines performance monitoring and helps ensure critical API endpoints are closely observed and managed effectively.

APM in Splunk

APM (Application Performance Monitoring) is a comprehensive suite of tools provided by Splunk 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 API endpoints.

API Endpoints in APM

In the context of Application Performance Monitoring (APM), API endpoints are specific URLs or paths that your application exposes to handle various operations. These endpoints are crucial interaction points where client applications make requests to your application, typically to perform CRUD (Create, Read, Update, Delete) operations or other specific tasks.

API Endpoints Metrics Monitored

  • Latency: Evaluates the delay experienced during request processing.

  • Error Rate: Monitors the percentage of requests that result in errors at the API endpoint.

  • Response Time: Measures the time taken for an API endpoint to process a request and return a response.

Setting Up Alerts on API Endpoints

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

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

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

  1. Access API Endpoints: In the same row as "APM Service," find the "Action" column. Click on "API Endpoints" in this column. This will display all the API endpoints that have been automatically configured and added by Temperstack.

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

Splunk Service Dependencies

Service Dependencies refer to third-party APIs that are not part of our system. We make calls to these services from external sources, which include various third-party services like Slack channels, APIs, and other external integrations.

Temperstack automatically identifies and tracks all external services that your application calls. These are displayed in the Service Dependencies section, providing a comprehensive view of all third-party interactions.

You can also set up alerts on these services to ensure that any issues with third-party integrations are quickly identified and addressed.

To find alerts for service dependencies, follow these steps:

  1. Navigate to the Resources -> Splunk Resources.

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

  3. Look for the "APM Service" entry in this column.

  4. Click on "Service Dependencies."

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

Dashboard
Navigate to Splunk Resources
Service Dependencies