Q&A by Topic

This article contains sections dealing with the following issues:

Security

Integration

SECURITY

Database Security

Challenge

When connecting a data source UI collector to a database, table and schema names are listed according to user credentials.
Sometimes names are shown which should not be revealed outside of the organization.

Solution
  1. Create a new DB.
  2. Replicate only the relevant and permitted tables /views /schemas to the new DB.
  3. Use Anodot's DB collector and connect to the newly created database.

INTEGRATION

Managing Multiple Data Sources in a Single Location

Challenge Managing several data sources in one location. This requires the use of a single collector.
Solutions

Either export the data to an S3 bucket. Use the AWS-S3 collector;
Or Export the data to a database and use a database collector from the available DB collectors.

Coding a Collector with REST API

Challenge Customer data sources that are not supported in Anodot UI must be coded using Anodot's REST API.
Solutions

Alternatively:

Either export the data to an S3 bucket. Use the AWS-S3 collector;
Or Export the data to a database and use a database collector from the available DB collectors.

 Handling Long Property Values 

Challenge How to handle keys with long property values.
Solutions

Property values longer than 150 chars are automatically truncated to enable streaming.

Was this article helpful?
0 out of 0 found this helpful
-->