Cobrowse.io Docs
  • Getting started
  • SDK Installation
    • Web
    • iOS
    • Android
    • React Native
    • Flutter
    • .NET Mobile
    • macOS
    • Windows
  • SDK Features
    • Account config
    • Identify your devices
    • Use 6-digit codes
    • Redact sensitive data
    • Viewing PDFs
    • Universal Cobrowse
    • Customize the interface
      • Active session controls
      • 6-digit code screen
      • User consent dialog
      • Remote control consent dialog
      • Full device consent dialog
      • Localization / translation
    • Initiate sessions with push
    • Listening for events
    • Full device capabilities
      • Full device screen sharing
      • Full device remote control
      • Managing full device mode
    • Advanced configuration
      • Starting and stopping the SDK
      • Declaring capabilities
      • Intercepting mobile SDK network requests
      • Web
        • IFrames support
        • IE 11 polyfills
        • Cross-domain session support
        • Ignore Views
      • iOS
        • Alternate render method
        • Custom touch handling
      • Android
        • Backporting TLS to older Android versions
  • Agent-side integrations
    • Agent-side overview
    • Platform integrations
      • Zendesk
      • Salesforce
        • Migrating from legacy to v2
        • Salesforce (Legacy)
      • Genesys
        • Genesys Cloud
        • Engage Workspace Web Edition (WWE)
        • Engage Workspace Desktop Edition (WDE)
      • Intercom
      • Freshworks
      • Talkdesk
      • NICE
    • Custom integrations
    • Agent SDK
      • API Reference
      • Sample code snippets
    • Authentication (JWTs)
      • JWT Policies
    • Authentication (SAML 2.0)
    • IFrame embeds
  • Enterprise self-hosting
    • Self-hosting overview
    • Docker Compose
    • Helm chart
      • Image Pull Secret
      • Environment Variables
      • Optional recording components
      • Pod Annotations
    • AWS terraform
      • AWS metrics configuration
    • Azure terraform
      • Azure metrics configuration
    • GCP terraform
      • GCP metrics configuration
    • Sizing guidelines
    • Running your instance
      • Adding a superuser
      • Limiting account creation
      • Limiting magic link recipients
      • Configuring SMTP
      • Managing your deployment
    • Monitoring your instance
      • Available metrics
      • Self-Hosted Prometheus
    • Advanced configuration
      • Air gap configuration
      • Pin web SDK version
      • L7 firewall configuration
      • Docker proxy configuration
    • Troubleshooting
Powered by GitBook
On this page
  • Prometheus scraping settings
  • Configure and deploy ConfigMaps

Was this helpful?

  1. Enterprise self-hosting
  2. Azure terraform

Azure metrics configuration

Configure Cobrowse on Microsoft Azure using the provided Terraform configurations, and seamlessly integrate with Azure Monitor for insightful container metrics.

PreviousAzure terraformNextGCP terraform

Last updated 1 year ago

Was this helpful?

If you are running the Cobrowse Enterprise Azure Terraform configuration, Azure Monitor provides a for its container insights offering. To configure the integration you'll be asked to configure scrape settings (we have configured this already) and deploy a ConfigMap resource.

Prometheus scraping settings

In the section of the Prometheus integration instructions, we will be using the "Cluster-wide" perspective using Pod annotation endpoints. The Cobrowse Enterprise for Azure Terraform configuration already applies all the pod annotations necessary for this integration, so no change to your cluster is required in this section of the instructions.

Configure and deploy ConfigMaps

In the section of the Prometheus integration instructions, you will need to create a new ConfigMap resource in your cluster to configure the Prometheus integration exporter to collect the application metrics.

For convenience, we have provided a sample configuration resource that has the key changes made from the Azure template to enable Prometheus metrics scraping. This configuration file is located in your Cobrowse Enterprise for Azure Terraform directory at path container-azm-ms-agentconfig.example.yaml. The key changes made are:

  • [prometheus-data-collection-settings].[prometheus_data_collection_settings.cluster].monitor_kubernetes_pods

    • Value changed to true

This example configuration will cause all pods in your cluster that have Prometheus scraping enabled in their pod annotations to have their Prometheus metrics collected and sent to Azure Monitor container insights.

If this is cost prohibitive, consider using the fieldpass and fielddrop settings to configure which metrics are collected. Furthermore, if you have multiple namespaces that contain other services whose Prometheus metrics you do not wish to scrape, you can use the monitor_kubernetes_pods_namespaces setting to limit the namespaces where pod metrics are scraped.

More information to help control your Azure Monitor spend can be found in the .

Once the ConfigMap resource is deployed, custom metrics should start being collected and available within the Azure Monitor Logs section of the Azure Portal within a few minutes.

Prometheus integration
Prometheus scraping settings
Configure and deploy ConfigMaps
Container Insights pricing documentation