Kyndryl Bridge

Experience Kyndryl Bridge

Common Metrics
Published On Jun 14, 2024 - 10:57 AM

Common Metrics

The Common Metrics allow you to view your metrics information across all Kyndryl Bridge Applications.
As an administrator, you have the independence to monitor a consolidated view of all successful and failed metrics ingested and troubleshoot errors in metrics information. To access the Common Metrics page, follow these steps:
  1. Navigate to the Services Switcher.
  2. Select
    Common Metrics
    . The Common Metrics page opens.
  3. Select the
    Metrics
    tab.
To understand which roles and permissions are required to access this service, see roles and permissions.

Understanding Common Metrics results

The Common Metrics page displays two figures/charts with the following information:
  • Metrics streaming errors: The number of errors while fetching metrics broken down by module. This dashboard displays a stacked bar chart that lets you know the specific modules that received errors.
  • Metrics checked during streaming: The number of metrics events that were checked to be streamed broken down by module. This dashboard displays a stacked bar chart that lets you know the total number of modules being fetched.

Viewing Metrics results

A module is a supported service whose metrics are being collected by Metricbeat as part of the out-of-the-box metric reports. For example: AWS, GCP, Docker, Kubernetes, Prometheus, etc. are all considered modules. At the same time, a module can contain one or multiple metricsets. For example: Billing, ec3, container, cpu, load balancing, query, etc. are all considered metricsets.
List table
The Metrics page also displays a more in-depth list table with the following information:
  • Provider: The modules being tracked by Metricbeat.
  • Last Run: The date, time, and duration for the last fetching process. It also includes the scheduled date and time of the next run.
  • Status: The status for the last metricset process. If the item discovered had failed due to invalid credentials or network issues, the reload button is displayed to allow the re-ingestion. Make sure to have admin/operator role permissions.
  • Discovery Summary: The number of errors found, and the number of metrics checked.
At the same time, you can click the arrow down icon to see more details as follows:
  • Credential: A connection name that allows you to access the module.
  • Metrics sets: The subpart contained within the module being tracked.
  • Registration ID: The ID number created for the corresponding connection previously onboarded.
  • Last Run: The date and time when the last fetching process for this credential was run, as well as how long the process took and when the next discovery will be run.
  • Status: The status for the last metricset process.
  • Summary: The number of errors found, and the number of metrics checked.

Viewing details

If you want to go further down metrics details, click the overflow menu next to a credential, and select
View details
to view more in-depth details for that credential. The details page displays the following information:
Summary
The Summary section provides basic details of the selected metricset and associated credentials.
  • Last Run: The date and time when the last fetching process for this credential was run.
  • Duration: The amount of time that the metrics discovery process took to complete.
  • Status: The status for the last metric set process.
  • Provider: The module associated with the credential.
  • Registration ID: The ID number that is associated to the respective connection previously onboarded.
  • Credential: The connection name of the connection created.

Errors

The Errors section provides the following information about each error encountered. You can click
Download
in the upper right side of the section to download this information in JSON format.
  • Type: The type of error.
  • Time: The date and time when the error occurred.
  • Description: Further information to help you diagnose the cause of the error.

Previous runs

The Previous Runs section provides a history of the previous metrics discovery processes for the corresponding metricset, and credential associated with the Registration ID, including the following information. You can click
Download
in the upper right side of the section to download this information in JSON format.
  • Registration ID: The ID number that is associated to the respective connection previously onboarded.
  • Run Time: The date and time when the discovery process occurred.
  • Duration: The amount of time that the metrics discovery process took to complete.
  • Status: The status for the metrics discovery process.
  • Summary: The number of metrics events checked.

Understanding status

The following are the different status explanations for the metrics discovery process:
  • In progress: The metrics discovery process is currently running.
  • Failed: The metrics fetch process failed. The number of metrics events that were successfully checked is listed.
  • Completed with errors: The metrics discovery for the metricset process was partially successful. The number of metrics events that were successfully ingested is listed.
  • Complete: The metrics discovery process completed without errors.
Do you have two minutes for a quick survey?
Take Survey