Skip to content

Commit 20ff35d

Browse files
authored
Merge pull request #38027 from apinnick/fix-mtc-troubleshooting
Fixing problems with performance metrics
2 parents 7568577 + 3e69dbc commit 20ff35d

File tree

5 files changed

+30
-28
lines changed

5 files changed

+30
-28
lines changed

migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,9 @@ This section describes logs and debugging tools that you can use for troubleshoo
2222
include::modules/migration-viewing-migration-plan-resources.adoc[leveloffset=+2]
2323
include::modules/migration-viewing-migration-plan-log.adoc[leveloffset=+2]
2424
include::modules/migration-using-mig-log-reader.adoc[leveloffset=+2]
25-
include::modules/migration-performance-metrics.adoc[leveloffset=+2]
26-
include::modules/migration-accessing-performance-metrics-in-ocp-web-console.adoc[leveloffset=+2]
25+
include::modules/migration-accessing-performance-metrics.adoc[leveloffset=+2]
26+
[discrete]
27+
include::modules/migration-provided-metrics.adoc[leveloffset=+3]
2728
include::modules/migration-using-must-gather.adoc[leveloffset=+2]
2829
include::modules/migration-debugging-velero-resources.adoc[leveloffset=+2]
2930
include::modules/migration-partial-failure-velero.adoc[leveloffset=+2]

migration_toolkit_for_containers/troubleshooting-mtc.adoc

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,9 @@ This section describes logs and debugging tools that you can use for troubleshoo
2222
include::modules/migration-viewing-migration-plan-resources.adoc[leveloffset=+2]
2323
include::modules/migration-viewing-migration-plan-log.adoc[leveloffset=+2]
2424
include::modules/migration-using-mig-log-reader.adoc[leveloffset=+2]
25-
include::modules/migration-performance-metrics.adoc[leveloffset=+2]
25+
include::modules/migration-accessing-performance-metrics.adoc[leveloffset=+2]
26+
[discrete]
27+
include::modules/migration-provided-metrics.adoc[leveloffset=+3]
2628
include::modules/migration-using-must-gather.adoc[leveloffset=+2]
2729
include::modules/migration-debugging-velero-resources.adoc[leveloffset=+2]
2830
include::modules/migration-partial-failure-velero.adoc[leveloffset=+2]

modules/migration-accessing-performance-metrics-in-ocp-web-console.adoc

Lines changed: 0 additions & 16 deletions
This file was deleted.
Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,18 @@
1+
// Module included in the following assemblies:
2+
//
3+
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
4+
// * migration-toolkit-for-containers/troubleshooting-mtc.adoc
5+
6+
[id="migration-accessing-performance-metrics_{context}"]
7+
= Accessing performance metrics
8+
9+
The `MigrationController` custom resource (CR) records metrics and pulls them into on-cluster monitoring storage. You can query the metrics by using Prometheus Query Language (PromQL) to diagnose migration performance issues. All metrics are reset when the Migration Controller pod restarts.
10+
11+
You can access the performance metrics and run queries by using the {product-title} web console.
12+
13+
.Procedure
14+
15+
. In the {product-title} web console, click *Monitoring* -> *Metrics*.
16+
. Enter a PromQL query, select a time window to display, and click *Run Queries*.
17+
+
18+
If your web browser does not display all the results, use the Prometheus console.

modules/migration-performance-metrics.adoc renamed to modules/migration-provided-metrics.adoc

Lines changed: 6 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -3,16 +3,13 @@
33
// * migrating_from_ocp_3_to_4/troubleshooting-3-4.adoc
44
// * migration-toolkit-for-containers/troubleshooting-mtc.adoc
55

6-
[id="migration-performance-metrics_{context}"]
7-
= Performance metrics
6+
[id="migration-provided-metrics_{context}"]
7+
= Provided metrics
88

9-
The `MigrationController` custom resource (CR) records a set of metrics and pulls it into on-cluster monitoring storage. You can query the metrics by using Prometheus Query Language (PromQL) to diagnose migration performance issues. All metrics are reset when the Migration Controller pod restarts.
10-
11-
[id="provided-metrics_{context}"]
12-
== Provided metrics
9+
The `MigrationController` custom resource (CR) provides metrics for the `MigMigration` CR count and for its API requests.
1310

1411
[id="cam_app_workload_migrations-metric_{context}"]
15-
=== cam_app_workload_migrations
12+
== cam_app_workload_migrations
1613

1714
This metric is a count of `MigMigration` CRs over time. It is useful for viewing alongside the `mtc_client_request_count` and `mtc_client_request_elapsed` metrics to collate API request information with migration status changes. This metric is included in Telemetry.
1815

@@ -31,7 +28,7 @@ This metric is a count of `MigMigration` CRs over time. It is useful for viewing
3128
|===
3229

3330
[id="mtc_client_request_count-metric_{context}"]
34-
=== mtc_client_request_count
31+
== mtc_client_request_count
3532

3633
This metric is a cumulative count of Kubernetes API requests that `MigrationController` issued. It is not included in Telemetry.
3734

@@ -58,7 +55,7 @@ This metric is a cumulative count of Kubernetes API requests that `MigrationCont
5855
|===
5956

6057
[id="mtc_client_request_elapsed-metric_{context}"]
61-
=== mtc_client_request_elapsed
58+
== mtc_client_request_elapsed
6259

6360
This metric is a cumulative latency, in milliseconds, of Kubernetes API requests that `MigrationController` issued. It is not included in Telemetry.
6461

0 commit comments

Comments
 (0)