Azure Stack Hub Billing
Cloud Assert HomeDocs Home
2010.2
2010.2
  • Introduction
  • Release Notes
  • Features
    • Admin Features
      • Settings
      • Pricing Profile
        • Manage Pricing Profiles
      • Usage History
      • Invoice
      • Quotas
      • Credits
        • User Credits
      • Usage & Quota
      • Notifications
      • Health Status
      • Billing Subscriptions
      • Billing Accounts
    • Tenant Features
      • Overview
      • Usage History
      • Invoice
      • Notifications
      • Usage and Quota
      • Billing Profile Creation
  • Installation
    • Prerequisites
      • PKI Certificate Requirements
      • Azure Stack Certification Authority certificate
    • Deployment
      • Install Billing Resource Provider
        • High Availability and Scale Deployment considerations
      • Operations and Monitoring
      • Billing Database and Log File Configuration
      • License Activation
      • Update VConnect Resource Provider With Billing Details
    • Configuration
      • Setup pricing profile and quotas
      • Invoice
      • Add Billing service to Azure Stack Plan
      • Add the resource provider in Tenant Portal
      • Mapping Subscriptions
      • How to add a new stamp as a connection?
    • Updates
      • Core Billing
      • Billing RP
    • Remove Resource Provider
  • Others
    • Troubleshooting
      • Cost Management
    • Multi-Stamp Azure Stack Hub
Powered by GitBook
On this page

Was this helpful?

  1. Installation
  2. Deployment

Operations and Monitoring

Add monitoring rules for the following components in your environment via monitoring tools like SCOM and associated Management Packs:

  • Windows Servers

  • SQL Server

  • IIS Web Server (in API Machines)

  • API End points

  • Billing Agent Service

You may in addition add monitoring for:

  • DB growth and/or the Disk(s) hosting Billing Database is monitored for performance and more importantly Available Free Space.

  • Event logs for Error level entries - though, beware of many false positives here. Only add monitoring of specific events if you have seen helping identify issues.

  • Down level source systems and dependencies like:

    • Microsoft Azure Stack (MAS) usage endpoint

    • Windows Azure Pack (WAP) usage endpoint

    • Active Directory and/or ADFS, if your environment depends on it

Having the operations team educated and routed with automated alerts is also essential to prevent failures and to enable faster recovery from any failures.

PreviousHigh Availability and Scale Deployment considerationsNextBilling Database and Log File Configuration

Last updated 5 years ago

Was this helpful?