Use the CData ODBC Driver for Sentry in MicroStrategy Web

MicroStrategy is an analytics and mobility platform that enables data-driven innovation. When you pair MicroStrategy with the CData ODBC Driver for Sentry, you gain database-like access to live Sentry data from MicroStrategy, expanding your reporting and analytics capabilities. In this article, we walk through adding Sentry as external data in MicroStrategy Web and creating a simple visualization of Sentry data.

The CData ODBC driver offers unmatched performance for interacting with live Sentry data in MicroStrategy due to optimized data processing built into the driver. When you issue complex SQL queries from MicroStrategy to Sentry, the driver pushes supported SQL operations, like filters and aggregations, directly to Sentry and utilizes the embedded SQL engine to process unsupported operations (often SQL functions and JOIN operations) client-side. With built-in dynamic metadata querying, you can visualize and analyze Sentry data using native MicroStrategy data types.

Connect to Sentry as an ODBC Data Source

Information for connecting to Sentry follows, along with different instructions for configuring a DSN in Windows and Linux environments (the ODBC Driver for Sentry must be installed on the machine hosting the connected MicroStrategy Intelligence Server).

Using API Key Authentication

Sentry uses token-based authentication. To obtain an Auth Token:

1. Log in to your Sentry account at https://sentry.io
2. Navigate to Settings > Auth Tokens
3. Click "Create New Token"
4. Select the required scopes and click "Create Token"
5. Copy the generated token (it will only be shown once)

After obtaining your Auth Token, set the following connection properties:

• AuthScheme: Set this to APIKey.

Set the following in the ProfileSettings connection property:

• APIKey: Set this to your Sentry Auth Token.
• OrganizationId: Set this to your Sentry organization slug or ID.

Example Connection String

Profile=C:\profiles\Sentry.apip;AuthScheme=APIKey;ProfileSettings="APIKey=your_auth_token;OrganizationId=your_org_slug";

Connecting to Sentry

Once the authentication is configured, you can connect to Sentry and query data from any of the available tables such as Organizations, Projects, Issues, and Events.

When you configure the DSN, you may also want to set the Max Rows connection property. This will limit the number of rows returned, which is especially helpful for improving performance when designing reports and visualizations.

Windows

If you have not already, first specify connection properties in an ODBC DSN (data source name). This is the last step of the driver installation. You can use the Microsoft ODBC Data Source Administrator to create and configure ODBC DSNs.

Linux

If you are installing the CData ODBC Driver for Sentry in a Linux environment, the driver installation predefines a system DSN. You can modify the DSN by editing the system data sources file (/etc/odbc.ini) and defining the required connection properties.

/etc/odbc.ini

[CData API Sys]
Driver = CData ODBC Driver for Sentry
Description = My Description
Profile = C:\profiles\Sentry.apip
AuthScheme = APIKey
ProfileSettings = "APIKey = your_auth_token
OrganizationId = your_org_slug"

For specific information on using these configuration files, please refer to the help documentation (installed and found online).

Connect to and Visualize Sentry Data using MicroStrategy Web

Once you have created a database instance in MicroStrategy Developer and connected it to a project, you can perform a data import of Sentry data from MicroStrategy Web. Alternatively, you can create a new data source based on the ODBC Driver.^*

1. Open MicroStrategy Web and select your project.
2. Click Add External Data, select Databases, and choose Select a Table as the Import Option.
3. In the Import from Tables wizard, click to add a new data source.
   • Select DSN Data Sources
   • Set the DSN property to the previously configured DSN (CData API Sys)
   • Set the Version property to Generic DBMS
   • Set the User and Password properties (or use filler values)
   • Set the Data Source Name
   👁 Configuring the new Data Source
   
4. After creating the data source, click to edit the catalog options and set the following queries and click OK.
   • SQL statement to retrieve tables available in the data source

     SELECT
      CatalogName NAME_SPACE,
      TableName TAB_NAME
     FROM
      SYS_TABLES
      

   • SQL statement to retrieve columns for the selected tables

     SELECT DISTINCT 
      CatalogName NAME_SPACE, 
      TableName TAB_NAME, 
      ColumnName COL_NAME, 
      DataTypeName DATA_TYPE, 
      Length DATA_LEN, 
      NumericPrecision DATA_PREC, 
      NumericScale DATA_SCALE 
     FROM 
      SYS_TABLECOLUMNS 
     WHERE 
      TableName IN (#TABLE_LIST#) 
     ORDER BY
      1,2,3
      

5. Drag a table into the pane. 👁 Connecting to Sentry data.
   Note: Since we create a live connection, we can import whole tables and utilize the filtering and aggregation features native to the MicroStrategy products.
6. Click Finish, choose to the option to connect live, save the query, and choose the option to create a new dossier. 👁 Save the query and create a new dossier.
   
7. Choose a visualization, choose fields to display, and apply any filters to create a new visualization of Sentry data. Data types are discovered automatically through dynamic metadata discovery. Where possible, the complex queries generated by the filters and aggregations will be pushed down to Sentry, while any unsupported operations (which can include SQL functions and JOIN operations) will be managed client-side by the CData SQL engine embedded in the driver. 👁 Visualize Sentry data.
   
8. Once you have finished configuring the dossier, click File -> Save.

Using the CData ODBC Driver for Sentry in MicroStrategy Web, you can easily create robust visualizations and reports on Sentry data. Read our other articles on connecting to Sentry in MicroStrategy and connecting to Sentry in MicroStrategy Desktop for more examples.

---

Note: connecting using a ODBC driver requires a 3- or 4-tier architecture.