You need to enable the standard observability components before using them. To do this, navigate to Administrator -> Observability -> Standard -> Settings and follow the instructions in the rest of this section.

The Metrics control plane uses Grafana, Prometheus, and Yace. They are only deployable in Default Tenant.

Navigate to Administrator -> Observability -> Standard -> Settings. Select the Monitoring tab to enable Metrics, and click the Enable Monitoring link.

In the Monitoring tab, select Enable Centralized Monitoring.

Below, the Monitoring view is shown after the metrics have been enabled. cAdvisor and Node Exporter collect metrics. Selecting a Tenant deploys the containers on all the Hosts in that Tenant.

In the DuploCloud Portal, navigate to Observability -> Standard -> Metrics to view various metrics per Tenant.

The DuploCloud AOS dashboards are a gateway to the detailed Grafana dashboards, serving two purposes:

• SSO and Authentication Proxy: The Grafana dashboards reside on a private network. DuploCloud acts as an authentication layer, connecting the same single sign-on (the DuploCloud login) to a Grafana session.

• Summarizing Links: While AOS contains many pre-configured Grafana dashboards, you can create quick links with descriptions of the ones you use most frequently. See Customizing Dashboards for more information.

Administrator and Tenant AOS Dashboards

Depending on your (Administrator or User), you can access the Advanced Observability Suite dashboard from two locations in the DuploCloud Portal.

1. The displays cloud data across all resources and allows you to select DuploCloud Infrastructures. To use it, navigate to Administrator -> Observability -> Advanced -> Dashboard in the DuploCloud Portal.

2. The displays data by Tenant. To use it, navigate to Observability -> Advanced -> Dashboard in the DuploCloud Portal.

Grafana Dashboards

The integration between DuploCloud AOS and Grafana ensures that you can seamlessly transition between high-level monitoring and detailed data analysis. Whether you need to troubleshoot a log entry, trace a request’s path, monitor resource usage, or track performance metrics, the ability to click through from the AOS Dashboard to the corresponding Grafana dashboards makes it easier to investigate and resolve issues.

From the DuploCloud AOS Dashboards, you can navigate directly to the Grafana dashboards for detailed data:

• Service Overview Dashboard: Click the Grafana link from the AOS dashboard and navigate to Integration-APM -> Service Overview Dashboard. This dashboard provides a high-level summary of the performance of your services, showing key metrics such as request rates, error rates, and other service-level indicators. It allows you to monitor the health of your services and quickly identify any issues that may need attention.

• From the DuploCloud AOS Dashboard, you can easily navigate to corresponding Grafana dashboards for deeper insights. Simply click the links in the following panels to access detailed data:

  • Logs: Dive into the Grafana Logging Dashboard

Navigate to Administrator -> Observability -> Standard -> Settings, and select the Logging tab to enable Logging. Click on Enable Logging.

Logging is based on OpenSearch and Kibana, deployed in the Tenant of your choice, and configurable, as shown below.

After enabling logging, choose which Tenants to collect logs from. The platform deploys collectors for each Tenant that you enable. Filebeat is the collector for Logs.

Access the Standard suite by navigating to Observability -> Standard -> Dashboard.

Using DuploCloud's Standard Observability Suite, you have access to:

• Comprehensive logging

• Metrics

To use the Standard version, first proceed to .

DuploCloud provides a default Kibana URL for viewing Logging data, but if you want to update filters or customize further, you can override the default with these settings.

Configuring a Custom Kibana Logging URL

1. Log in to the DuploCloud Portal.

2. Navigate to Administrator -> System Settings -> System Config.

3. Click Add. The Add Config pane displays.
4. In the Config Type list box, select AppConfig.

5. In the Key list box, choose one of the following keys:

   • Kibana Base URL: This URL points to the proxy or direct access Kibana URL.

   • Kibana Logs URL Template: This URL template links to Kibana’s Logs.

6. In the Value field, enter the custom URL for the selected key. For example:

   • Kibana Base URL: /proxy/kibana

   • Kibana Logs URL Template: https://kibana.example.com/app/discover#/?_a=(query:(language:kuery,query:'log_type:"application"'))&_g=(time:(from:now-1h,to:now))

1. Click Submit to save the configuration.

After configuring the Kibana URL in DuploCloud, you can access the selected Kibana Logs data directly from the DuploCloud Portal:

• Navigate to Administrator -> Observability -> Standard -> Logging.

