This section describes how to enable or disable logging of user activities and transfer of the logs to Trifacta®. When this feature is enabled, user activities are captured locally on the Trifacta node in a series of log files. Periodically, these log files are uploaded to a predefined S3 bucket, where Trifacta can ingest the logging activity to improve the product and assist in troubleshooting.
Tip: This feature is useful for providing better suggestions and machine-based learning to the Trifacta platform instance.
NOTE: During initial deployment, this service may be enabled for you. You can use the information below to disable the service.
Trifacta captures the following types of usage information, which are available in different releases.
- These can be separately enabled.
For more information on the data that is captured, see https://community.trifacta.com/s/article/Trifacta-Usage-Data-Collection-1515802070895.
Trifacta proprietary capture of information about the Trifacta platform
|Segment Analytics||Analytics for various common data segments, such as Google and Marketo.|
The following configuration steps must be completed:
- Customer must file a request with Trifacta Support when this service is to be enabled for the first time.
- Services must be enabled on the Trifacta node.
Open user logging port, if not already opened.
- Generate and publish credentials.
- Define cron job to upload logs.
To enable this service, customers must file a support ticket with Trifacta Support. In your request, please include a request for the appropriate API write key values to insert in the configuration. Details are below.
Configure for Platform Analytics
The platform's custom-built telemetry system is controlled by the following config field in You can apply this change through the Admin Settings Page (recommended) or
trifacta-conf.json. For more information, see Platform Configuration Methods.:
|When set to |
Configure for Segment Analytics
The following settings apply to segment analytics.
For remote analytics, this property identifies the segment API writeKey matching the project to which to push. Within the Segment project lives the configuration for each sink (e.g Google Analytics, Marketo).
The channels for which to record data:
For remote analytics, this value and the
- Make changes to the above properties as needed.
- Save your changes and restart the platform.
Configure for Amplitude Analytics client-side SDK
|When set to |
Open user logging port
NOTE: To receive the full benefits of this feature, the Trifacta node must be able to connect to the public Internet.
On the server hosting the Trifacta platform, the following port must be opened:
- Port 80 (HTTP) and/or
- Port 443 (HTTPS)
Create credentials file
To connect to S3, the Trifacta platform requires that a set of credentials be generated and stored in the following directory. This credentials is provided by Trifacta.
Generate cron job
To regularly upload the generated logs to Trifacta, you can configure a cron job to transfer the files.
- Create an agent or script to periodically run the node process
log-forwarding.js. You should run this once per day.
An example command to run this script from the deployment directory is the following:
To disable the service, set
false. Then, restart the platform.
This page has no comments.