1
Connect Application Logs
Select how you wish to connect your application logs to Trusys. This is crucial for data ingestion and analysis:
Folder MethodInput the folder path where your application logs are stored. Select the cloud provider (currently Azure and AWS are supported) and provide the necessary authentication details.
SDK MethodSelect this option and choose an existing API key to save the configuration. This API key should be integrated into your application’s project to send logs directly to Trusys.1. Install the SDKInstall 2. Set Environment VariablesConfigure the required environment variables for exporting telemetry data:4. Initialize the SDKInitialize This sets up observability and monitoring hooks automatically for your application.
openlit using pip:💡 Replace3. Import the SDKIn your application code, import theabc123with your actual API key. Refer to the documentation on “How to Create an API Key” for more details. 💡 Replacexyz123with your actual application ID of your application on trusys platform.
openlit SDK:openlit with your application ID:2
Define Collection Settings
Configure how Trusys collects data from your logs:
Sampling Frequency– Choose between percentage-wise or count-wise sampling.Enter Percentage or Count– Specify the exact percentage of logs to sample (e.g., 10% of logs) or the number of logs to sample (e.g., 100 logs).
By default, sampling is performed and evaluated every hour.
3
Define Functional Monitoring Metrics
Select functional metrics against which you want to monitor your production logs and define their respective expected values. These metrics assess the performance and accuracy of your AI application in real-time.4
Define Security Monitoring Metrics
Select vulnerable categories you wish to monitor for your application. This ensures continuous vigilance against potential security threats and compliance breaches.Session Tracking for Conversational ApplicationsFor applications that maintain user sessions (such as chatbots, virtual assistants, or multi-turn conversational interfaces), implement session tracking to enable comprehensive evaluation and monitoring of complete user journeys.
Evaluation is performed on traces with the same On session end:
application.id, and sessions are identified by grouping traces that share a session.id attribute. The end of a session is explicitly marked with the ended status.On every request:Upon successfully enabling monitoring, you will begin to see traces from your application appear in the Traces section, detailed evaluation results for each log, and a Monitoring Dashboard providing an overview of your application’s health, functional metric evaluations, and security evaluations.