WikiSysop at 08:30, June 23, 2023

2023-06-23T08:30:53Z

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

2023-06-23T08:00:54Z

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

New page

{{ComponentRN
|ComponentId=e17cb0c3-b6d6-41c2-8dfc-40ee83f99d56
|JQL=labels=GCXIRN10000330000
|DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
|ReleaseDate=2023-06-16
|Highlight=New helm chart parameters.

New MicroStrategy version.

Updated VitaraCharts version.

Resolved issues.
}}
{{Issue
|TicketNumber=GCXI-6826
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Vitara Charts component updated to version 5.1.3.032.See Vitara change log for updates.[https://docs.vitaracharts.com/changeLog/revisionHistory.html
|LocalContent=The VitaraCharts component is updated to version 5.1.3.032. See the VitaraCharts [https://docs.vitaracharts.com/changeLog/revisionHistory.html change log] for more information on the new version.
}}
{{Issue
|TicketNumber=GCXI-6822
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Fixed minor error when filling service gcxi_events tanle in meta db.
|LocalContent=A minor issue that resulted in the '''gcxi_events''' table in the meta database not being updated after an upgrade is addressed.
}}
{{Issue
|TicketNumber=GCXI-6821
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=When reading dashboards formatting properties, our generator raised errors if values of those properties did not correspond to their types. We turned the error to warning, such discrepancy is not fatal.
|LocalContent=When reading the formatting properties of dashboards, the GCXI generator raised errors if values of those properties did not correspond to their types. These errors are now flagged as warnings, as these discrepancies are not fatal.
}}
{{Issue
|TicketNumber=GCXI-6814
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=# DB Instance patching: our updater will NOT patch DB Instances with embedded DB Connections. GCXI never had and does not has such DB Instances.# A more sophisticated shortcut processing helping to avoid errors.# A faster creation/update of FFSQL reports.# If our updater creates a shortcut with name different then the name of its target object, and if the destination folder already contains a shortcut with the same name, and if the target object of the existing shortcut is not the target object of the new one, then we rename the existing shortcut so that its name is equal to the name of its target object. If we do not do it, there will be “The … folder already has object with name .. and type 18…” error.
|LocalContent=The GCXI updater does NOT patch DB Instances with embedded DB Connections, and it never has.

A more sophisticated shortcut processing is introduced to help to avoid errors.

*GCXI offers faster creation and updating of FFSQL reports.
*If the updater creates a shortcut with a name that is different from its target object's name, and if the destination folder already contains a shortcut with the same name, and if the target object of the existing shortcut is not the target object of the new one, then the existing shortcut is renamed so that its name is the same as its target object's name.
*If the renaming does not occur, an error message is displayed.
}}
{{Issue
|TicketNumber=GCXI-6808
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=New container environment variable introduced:*METRICS_NO_TS* (default: empty string)In some environments a problem with GCXI TCP metrics endpoint may occur.Normally, GCXI supplies metrics in Prometheus format with timestamps.But sometime Prometheus may fail to process them correctly, resulting in gaps in GCXI metrics timeseries.If you observe such behavior, run container with:METRICS_NO_TS=trueIt will make GCXI container to give out metrics without timestamps.In this case Prometheus is supposed to take care abount timestamps on its own.
|LocalContent=A new container environment variable, '''METRICS_NO_TS''', is introduced. Its default value is an empty string. In some environments, a problem with the GCXI TCP metrics endpoint may occur. Normally, GCXI supplies metrics in the Prometheus format with timestamps. But at times, Prometheus may fail to process them correctly, resulting in gaps in the GCXI metrics time series. If you observe such behavior, run the GCXI container with '''METRICS_NO_TS''' set to <code>true</code>. This will enable the GCXI container to provided metrics without timestamps. In this case, Prometheus is supposed to handle the timestamps on its own.
}}
{{Issue
|TicketNumber=GCXI-6790
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=When installing GCXI, we replace one of Microstrategy JAR files, namely “foundry-sql-jdbc-driver.jar”, with its patched copy. The copy has “Multi-Release: true” line in its “META-INF/MANIFEST.MF” entry. Without this change our JDBC driver produces no log4j logs because Microstrategy JVM fails to property initialize the log4j. The patch fixes the problem.
|LocalContent=One of the Microstrategy JAR files, '''foundry-sql-jdbc-driver.jar''', is now replaced with its patched copy. The updated file has the '''Multi-Release''' option set to <code>true</code> in its '''META-INF/MANIFEST.MF''' entry. Without this change the GXCI JDBC driver produces no log4j logs because the Microstrategy JVM fails to properly initialize log4j.
}}
{{Issue
|TicketNumber=GCXI-6786
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Bugfix: when applying access restriction, our JDBC driver failed to work with metabases where Microstrategy tables were in a non-default schema. It’s fixed. The ODBC system data source described above have “InitializationString” properties set to something like “SET SEARCH_PATH TO …”. It’s a statement which the ODBC driver runs immediately establishing the connection. Now our JDBC driver, when connecting that DB, reads “InitializationString” property and, if the property is set, runs the statement as well.
|LocalContent=When applying access restriction, the GCXI JDBC driver failed to work with metabases where MicroStrategy tables were in a non-default schema. This issue is now fixed. The ODBC system data source has an <code>InitializationString</code> property that is set to a statement that the the ODBC driver runs immediately after the connection is established. Now the GCXI JDBC driver, when connecting to that DB, reads the <code>InitializationString</code> property and, if the property is set, runs the corresponding statement as well.
}}
{{Issue
|TicketNumber=GCXI-6776
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Decreased number of exported metrics on the metrics enpoint (“/gcxi/monitor/metrics“).Some metrics were unneeded or excessive, which cluttered the output and increased metrics processing costs.
|LocalContent=The number of exported metrics on the '''/gcxi/monitor/metrics''' metrics endpoint is now decreased. Some metrics were unneeded or excessive, thereby cluttering the output and increasing metrics processing costs.
}}
{{Issue
|TicketNumber=GCXI-6775
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Update frequency for GCXI service metrics (produced by “/gcxi/monitor/metrics“ endpoint) was increased: each ~6 minutes => each ~3 minutes
|LocalContent=The update frequency for GCXI service metrics, produced by the '''/gcxi/monitor/metrics''' endpoint, is increased to 3 minutes from 6 minutes.
}}
{{Issue
|TicketNumber=GCXI-6746
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=GCXI uses Netcat to run metrics TCP endpoint inside the container.Some customers don’t want to have netcat running because of compliance concerns.Added container variable:{{NC_RUN_SERVER=true
|LocalContent=GCXI uses Netcat (NC) to run the TCP metrics endpoint inside the container. A new container variable, '''NC_RUN_SERVER''', is introduced to control this behaviour. If you do not want NC to run in the background, set '''NC_RUN_SERVER''' to ''false''. However, note that this will also disable the TCP metrics endpoint.
}}
{{Issue
|TicketNumber=GCXI-6744
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Default value for JDBC statement timeout for Postgres has been set too low in v032.It has been increased from 180000 (3 min) => 1800000 (30 min) in v033.If you want to set a custom timeout, use JDBC_OPTS clause of DSNDEF* variables.The syntax would be as follows:{{DSNDEF1=DSN_NAME=GCXI_GIM_DB;DRV_TYPE=JDBC;JDBC_OPTS=options=-cstatement_timeout=1740000;GCXI_QENGINE=ON...}}Note, that you can set multiple JDBC parameters thru JDBC_OPTS clause of DSNDEF.Syntax: individual parameters should be separated by pipe, while options inside ‘option’ field should be separated by url-encoded space aka %20.For example, here we set the following parameters:{{DSNDEF1=DSN_NAME=GCXI_GIM_DB;DRV_TYPE=JDBC;JDBC_OPTS=sslmode=require
|LocalContent=The default value for the JDBC statement timeout option for PostgreSQL was set too low in v032. This is now increased from ''180000 (3 min)'' to ''1800000 (30 min)'' in v033.

If you want to set a custom timeout, use the <code>JDBC_OPTS</code> clause of the <code>DSNDEF*</code> variables. The syntax is as follows:
DSNDEF1=DSN_NAME=GCXI_GIM_DB;DRV_TYPE=JDBC;JDBC_OPTS=options=-cstatement_timeout=1740000;GCXI_QENGINE=ON...
Note: You can also set multiple JDBC parameters thru the JDBC_OPTS clause of the DSNDEF* variables. Individual parameters must be separated by a pipe, while options inside the option field must be separated by the url-encoded space, '''%20'''.
For example:
DSNDEF1=DSN_NAME=GCXI_GIM_DB;DRV_TYPE=JDBC;JDBC_OPTS=sslmode=require&vert;options=-cstatement_timeout=1740000%20-csearch_path=custom;GCXI_QENGINE=ON...

sslmode=false
options=
-cstatemnt_timeout=1740000
-csearch_path=custom
For more information, refer to the [https://jdbc.postgresql.org/documentation/use/#connection-parameters PostgreSQL documentation for JDBC parameter reference].
}}
{{Issue
|TicketNumber=GCXI-6695
|IssueCategoryId=5c483167-c133-4dc5-87c0-bd2719670bc1
|Content=Kubernetes descriptor example for ingress-nginx daemonset was updated to v1.7.0.Check the {{file nginx-daemon.yaml}} in k8s descriptors.
|LocalContent=The Kubernetes descriptor example for the <code>ingress-nginx</code> daemonset is updated to v1.7.0. You can verify the k8s descriptors in the '''nginx-daemon.yaml''' file.
}}
{{Issue
|TicketNumber=GCXI-6694
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=GCXI is based on the latest Microstrategy version 11.3.0960.0061.
|LocalContent=MicroStrategy version is upgraded to [https://www2.microstrategy.com/producthelp/Current/Readme/en-us/Content/whats_new.htm#update10_june2023 11.3.1060.00468].
}}
{{Issue
|TicketNumber=GCXI-6678
|IssueCategoryId=720446c8-10b6-42b8-af36-34a298aa1c72
|Content=Updated Postgres client tools to v13 in GCXI images.Now GCXI supports both Postgres 12 and 13 as meta db RDBMS.
|LocalContent=PostgreSQL client tools have been upgraded to version 13 in the GCXI images. Now, GCXI supports meta databases in both PostgreSQL versions, 12 and 13.
}}

@@ Line 3: / Line 3: @@
 |JQL=labels=GCXIRN10000330000
 |DeploymentTypeId=ec194bf2-b79a-436d-8ff6-eaff94d9f43a, 5439f1be-1868-4091-b058-1667389b6ce1, 8b480b3c-2733-433a-9166-eab2c2d0663a
-|ReleaseDate=2023-06-16
+|ReleaseDate=2023-06-23
 |Highlight=New helm chart parameters.

RN/GenesysCX Insights/100.0.033.0000 - Revision history

WikiSysop at 08:30, June 23, 2023

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