Skip to content

How to Configure Data Logging

Set up data logging to capture CAN bus data to files, InfluxDB, Prometheus, or MQTT.

Prerequisites

  • An active profile with components configured
  • (For cloud logging) Access to InfluxDB, Prometheus, or MQTT server
  • Admin access to configure loggers

Steps

Step 1: Choose Your Logger Type

Profinity supports: - File Logger - Log to CSV or other file formats - InfluxDB/Prometheus Logger - Log to time-series databases - MQTT Logger - Publish data to MQTT brokers

Step 2: Add a Logger Component

  1. Navigate to ADMIN → Components
  2. Click Add Component
  3. Select your logger type:
  4. File Logger
  5. InfluxDB Prometheus Logger
  6. MQTT Logger

Step 3: Configure File Logger

  1. Set Logger Name
  2. Configure File Path - where log files are saved
  3. Set File Format - CSV, JSON, etc.
  4. Configure Logging Interval - how often to write data
  5. Select Components - choose which components to log
  6. Click Save

Step 4: Configure InfluxDB/Prometheus Logger

  1. Set Logger Name
  2. Configure connection:
  3. InfluxDB URL - server address
  4. Database Name - target database
  5. Username/Password - credentials
  6. Set Logging Interval
  7. Select Components
  8. Test Connection
  9. Click Save

Step 5: Configure MQTT Logger

  1. Set Logger Name
  2. Configure MQTT Broker:
  3. Broker URL - MQTT broker address
  4. Port - usually 1883 or 8883
  5. Username/Password - if required
  6. Topic Prefix - base topic for messages
  7. Set Publishing Interval
  8. Select Components
  9. Test Connection
  10. Click Save

Step 6: Activate the Logger

  1. Ensure logger is added to your active profile
  2. Logger starts automatically when profile is active
  3. Check logger status in component list

Step 7: Verify Logging

File Logging: - Check file path for new log files - Verify data is being written

InfluxDB/Prometheus: - Query database to verify data is arriving - Check connection status in logger component

MQTT: - Subscribe to MQTT topics to see published messages - Check logger status for connection info

Tips

  • Start with File Logging: Easiest to set up and verify
  • Monitor Disk Space: File loggers can generate large files
  • Use Appropriate Intervals: Balance between data granularity and resource usage
  • Test Connections: Always test cloud loggers before relying on them
  • Filter Components: Only log components you need to reduce data volume

Troubleshooting

  • No data being logged: Check that components are selected and active
  • Connection errors: Verify network connectivity and credentials
  • Missing data: Check logging intervals and component data availability