DuploCloud provides a default Kibana URL for viewing audit logs, but if you want to update filters or customize further, you can override the default with these settings.

Configuring a Custom Kibana Audit URL

1. Log in to the DuploCloud Portal.

2. Navigate to Administrator -> System Settings -> System Config.

3. Click Add. The Add Config pane displays.
4. In the Config Type list box, select AppConfig.

5. In the Key list box, choose one of the following keys:

   • Kibana Base URL: This URL points to the proxy or direct-access Kibana instance.

   • Kibana Audit URL Template: This URL template links to Kibana’s Audit logs.

6. In the Value field, enter the custom URL for the selected key. For example:

   • For Kibana Base URL: /proxy/kibana

   • For Kibana Audit URL Template: https://kibana.example.com/app/discover#/?_a=(query:(language:kuery,query:'log_type:"audit"'))&_g=(time:(from:now-1h,to:now))

1. Click Submit to save the configuration.

After configuring the Kibana URL in DuploCloud, you can access Kibana Audit data directly from the DuploCloud Portal:

• Navigate to Administrator -> Observability -> Audit.

The DuploCloud Standard Observability Suite generates audit trails using OpenSearch. Enabling logging is a prerequisite for audit functionality.

In the DuploCloud Portal, navigate to Administrator -> Observability -> Standard -> Settings -> Audit and click the Enable Audit link.

Once enabled, the Audit view is accessible at Administrator -> Observability ->Audit. See the Auditing topic for further details.

Viewing detailed auditing diagnostics

To view complete auditing reports and logs, navigate to the Observability -> Audit page in the DuploCloud Portal.

DuploCloud Standard Observability Suite uses built-in OpenSearch for log storage and search. Filebeat is the collector deployed on each host to gather logs from containers and other system services.

Logs can be accessed at the platform level (by Administrators), at the Tenant level, or directly from a specific Service using the Logs link.

Viewing Platform Logs

Use this option to view logs across all tenants or to troubleshoot issues at the platform level.

DuploCloud's Advanced Observability Suite (AOS) is an add-on service to boost your monitoring and troubleshooting abilities. Built on OpenTelemetry, our AOS leverages CloudWatch, LGTM (Loki, Grafana, Tempo and Mimir), and Pyroscope to deliver robust observability for your cloud infrastructure. It includes real-time anomaly detection and customizable alerts and unifies metrics, traces, logs, and profiles to track all aspects of your environment easily.

The Grafana-powered dashboards spotlight key metrics and visualize trends in real-time, empowering swift, data-driven decisions. Additionally, AOS leverages object storage solutions like S3, GCS, and Storage Accounts, making it extremely cost-effective. Overall DuploCloud’s AOS simplifies troubleshooting and enhances system health by providing a holistic view of your application and infrastructure performance.

About OpenTelemetry

a project under the Cloud Native Computing Foundation (CNCF), supports multiple programming languages and environments and provides a flexible, vendor-neutral framework for monitoring and analyzing application performance. Designed for high scalability and ideal for distributed applications, OpenTelemetry is the industry standard for observability. See the

The Tenant AOS Dashboard provides cost and observability data by Tenant for granular infrastructure management. It is accessible to non-administrators who have access to the selected Tenant.

To access the Tenant AOS Dashboard, navigate to Observability -> Advanced -> Dashboard.

Selecting a Tenant

You can use the Tenant list box at the top of the Tenant AOS Dashboard to select the Tenant for which you want to view metrics.

DuploCloud ships with a standard suite of observability tools built into the platform. An extensible add-on suite of advanced diagnostic and monitoring tools, the DuploCloud Advanced Observability Suite based on OpenTelemetry, is also available for a monthly cost.

• The Standard Edition includes:

  • Logging using OpenSearch and Kibana

DuploCloud allows automatic alert generation for resources within a Tenant. This ensures that the defined monitoring baseline is applied to all current and new resources based on a set of rules.

Creating an Alert

As an Administrator:

1. From the DuploCloud portal, navigate to Administrator

DuploCloud's Advanced Observability Suite (AOS) allows you to manage Grafana resources, such as dashboards and alerts, using Infrastructure as Code (IAC) through the Grafana Terraform provider. This integration simplifies the authentication process by providing a proxy that automatically handles authentication with DuploCloud’s session tokens, eliminating the need to manage Grafana API tokens manually (see the Terraform example below). For more information, see the Terraform documentation.

