Draft:RN/GenesysCX Insights/100.0.034.0000 - Revision history

WikiSysop: Redirected page to Draft:RN/GenesysCX Insights/100.0.034.0001

2023-11-16T10:01:21Z

Redirected page to Draft:RN/GenesysCX Insights/100.0.034.0001

WikiSysop at 09:00, October 13, 2023

2023-10-13T09:00:44Z

WikiSysop: Created page with "{{ComponentRN |ComponentId=e17cb0c3-b6d6-41c2-8dfc-40ee83f99d56 |JQL=labels=GCXIRN10000340000 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1..."

2023-10-13T08:30:36Z

Created page with "{{ComponentRN |ComponentId=e17cb0c3-b6d6-41c2-8dfc-40ee83f99d56 |JQL=labels=GCXIRN10000340000 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1..."

New page

{{ComponentRN
|ComponentId=e17cb0c3-b6d6-41c2-8dfc-40ee83f99d56
|JQL=labels=GCXIRN10000340000
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
|ReleaseDate=2023-10-20
|PrivateEditionReleaseDate=2023-10-20
}}
{{Issue
|TicketNumber=GCXI-7049
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Vitara Charts component updated to version 5.2.3.081.See Vitara change log for updates.[https://docs.vitaracharts.com/changeLog/revisionHistory.html
|LocalContent=Vitara Charts component updated to version 5.2.3.081.See Vitara change log for updates.[https://docs.vitaracharts.com/changeLog/revisionHistory.html
}}
{{Issue
|TicketNumber=GCXI-7036
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=GCXI updated to Microstrategy v. 11.3.11
|LocalContent=GCXI updated to Microstrategy v. 11.3.11
}}
{{Issue
|TicketNumber=GCXI-6944
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Added extra metrics to GCXI metrics endpoint, which are more convenient to be employed in PromQL formulas.Both metrics are based on gcxi__projects__status metric, and can have value either 0 or 1.Metrics are mutually exclusive, when one = 0, the other one = 1, and vice versa.* gcxi__projects__status_failvalues: 1 = when gcxi__projects__status != 0 (i. e. gcxi is not healthy), 0 otherwise* gcxi__projects__status_okvalues: 1 = when gcxi__projects__status == 0 (i. e. gcxi is ok), 0 otherwise
|LocalContent=Added extra metrics to GCXI metrics endpoint, which are more convenient to be employed in PromQL formulas.Both metrics are based on gcxi__projects__status metric, and can have value either 0 or 1.Metrics are mutually exclusive, when one = 0, the other one = 1, and vice versa.* gcxi__projects__status_failvalues: 1 = when gcxi__projects__status != 0 (i. e. gcxi is not healthy), 0 otherwise* gcxi__projects__status_okvalues: 1 = when gcxi__projects__status == 0 (i. e. gcxi is ok), 0 otherwise
}}
{{Issue
|TicketNumber=GCXI-6921
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=The "gcxi_gauth_redirect" metric was counted incorrectly (excessive increments), now it’s fixed.
|LocalContent=The "gcxi_gauth_redirect" metric was counted incorrectly (excessive increments), now it’s fixed.
}}
{{Issue
|TicketNumber=GCXI-6910
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Added name of the rapped signal to graceful_exit() function output in the container log. Now it shows what exactly exit signal was sent to the container.
|LocalContent=Added name of the rapped signal to graceful_exit() function output in the container log. Now it shows what exactly exit signal was sent to the container.
}}
{{Issue
|TicketNumber=GCXI-6904
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Sometimes value for _gcxi_cluster_info_ metric was counted incorrectly (this value represents current number of nodes in MSTR cluster).Fixed node count calculation.
|LocalContent=Sometimes value for _gcxi_cluster_info_ metric was counted incorrectly (this value represents current number of nodes in MSTR cluster).Fixed node count calculation.
}}
{{Issue
|TicketNumber=GCXI-6924, GCXI-7011
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=Multiple improvements and bug fixes have been implemented in the SSO auth module.
}}
{{Issue
|TicketNumber=GCXI-6854, GCXI-6915, GCXI-6917, GCXI-6927, GCXI-6928, GCXI-6929, GCXI-6930, GCXI-6931, GCXI-6932, GCXI-6933, GCXI-6935, GCXI-6937, GCXI-6940, GCXI-6942, GCXI-6943, GCXI-6982, GCXI-7037
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|LocalContent=Multiple improvements and bug fixes have been implemented in relation to the processing of Microstrategy objects.
}}

← Older revision		Revision as of 10:01, November 16, 2023
Line 1:		Line 1:
−	~~{{ComponentRN~~	+	#REDIRECT [[Draft:RN/GenesysCX Insights/100.0.034.0001]]
−	~~\|ComponentId=e17cb0c3-b6d6-41c2-8dfc-40ee83f99d56~~
−	~~\|JQL=labels=GCXIRN10000340000~~
−	~~\|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a~~
−	~~\|ReleaseDate=2023-10-20~~
−	~~\|PrivateEditionReleaseDate=2023-10-20~~
−	~~\|Highlight=New MicroStrategy version.~~
−
−	~~Updated VitaraCharts version.~~
−
−	~~Resolved issues.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-7049~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	~~\|Content=Vitara Charts component updated to version 5.2.3.081.See Vitara change log for updates.~~[~~https://docs.vitaracharts.com/changeLog/revisionHistory.html~~
−	~~\|LocalContent=The VitaraCharts component is updated to version 5.2.3.081. See the VitaraCharts~~ [~~https~~://~~docs~~.~~vitaracharts~~.~~com/changeLog/revisionHistory~~.~~html change log~~] ~~for more information on the new version.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-7036~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	~~\|Content=GCXI updated to Microstrategy v. 11.3.11~~
−	~~\|LocalContent=MicroStrategy version is upgraded to [https://www2.microstrategy.com/producthelp/Current/Readme/en-us/Content/whats_new.htm#update11_september2023 11.3.11~~].
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-6944~~
−	~~\|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72~~
−	\|Content=Added extra metrics to GCXI metrics endpoint, which are more convenient to be employed in PromQL formulas.Both metrics are based on gcxi__projects__status metric, and can have value either 0 or 1.Metrics are mutually exclusive, when one = 0, the other one = 1, and vice versa.* gcxi__projects__status_failvalues: 1 = when gcxi__projects__status != 0 (i. e. gcxi is not healthy), 0 otherwise* gcxi__projects__status_okvalues: 1 = when gcxi__projects__status == 0 (i. e. gcxi is ok), 0 otherwise
−	\|LocalContent=Two new metrics have been included to the GCXI metrics endpoint. The new metrics are more convenient to be employed in PromQL formulas. Both the metrics are based on the <code>gcxi__projects__status</code> metric, and can have a value of either ''0'' or ''1''. The metrics are mutually exclusive, when one metric = ''0'', the other metric = ''1'', and vice versa.
−
−	*<code>gcxi__projects__status_fail</code> (values: ''1,'' when <code>gcxi__projects__status != 0</code> (that is, GCXI is not healthy), else ''0).''
−	*<code>gcxi__projects__status_ok</code> (values: ''1,'' when <code>gcxi__projects__status == 0</code> (that is, GCXI is OK), else ''0).''
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-6921~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|Content=The "gcxi_gauth_redirect" metric was counted incorrectly (excessive increments), now it’s fixed.~~
−	~~\|LocalContent=The <code>gcxi_gauth_redirect</code> metric was counted incorrectly (excessive increments) and is now fixed.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-6910~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|Content=Added name of the rapped signal to graceful_exit() function output in the container log. Now it shows what exactly exit signal was sent to the container.~~
−	~~\|LocalContent=The name of the rapped signal has been added to the <code>graceful_exit()</code> function output in the container log. Now, it shows the exact exit signal that was sent to the container.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-6904~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|Content=Sometimes value for _gcxi_cluster_info_ metric was counted incorrectly (this value represents current number of nodes in MSTR cluster).Fixed node count calculation.~~
−	\|LocalContent=At times, the value for the <code>_gcxi_cluster_info_</code> metric was counted incorrectly (this value represents the current number of nodes in the MSTR cluster). The incorrect node count calculation is now fixed.
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-6924, GCXI-7011~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=Multiple improvements and bug fixes have been implemented in the SSO auth module.~~
−	}}
−	~~{{Issue~~
−	~~\|TicketNumber=GCXI-6854, GCXI-6915, GCXI-6917, GCXI-6927, GCXI-6928, GCXI-6929, GCXI-6930, GCXI-6931, GCXI-6932, GCXI-6933, GCXI-6935, GCXI-6937, GCXI-6940, GCXI-6942, GCXI-6943, GCXI-6982, GCXI-7037~~
−	~~\|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1~~
−	~~\|LocalContent=Multiple improvements and bug fixes have been implemented in relation to the processing of MicroStrategy objects.~~
−	}}

@@ Line 5: / Line 5: @@
 |ReleaseDate=2023-10-20
 |PrivateEditionReleaseDate=2023-10-20
 }}
 {{Issue
@@ Line 10: / Line 15: @@
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 |Content=Vitara Charts component updated to version 5.2.3.081.See Vitara change log for updates.[https://docs.vitaracharts.com/changeLog/revisionHistory.html
-|LocalContent=Vitara Charts component updated to version 5.2.3.081.See Vitara change log for updates.[https://docs.vitaracharts.com/changeLog/revisionHistory.html
+|LocalContent=The VitaraCharts component is updated to version 5.2.3.081. See the VitaraCharts [https://docs.vitaracharts.com/changeLog/revisionHistory.html change log] for more information on the new version.
 }}
 {{Issue
@@ Line 16: / Line 21: @@
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 |Content=GCXI updated to Microstrategy v. 11.3.11
-|LocalContent=GCXI updated to Microstrategy v. 11.3.11
+|LocalContent=MicroStrategy version is upgraded to [https://www2.microstrategy.com/producthelp/Current/Readme/en-us/Content/whats_new.htm#update11_september2023 11.3.11].
 }}
 {{Issue
@@ Line 22: / Line 27: @@
 |IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
 |Content=Added extra metrics to GCXI metrics endpoint, which are more convenient to be employed in PromQL formulas.Both metrics are based on gcxi__projects__status metric, and can have value either 0 or 1.Metrics are mutually exclusive, when one = 0, the other one = 1, and vice versa.* gcxi__projects__status_failvalues: 1 = when gcxi__projects__status != 0 (i. e. gcxi is not healthy), 0 otherwise* gcxi__projects__status_okvalues: 1 = when gcxi__projects__status == 0 (i. e. gcxi is ok), 0 otherwise
-|LocalContent=Added extra metrics to GCXI metrics endpoint, which are more convenient to be employed in PromQL formulas.Both metrics are based on gcxi__projects__status metric, and can have value either 0 or 1.Metrics are mutually exclusive, when one = 0, the other one = 1, and vice versa.* gcxi__projects__status_failvalues: 1 = when gcxi__projects__status != 0 (i. e. gcxi is not healthy), 0 otherwise* gcxi__projects__status_okvalues: 1 = when gcxi__projects__status == 0 (i. e. gcxi is ok), 0 otherwise
+|LocalContent=Two new metrics have been included to the GCXI metrics endpoint. The new metrics are more convenient to be employed in PromQL formulas. Both the metrics are based on the <code>gcxi__projects__status</code> metric, and can have a value of either ''0'' or ''1''. The metrics are mutually exclusive, when one metric = ''0'', the other metric = ''1'', and vice versa.
 }}
 {{Issue
@@ Line 28: / Line 36: @@
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 |Content=The "gcxi_gauth_redirect" metric was counted incorrectly (excessive increments), now it’s fixed.
-|LocalContent=The "gcxi_gauth_redirect" metric was counted incorrectly (excessive increments), now it’s fixed.
+|LocalContent=The <code>gcxi_gauth_redirect</code> metric was counted incorrectly (excessive increments) and is now fixed.
 }}
 {{Issue
@@ Line 34: / Line 42: @@
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 |Content=Added name of the rapped signal to graceful_exit() function output in the container log. Now it shows what exactly exit signal was sent to the container.
-|LocalContent=Added name of the rapped signal to graceful_exit() function output in the container log. Now it shows what exactly exit signal was sent to the container.
+|LocalContent=The name of the rapped signal has been added to the <code>graceful_exit()</code> function output in the container log. Now, it shows the exact exit signal that was sent to the container.
 }}
 {{Issue
@@ Line 40: / Line 48: @@
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
 |Content=Sometimes value for _gcxi_cluster_info_ metric was counted incorrectly (this value represents current number of nodes in MSTR cluster).Fixed node count calculation.
-|LocalContent=Sometimes value for _gcxi_cluster_info_ metric was counted incorrectly (this value represents current number of nodes in MSTR cluster).Fixed node count calculation.
+|LocalContent=At times, the value for the <code>_gcxi_cluster_info_</code> metric was counted incorrectly (this value represents the current number of nodes in the MSTR cluster). The incorrect node count calculation is now fixed.
 }}
 {{Issue
@@ Line 50: / Line 58: @@
 |TicketNumber=GCXI-6854, GCXI-6915, GCXI-6917, GCXI-6927, GCXI-6928, GCXI-6929, GCXI-6930, GCXI-6931, GCXI-6932, GCXI-6933, GCXI-6935, GCXI-6937, GCXI-6940, GCXI-6942, GCXI-6943, GCXI-6982, GCXI-7037
 |IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
-|LocalContent=Multiple improvements and bug fixes have been implemented in relation to the processing of Microstrategy objects.
+|LocalContent=Multiple improvements and bug fixes have been implemented in relation to the processing of MicroStrategy objects.
 }}