Skip to content

Cloudwatch dashboard does not show Igraph(PMET) metrics

0

I am trying to add igraph(PMET) metrics to a CloudWatch Dashboard. With identical metric query parameters, for the same account, same region, I can see the metric in igraph, this means the metrics are being received by igraph. But cloudwatch with the same metric parameters shows empty result. In the same dashboard, I do see PMET metrics in another marketplace.

Igraph metric parameters

Schema Name: Service

DataSet: Test:Prod

Marketplace: aws-cookie-monster-devo.amazon.com

HostGroup: ALL

Host: ALL

ServiceName: CMEventProcessor

MethodName: ALL

Client: ALL

MetricClass: NONE

Instance: NONE

Metric: HM_TLS.HM_CERT.VALIDATION_SUCCESS

Enter image description here

CW metric parameters

[ "Service", "HM_TLS.HM_CERT.VALIDATION_SUCCESS", "Client", "ALL", "DataSet", "Test:Prod", "Host", "ALL", "HostGroup", "ALL", "Instance", "NONE", "Marketplace", "aws-cookie-monster-devo.amazon.com", "MethodName", "HM_TLS.VALIDATION", "MetricClass", "NONE", "ServiceName", "CMEventProcessor", { "label": "CMEventProcessor-us-east-1-devo", "accountId": "igraph", "stat": "Sum", "region": "us-east-1" } ],

1 Answer
0

Hi Waizi,

Let's dive into your issue now.


Clarifying the Issue

The issue you're facing—CloudWatch Dashboard not displaying Igraph(PMET) metrics—might be rooted in permissions, data publishing gaps, or subtle mismatches in your metric query. Even though the metrics are visible elsewhere, CloudWatch requires specific configurations and permissions to display them properly. Let’s break this down step by step, with permissions being the first thing to check.


1. Verify IAM Permissions

CloudWatch requires appropriate IAM permissions to access and display metrics:

  • Ensure the IAM role or user querying CloudWatch has these permissions:
    • cloudwatch:GetMetricData
    • cloudwatch:ListMetrics

To confirm that CloudWatch has visibility into the metrics, run the following command in the AWS CLI:

aws cloudwatch list-metrics --namespace "Service" --region us-east-1  

If the expected metrics do not appear, it’s likely due to permissions or an issue with the namespace.


2. Check Metric Data Consistency

While Igraph confirms metrics are being received, subtle mismatches might prevent CloudWatch from displaying them:

  • Double-check the metric parameters (e.g., Service, DataSet, HostGroup, ServiceName) for spelling and casing consistency.
  • Confirm you’re querying the correct region (us-east-1 in your case).

3. Verify Namespace and Metric Visibility

CloudWatch relies on a specific namespace for metrics. Ensure that the PMET metrics are being pushed to the expected namespace:

  • Namespaces must match exactly what CloudWatch expects. Even small differences, such as extra spaces or casing, can prevent the metric from appearing.
  • Use the AWS CLI to confirm that the metric exists under the correct namespace:
aws cloudwatch list-metrics --namespace "Service" --region us-east-1  

If the metric doesn’t appear in the output, you may need to verify that the service or third-party source is pushing the metrics correctly to CloudWatch.


4. Metric Publishing Intervals and Gaps

CloudWatch requires metrics to be published at fixed intervals (e.g., 1 minute or 5 minutes):

  • Check that PMET metrics are being published consistently. Gaps in publishing (visible in Igraph) may cause CloudWatch to miss them.

5. Cross-Account or Marketplace Issues

If the PMET metrics are visible in another marketplace but not in your CloudWatch Dashboard:

  • Confirm permissions and configurations for cross-account metric sharing.
  • Verify that the marketplace service (aws-cookie-monster-dev) is correctly pushing metrics to your account.

Summary

From your screenshots and description, the issue likely stems from IAM permissions, inconsistencies in metric publishing, or mismatches in query parameters. Start by ensuring the IAM role or user querying CloudWatch has the right permissions (cloudwatch:GetMetricData and cloudwatch:ListMetrics). Then confirm visibility with the AWS CLI and validate all query configurations.

If the metrics still don’t appear, consider checking for cross-account access issues or marketplace-specific configurations.

Let me know if you’d like further steps or help troubleshooting permissions! 🚀

Cheers! Aaron 🎯

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.