terraform {
  required_providers {
    grafana = {
      source  = "grafana/grafana"
      version = "3.13.2"
    }
  }
}

provider "grafana" {
  url  = "https://grafana-proxy-......./"
  auth = "anonymous"
  http_headers = {
    Authorization = "Bearer <<DUPLO_SESSION_TOKEN>>"
  }
}

resource "grafana_folder" "folder" {
  title  = "terraform"
}

DuploCloud’s Advanced Observability Suite (AOS) supports custom metrics collection and visualization, enabling you to monitor application-specific metrics in addition to default Kubernetes metrics. This guide will walk you through the steps to configure your applications to expose custom metrics and make them available in DuploCloud AOS.

Configuring Annotations for Scraping Custom Metrics

k8s_grafana_com_scrape: true
k8s_grafana_com_job: custom-metrics
k8s_grafana_com_metrics_path: /metrics
k8s_grafana_com_metrics_portNumber: 9100

The Administrator AOS Dashboard displays cloud data across all resources and infrastructures. It is only accessible to Administrators.

To access it, navigate to Administrator -> Observability -> Advanced -> Dashboard.

Viewing Admin Cloud Spend Data

The Cloud Spend area, on the left side of the Advanced AOS Dashboard, offers a comprehensive, real-time view of expenses across all resources.

• Fin Ops: The Fin Ops button, in the Cloud Spend header, opens the DuploCloud Billing dashboard, which displays billing details including billing summaries by month or Tenant, billing alerts, and DuploCloud license usage information.

• Current Month: Displays cloud expenditures for the current month.

• Monthly Spend: Displays spending by month. Use the Monthly Spend list box to display spending by week or day.

Viewing Admin Observability Data

The Observability section, on the right side of the Advanced AOS Dashboard, gives real-time health and usage data across resources.

• Infrastructure: In the Observability header, the Infrastructure list box allows you to select the Infrastructure for which you wish to view observability details.

• Grafana: The Grafana button, in the Observability header, opens the Grafana console where you can add, customize, or edit your dashboards, query your logs, metrics, and traces, and more. For additional information, see the .

Under the Observability header are data cards displaying the following metrics:

• Resources: Lists the type and number of DuploCloud resources, such as Tenants, Services, etc.

• K8s/Docker: Shows Kubernetes and Docker metrics, providing visibility into containerized workloads.

• Logs: Displays logs for troubleshooting and compliance checks across all resources.

• Metrics: Displays rate, errors, and duration metrics across Services.

For Grafana-generated metrics (e.g., K8s/Docker, Logs, Metrics, Traces, Profiles), you can click on the card to open the corresponding detailed view in the Grafana console. Additionally, you can .

DuploCloud's Advanced Observability Suite (AOS) metrics pipeline leverages AWS CloudWatch for capturing critical metrics such as CPU utilization, memory usage, and Lambda execution times, Grafana Mimir as the backend for scalable and high-availability metrics storage, Grafana as the visualization tool for intuitive dashboard creation, and Grafana Alloy for bundling tools like Beyla and OpenTelemetry SDKs to collect metrics from applications and infrastructure. Out-of-the-box metrics combine with custom application-level metrics, to create unified dashboards that correlate infrastructure and application performance for a comprehensive view of system health.

About RED Metrics

RED metrics (Rate, Errors, Duration) are critical for monitoring and understanding the health and performance of distributed systems and microservices. When integrated into a Grafana dashboard using OpenTelemetry, they provide essential insights for diagnosing issues and optimizing performance, such as:

• Rate: Tracks the number of requests per second, indicating the system's throughput. A sudden drop can highlight service degradation or bottlenecks.

• Errors: Measures the percentage or count of requests that fail. This helps quickly identify stability issues or breaking changes in your service.

• Duration: Monitors the time to process requests, providing insights into system latency. High durations can indicate inefficiencies or resource constraints.

Displaying Metrics in the DuploCloud Advanced Observability Suite (AOS)

1. In the DuploCloud Portal, navigate to Administrator -> Observability -> Advanced -> Dashboard (Administrator AOS Dashboard) or Observability -> Advanced -> Dashboard (Tenant AOS Dashboard). The AOS Dashboard displays.

2. Select your Infrastructure from the Infrastructure list box (Administrator AOS Dashboard) or Tenant from the Tenant list box (Tenant AOS Dashboard).

3. Click the Metrics card button. The Grafana APM -> RED Metrics

Exploring Detailed Metrics

