How can we help?

Dashboard

Anthony - Versasec Support
Anthony - Versasec Support
  • Updated

From version 5.1 of the vSEC:CMS it is possible to configure a dashboard view which can then be viewed from the Home screen of the administration console. In this article we will describe how to configure 4 common dashboard views. If additional views are required to be configured please contact Versasec at support@versasec.com

Important
It is required that MS SQL is used for the database in order to use this functionally. Additionally, the database schema needs to be at the correct number of 12. You can check this from the administration console and from Help – Diagnostic check under vSEC:CMS: Service for the entries: DB schema application, DB schema plugin and DB schema SQL and make sure these all have a value of 12. If the schema is not at this value then from System Status click the yellow circle in the bottom right of the administration console and you will see an entry about Database schema needs to be updated. Perform the database schema update and close the administration console and restart the CMS services in order to apply the update.

Configure Dashboard Views

In this article we will provide samples on how 4 common dashboard views can be configured. The views are:

  • Cards that have been issued in last 24 hours;
  • Revocations that have been performed in last 24 hours;
  • Operational activity in last 24 hours;
  • Managed devices activity in last 24 hours.

By default, the views are not available. Therefore, it is required to run SQL queries in order to show these views. We will describe how this can be done with sample SQL queries below for each of the views.

Cards Issued in Last 24 Hours

Using an MS SQL query console run the following query:

UPDATE[Tenant0].[DashboardConfig]
SET[Order] = 1,
[Title] = N'Issued Cards in Last 24 Hours',
[Description] = N'All Issued Cards' + NCHAR(13) + NCHAR(10) + N'In Last 24 Hours',
[ExtendedViewName] = N'ExtendedCards',
[AuditDbRecordType] = N'cards',
[SelectionExpression] = N'AddOperationLessEqual true "TimeStampAssigned" false T?NOW-24H'
WHERE[InternalName] = N'dashboard1';
Important
After running the SQL query it can take up to 2 minutes before the CMS will read the changes in the database. Therefore, you may have to wait up to 2 minutes before you see the entry available in the administration console. Navigate to another page and then go back to the Home page to see that the dashboard entry is available.
Additionally, you should not run another SQL query, as described in this article, until the CMS has read in this particular database change. Again, this can take up to 2 minutes for the CMS to read in the database changes.

Additionally, you should not run another SQL query, as described in this article, until the CMS has read in this particular database change. Again, this can take up to 2 minutes for the CMS to read in the database changes.

Revocations Performed in Last 24 Hours

Using an MS SQL query console run the following query:

UPDATE[Tenant0].[DashboardConfig]
SET[Order] = 2,
[Title] = N'Revocations in Last 24 Hours',
[Description] = N'All Revocations' + NCHAR(13) + NCHAR(10) + N'In Last 24 Hours',
[ExtendedViewName] = N'ExtendedAudit',
[AuditDbRecordType] = N'actionlist',
[SelectionExpression] = N'AddOperationLessEqual true "TimeStamp" false T?NOW-24H' + NCHAR(13) + NCHAR(10) + 'AddOperationEqual false "ActionID" false U12'
WHERE[InternalName] = N'dashboard2';
Important
After running the SQL query it can take up to 2 minutes before the CMS will read the changes in the database. Therefore, you may have to wait up to 2 minutes before you see the entry available in the administration console. Navigate to another page and then go back to the Home page to see that the dashboard entry is available.
Additionally, you should not run another SQL query, as described in this article, until the CMS has read in this particular database change. Again, this can take up to 2 minutes for the CMS to read in the database changes.

Operational Activity in Last 24 Hours

Using an MS SQL query console run the following query:

UPDATE[Tenant0].[DashboardConfig]
SET[Order] = 3,
[Title] = N'Operational Activity in last 24 hours',
[Description] = N'Operational Activity' + NCHAR(13) + NCHAR(10) + N'In Last 24 Hours',
[ExtendedViewName] = N'ExtendedSyslog',
[AuditDbRecordType] = N'syslog',
[SelectionExpression] = N'AddOperationLessEqual true "TimeStamp" false T?NOW-24H'
WHERE[InternalName] = N'dashboard3';
Important
After running the SQL query it can take up to 2 minutes before the CMS will read the changes in the database. Therefore, you may have to wait up to 2 minutes before you see the entry available in the administration console. Navigate to another page and then go back to the Home page to see that the dashboard entry is available.
Additionally, you should not run another SQL query, as described in this article, until the CMS has read in this particular database change. Again, this can take up to 2 minutes for the CMS to read in the database changes.

Managed Devices Activity in Last 24 Hours

Using an MS SQL query console run the following query:

UPDATE[Tenant0].[DashboardConfig]
SET[Order] = 4,
[Title] = N'Managed Devices Activity in last 24 hours',
[Description] = N'Managed Devices Activity' + NCHAR(13) + NCHAR(10) + N'In Last 24 Hours',
[ExtendedViewName] = N'ExtendedRsdmLog',
[AuditDbRecordType] = N'rsdm_actions',
[SelectionExpression] = N'AddOperationLessEqual true "TimeStamp" false T?NOW-24H'
WHERE[InternalName] = N'dashboard4';
Important
After running the SQL query it can take up to 2 minutes before the CMS will read the changes in the database. Therefore, you may have to wait up to 2 minutes before you see the entry available in the administration console. Navigate to another page and then go back to the Home page to see that the dashboard entry is available.
Additionally, you should not run another SQL query, as described in this article, until the CMS has read in this particular database change. Again, this can take up to 2 minutes for the CMS to read in the database changes.