From the Grafana Beyla RED Dashboard, navigate to Grafana Dashboards in the left pane. Various out-of-box metrics and visualizations are available to you without creating specific queries.

For example, by selecting K8s Resource Monitoring from the Dashboards page, you can view numerous Kubernetes widgets depicting resource usage of Kubernetes Pods and containers, among other helpful performance data.

Click the Add button and select from the displayed list to add additional customizations and visualizations to a dashboard.

A profile is essentially a snapshot of your application's performance metrics at a specific point in time. DuploCloud’s Advanced Observability Suite (AOS) uses Pyroscope to provide detailed application profiles. These profiles give you detailed insights into how resources like CPU and memory are being used and help you optimize performance and monitor resource usage.

Pyroscope integrates seamlessly with DuploCloud’s other observability tools, like Tempo (for tracing) and Beyla (for telemetry). This allows you to view profiling data alongside traces and logs in Grafana for a unified monitoring experience. The combination of automatic profiling with the option for manual fine-tuning using OpenTelemetry SDKs helps capture the most relevant data for optimizing application performance.

By default, CPU profiles are collected for all applications, while memory profiles are specifically collected for Go and Java applications, providing deeper insights into performance and resource utilization.

Enabling Profiling

To enable application profiling, you can push profiling data directly to Pyroscope by . For detailed instructions on configuring the client, refer to the .

What Profiles Can Tell You

Pyroscope is the backend for profiles that show the CPU and Memory profile for the application. Exploring profiles helps identify and resolve performance issues, optimize resource usage, and improve efficiency. Key benefits include:

• Identifying Performance Bottlenecks: Pinpointing slow functions or resource-heavy processes.

• Optimizing Resource Utilization: Analyzing CPU and memory usage for better scaling decisions.

• Debugging Latency Issues: Detecting areas with high latency that may affect user experience.

• Root Cause Analysis: Correlating profiling data with logs and traces to identify the cause of performance issues.

Exploring Profiles in the DuploCloud Advanced Observability Suite

1. In the DuploCloud Portal, navigate to Administrator -> Observability -> Advanced -> Dashboard (Administrator AOS Dashboard) or Observability -> Advanced -> Dashboard (Tenant AOS Dashboard). The AOS Dashboard displays.

2. Select your Infrastructure from the Infrastructure list box (Administrator AOS Dashboard) or Tenant from the Tenant list box (Tenant AOS Dashboard).

3. Click the Profiles card. The Grafana Profiling dashboard displays.

For more information about profile data, see the .

The Profiling Dashboard provides detailed insights into how your application utilizes resources such as CPU and memory.

You can also view Flame Graphs, which show the call stack and resource consumption, making it easier to identify the specific functions causing performance issues. The Explain Flame Graph feature further analyzes the data, offering insights into bottlenecks and suggesting optimizations for improved performance.

Viewing Profiles and Traces in Grafana

You can use the Explore feature in Grafana to . This allows you to correlate profiling and trace data for deeper insights into your application's performance. To learn more, check out the .

Advanced Observability Suite (AOS) is based on OpenTelemetry. The following graphic shows the various components.

Viewing the DuploCloud Deployment of the OpenTelemetry Stack

To view the complete deployment of the OpenTelemetry stack:

1. In the DuploCloud Portal, navigate to Administrator -> Observability -> Advanced -> Dashboard.

2. In the Observability area, click the K8s/Docker card. The Grafana K8s Resource Monitoring dashboard launches, giving you a detailed view of resources and monitoring for Kubernetes nodes, Docker containers, and Pods.

Viewing OpenTelemetry Data in DuploCloud

OpenTelemetry data is stored in S3 Buckets, which you can view in the DuploCloud Portal.

1. In the DuploCloud Portal, select the OpenTelemetry_Tenant from the Tenant list box at the top of the Portal.

2. Navigate to Cloud Services -> Storage and select the S3 tab to view the data. This data setup is deployed and managed via release infrastructure.

To view a complete list of Kubernetes Services in an OpenTelemetry deployment, select the OpenTelemetry_Tenant from the Tenant list box at the top of the Portal and navigate to Kubernetes -> Services.

To view a complete list of Docker Containers in an OpenTelemetry deployment, select the OpenTelemetry_Tenant from the Tenant list box at the top of the Portal and navigate to Kubernetes -> Containers.

DuploCloud's Advanced Observability Suite (AOS) leverages for tracing, with and as the data collectors. Beyla, powered by eBPF (extended Berkeley Packet Filter), enables seamless collection of observability data directly from the system kernel without requiring application-level instrumentation. By attaching to system events like network requests and function calls, Beyla efficiently gathers metrics and traces. For more detailed trace information, users can , integrating traces into logs for enhanced observability.

What Tracing Can Tell You

Tracing with OpenTelemetry is useful in scenarios where you want to identify, analyze, and resolve performance issues or understand the flow of requests through a distributed system. Tracing is helpful for:

DuploCloud AOS users can tailor observability for their Kubernetes clusters by managing OpenTelemetry stacks and configuring Grafana dashboards to meet specific needs. Additionally, custom links can be added to AOS dashboard cards, enabling seamless integration with external tools or data sources.

By default, each Kubernetes cluster in DuploCloud has its own dedicated OpenTelemetry (OTEL) stack. If you need to share an OTEL stack across multiple clusters, contact DuploCloud Support.

Configuring OpenTelemetry Cards

In the AOS dashboard, the OpenTelemetry section features five cards that link to Grafana dashboards. To configure these cards and their links, go to Administrator -> System Settings -> System Config in the DuploCloud Portal and search for

DuploCloud's Advanced Observability Suite (AOS) integrates Grafana Loki as the logging backend, with Grafana Alloy acting as the log collector. This setup enables real-time log visualization, filtering, and analysis through Grafana, providing a unified observability experience alongside metrics and traces.

Grafana Loki powers the logging solution by indexing enriched metadata, including Kubernetes attributes such as Tenant name, Namespace, container, and Host, which DuploCloud automatically configures for every log entry. This enriched metadata simplifies querying and allows users to easily drill down into issues or switch from logs to traces directly from the dashboard to identify problems quickly.

What Logs Can Tell You

Logs are crucial for observability, offering detailed, time-stamped insights into system behavior. They enable you to:

Grafana's native Alert manager is used for alerting within the DuploCloud Advanced Observability Suite (AOS). DuploCloud's AOS includes a default set of alerts based on best practices and compliance standards. Custom alerting can also be set up to meet your unique needs based on log strings, metrics, etc.

Default Alerts

When you enable AOS, a set of alerts is automatically available in Grafana. These alerts cover common health and performance issues for Linux nodes and Kubernetes clusters, helping you monitor critical infrastructure without extra setup.

The default alerts include:

These alerts are provided automatically in Grafana for AOS. Any additional alerts beyond these categories must be manually created.

Configuring Custom Alerts

Any alerting beyond the default node and Kubernetes integrations must be created manually. For example, you might add alerts based on:

• Application-specific error logs (e.g., HTTP 500 spikes).

• Business KPIs (e.g., queue depth, transaction rates).

• Service-level metrics such as latency or availability.

These types of alerts can be defined directly in Grafana to suit your organization’s needs. To create or manage them, follow these steps:

1. From the DuploCloud Portal, navigate to one of the following dashboards:

   • Admin AOS Dashboard: Administrator → Observability → Advanced → Dashboard

   • Tenant AOS Dashboard: Observability → Advanced → Dashboard

The DuploCloud OpenTelemetry (OTEL) stack requires specific resources for deployment. The implementation features node-level components, deployed as DaemonSets, for telemetry collection and central observability components for data aggregation, processing, and visualization. Object storage is the backbone for retaining metrics, logs, traces, and profiling data, ensuring scalability and long-term accessibility.

OTEL Resource Requirements

Service Level Objectives (SLOs) are metrics that define the desired reliability and performance targets for a service. Powered by Service Level Indicators (SLIs) such as latency, availability, and error rates, SLOs provide a precise measure of whether your service is meeting its goals. With SLOs integrated into DuploCloud’s Advanced Observability Suite (AOS), you benefit from automated dashboards, real-time performance monitoring, and proactive alerting. These capabilities empower you to continuously monitor and optimize your service's health for a seamless user experience.

DuploCloud streamlines the management of SLOs by integrating them with Grafana, where users can easily create and modify SLO configurations. Instead of manually editing backend files or complex configurations, DuploCloud uses a business form to simplify the process. This form is available in the DuploCloud UI through Grafana, where you can submit your SLO request with a few clicks.

Once submitted, the request is automatically processed by the Duplo-automation service. This powerful service takes care of creating and configuring the necessary backend resources, rules, and alerts based on your input. This automation reduces manual intervention and ensures that your SLO setup is quick, efficient, and error-free.

Faults that happen in the system, be it Infrastructure creation, container deployments, Application health checks, or any Triggered Alarms can be tracked in the DuploCloud portal under Faults Menu.

Viewing Faults

You can look at Tenant-specific faults under Observability -> Faults or all the faults in the system under Administrator -> Faults.

The creation of a Web Application Firewall (WAF) is a one-time process. Create a WAF in the public cloud Console, fetch the ID/ARN, and update the Plan in DuploCloud. Once updated, the WAF can be attached to the Load Balancer.

Creating a Web Application Firewall (WAF)

When you create a WAF in DuploCloud, an entry is added to the . You use this entry to attach an ALB Load Balancer to your WAF.

DuploCloud supports viewing of Faults in the portal and sending notifications and emails to the following systems:

• Sentry

• PagerDuty

• NewRelic

• OpsGenie

You will need to generate an keys from each of these vendor systems, and then provide that key to DuploCloud to enable integration.

Generating an Integration Key from Sentry

1. In the website, navigate to Projects -> Create a New Project.

2. Click Settings -> Projects -> project-name -> Client keys. The Client Keys page displays.

3. Complete the DSN fields on the screen.

Generating an Integration Routing Key from PagerDuty

1. In the website home page, select the Services tab and navigate to the service that receives Events. If a Service does not exist, click New Service. When prompted, enter a friendly Name (for example, your DuploCloud Tenant name) and click Next.

2. Assign an Escalation policy, or use an existing policy.

3. Click Integration.

Generating an Integration Key from NewRelic

1. In the website, use the to generate an to send events to NewRelic Insights.

2. In the DuploCloud Portal, navigate to Observability -> Faults.

3. Click Update Notifications Config. The Set Alert Notifications Config pane displays.

OpsGenie

1. In the website, .

2. In the DuploCloud Portal, navigate to Observability -> Faults.

3. Click Update Notifications Config. The Set Alert Notifications Config pane displays.

DuploCloud leverages automated instrumentation with and the to provide robust monitoring and tracing without extensive manual configuration. With Grafana Beyla, users can get automatic instrumentation for a wide range of languages, capturing key metrics and trace spans with minimal setup. For languages and use cases not covered by Beyla, users can manually instrument their applications using OpenTelemetry, offering full flexibility to capture detailed telemetry data where automated options are unavailable.

Automated Instrumentation

Set billing alerts based on the previous month's spending or define a custom threshold. Receive email notifications if the current month's expenses exceed a specified percentage of the threshold.

Set up billing alerts in DuploCloud to monitor and manage AWS cloud spending. Alerts can help you stay within budget by notifying you when expenses exceed a defined threshold. DuploCloud supports two types of billing alerts:

• Administrator Billing Alerts monitor total usage across all Tenants.

• Tenant Billing Alerts track spending within an individual Tenant.

Each alert compares current monthly usage against either the previous month’s spending or a custom threshold, and sends email notifications when a specified percentage is reached.

Creating a Billing Alert

Billing alerts can be created at two levels: Administrator alerts monitor overall cloud spending across all tenants, while Tenant alerts focus on the usage within a specific Tenant. Choose the appropriate section in the DuploCloud Portal based on the scope you want to monitor.

1. In the DuploCloud Portal, navigate to Administrator → Billing for Administrator-level alerts or Cloud Services → Billing for Tenant-level alerts.

2. Click Add to create a new billing alert. The Add Billing Alert Config pane displays.
3. Complete the fields (shown in the table below) according to your alert preferences.

1. Click Submit to save your alert. The alert appears in the Billing Alerts tab and will trigger email notifications when conditions are met.

Viewing Billing Alerts

To view detailed information about a billing alert:

1. In the DuploCloud Portal, navigate to Administrator → Billing for Administrator-level alerts or Cloud Services → Billing for Tenant-level alerts.

2. Select the Billing Alerts tab.

3. Select the billing alert you want to view from the NAME column.

Managing Billing Alerts

You can view billing alert details, edit alert configurations, or delete alerts as needed directly from the DuploCloud Platform.

1. In the DuploCloud Portal, navigate to Administrator → Billing for Administrator-level alerts or Cloud Services → Billing for Tenant-level alerts.

2. Select the Billing Alerts tab.

3. Click the menu icon () in the row of the billing alert you want to manage.

Additional Resources

For cost management and billing data details related to your specific cloud provider, see the associated sections in the DuploCloud documentation: