Skip to main content

Device App Connection Log

The deviceDevice appApp connectionConnection logLog API providesenables functionalityapplications to register detailed network connection eventslogs betweenfor devicesmonitoring and applications.analytics purposes. This endpoint iscaptures comprehensive network connectivity data including connection types, security protocols, location information, and performance metrics, making it essential for trackingnetwork monitoring applications and connectivity patterns,analysis monitoring device activity, and maintaining audit trails for security and compliance purposes.tools.

Base URL: https://gate.zequenze.com/api/v1

Authentication: All endpoints require a Bearer token:

Authorization: Bearer <your-api-token>

Overview

The Device App Connection Log API allowsprovides youa centralized way to recordtrack and tracklog network connectionconnections events betweenfrom devices and applicationsapplications. within your system. This logging mechanism is crucial for:

    Security Monitoring: Track when devices connect to applications and identify unusual connection patterns Compliance Auditing: Maintain detailed logs of device-application interactions for regulatory requirements Network Analytics: Analyze connection patterns to optimize network performance and identify bottlenecks Troubleshooting: Diagnose connectivity issues by reviewing historical connection data

    This API is typicallydesigned usedfor by network monitoring tools, security applications, and device management systemsorganizations that need to monitor network usage patterns, analyze connectivity performance, and maintain comprehensivedetailed logsrecords of device connectivitynetwork events.activity.

    The

    Key loggedFeatures:

      Support for multiple network types (WiFi, Mobile, Bluetooth, Ethernet) Comprehensive security protocol tracking (Open, WEP, WPA, WPA2, 3GPP) Location-based logging with GPS coordinates Network performance metrics including data cantransfer beand usedlink speeds Connection quality measurements (RSSI, SINR) Mobile network specifics (MCC/MNC, Cell ID, roaming status)

      Common Use Cases:

        Network performance monitoring and analytics Device connectivity auditing and compliance Troubleshooting network connectivity issues Gathering data for generatingnetwork reports,optimization triggeringSecurity alerts,monitoring orand feedinganomaly intodetection analytics systems.

        Endpoints

        POST /device_app_connection_log/

        Description: Registers a new network connection log entry betweenwith detailed network information, performance metrics, and location data. This endpoint is typically called when a device andestablishes, anmaintains, application.or Thisterminates endpointa capturesnetwork connection events in real-time, allowing you to buildcreate a comprehensive audit trail of device-application interactions. Use this endpoint whenever a device establishes or terminates a connection with an application to maintain accurate connectivity records.trail.

        Use Cases:

        • LogLogging deviceWiFi authenticationconnection events towith applicationssecurity and performance details
        • RecordRecording connectionmobile attemptsnetwork connections including roaming status and cell information
        Tracking network usage patterns for analytics and optimization Creating audit trails for security monitoring Track application usage patterns across devices Maintainand compliance logs for auditing purposes Monitor network connectivity for troubleshootingmonitoring

        Full URL Example:

        https://gate.zequenze.com/api/v1/device_app_connection_log/
        

        Parameters:

        Parameter Type In Required Description
        data string body Yes JSON string containing the network connection log detailsdata
        including

        Request Body Schema:

        Field Type Required Description network_name string No Name of the current network (e.g., "Office WiFi", "Guest Network") network_type string Yes Network type. Use: 'wi' (WiFi), 'mo' (Mobile), 'bl' (Bluetooth), 'et' (Ethernet) network_security string Yes Security protocol. Use: 'opn' (Open), 'wep' (WEP), 'wpa' (WPA), 'wp2' (WPA2), '3gp' (3GPP) network_mccmnc string No Mobile Country Code/Mobile Network Code for mobile networks frequency number No Wireless network frequency in Hz (e.g., 2.4, 5.0 for WiFi) authentication string No Authentication method. Use: 'non' (None), 'cpo' (Captive portal), 'wis' (WISPr), 'psk' (Pre-shared key), 'rad' (RADIUS MAC-based), 'eap' (EAP/802.1x), '3gp' (3GPP) bssid string No Basic Service Set Identifier for wireless networks cellid string No Mobile network Cell ID identifier roaming boolean No True if device ID,was applicationroaming ID,on a non-home network latitude string No GPS latitude coordinate in decimal format longitude string No GPS longitude coordinate in decimal format inbytes integer No Number of bytes received during the connection timestamp, status,andoutbytes metadatainteger No Number of bytes transmitted during the connection link_speed number No Maximum attainable link speed in Mbps quality_metric string No Connection quality measurement type. Use: 'rssi' (RSSI), 'sinr' (SINR) quality_value number No Numeric value for the quality metric

        cURL Example:

        curl -X POST "https://gate.zequenze.com/api/v1/device_app_connection_log/" \
          -H "Authorization: Bearer YOUR_API_TOKEN" \
          -H "Content-Type: application/json" \
          -d '{
            "device_id"network_name": "DEV-001-XR7H9",Office "application_id":WiFi "APP-MOBILE-001",
            "connection_type": "established",
            "timestamp": "2024-01-15T14:30:25Z",
            "ip_address": "192.168.1.105",
            "user_agent": "MobileApp/2.1.0 (iOS 17.0)",
            "status": "success",
            "duration": null,
            "metadata": {
              "location": "Building A - Floor 2"5GHz",
            "network_type": "WiFi"wi",
            "signal_strength"network_security": "wp2",
            "frequency": 5.2,
            "authentication": "psk",
            "bssid": "aa:bb:cc:dd:ee:ff",
            "latitude": "40.7128",
            "longitude": "-74.0060",
            "inbytes": 1048576,
            "outbytes": 524288,
            "link_speed": 150.0,
            "quality_metric": "rssi",
            "quality_value": -45
            }45.0
          }'
        

        Example RequestResponse Body:(201 Created):

        {
          "device_id"network_name": "DEV-001-XR7H9",Office "application_id":WiFi "APP-MOBILE-001", 
          "connection_type": "established",
          "timestamp": "2024-01-15T14:30:25Z",
          "ip_address": "192.168.1.105",
          "user_agent": "MobileApp/2.1.0 (iOS 17.0)",
          "status": "success",
          "duration": null,
          "metadata": {
            "location": "Building A - Floor 2"5GHz",
          "network_type": "WiFi"wi",
          "signal_strength"network_security": "wp2",
          "network_mccmnc": null,
          "frequency": 5.2,
          "authentication": "psk",
          "bssid": "aa:bb:cc:dd:ee:ff",
          "cellid": null,
          "roaming": null,
          "latitude": "40.7128",
          "longitude": "-74.0060",
          "inbytes": 1048576,
          "outbytes": 524288,
          "link_speed": 150.0,
          "quality_metric": "rssi",
          "quality_value": -45,
            "session_id": "sess_abc123xyz",
            "protocol": "HTTPS"
          }45.0
        }
        

        ExampleMobile Response:Network Example:

        curl -X POST "https://gate.zequenze.com/api/v1/device_app_connection_log/" \
          -H "Authorization: Bearer YOUR_API_TOKEN" \
          -H "Content-Type: application/json" \
          -d '{
            "id": 12847,
          "device_id"network_name": "DEV-001-XR7H9",Verizon "application_id": "APP-MOBILE-001",
          "connection_type": "established",
          "timestamp": "2024-01-15T14:30:25Z",
          "ip_address": "192.168.1.105",
          "user_agent": "MobileApp/2.1.0 (iOS 17.0)",
          "status": "success",
          "duration": null,
          "created_at": "2024-01-15T14:30:26Z",
          "metadata": {
            "location": "Building A - Floor 2"LTE",
            "network_type": "WiFi"mo",
            "signal_strength": -45,
            "session_id"network_security": "sess_abc123xyz"3gp",
            "protocol"network_mccmnc": "HTTPS"310012",
            "authentication": "3gp",
            "cellid": "12345678",
            "roaming": false,
            "latitude": "37.7749",
            "longitude": "-122.4194",
            "inbytes": 2097152,
            "outbytes": 1048576,
            "quality_metric": "sinr",
            "quality_value": 15.2
          }
        }'
        

        Response Codes:

        Status Description
        201 Created - Connection log successfully registered
        400 Bad Request - Invalid data format or missing required fields
        401 Unauthorized - Invalid or missing APIauthentication token
        422 Unprocessable Entity - ValidInvalid format but invalid datafield values
        or 500 Internal Server Error - Server processing errorconstraints

        Common Use Cases

        Use Case 1: Real-timeWiFi SecurityConnection Monitoring

        MonitorApplications devicemonitoring connectionsWiFi inconnectivity real-timecan tolog detect unauthorized access attempts or unusualeach connection patterns. Log every connection attemptevent with devicenetwork details,name, timestamps,security type, signal strength, and connectiondata outcomesusage. toThis feedhelps intoidentify securitynetwork monitoringperformance dashboards.issues and optimize WiFi deployments.

        Use Case 2: ComplianceMobile AuditNetwork TrailAnalytics

        MaintainMobile detaileddevice logsmanagement ofapplications allcan device-applicationtrack cellular connections forincluding regulatorycarrier complianceinformation, requirements.roaming Record connection events with timestamps, user context,status, and sessiondata detailsconsumption to supportanalyze auditmobile processesnetwork usage patterns and compliance reporting.costs.

        Use Case 3: Location-Based Network Performance AnalyticsAnalysis

        TrackIoT devices and mobile applications can combine network connection patternsdata andwith durationsGPS coordinates to analyze network performancecoverage, identify dead zones, and identifycorrelate bottlenecks.network Useperformance connectionwith logsgeographic to understand peak usage times, popular applications, and connection quality metrics.locations.

        Use Case 4: TroubleshootingSecurity Connectivity IssuesAuditing

        CreateSecurity detailedapplications can log network connections to detect unusual network access patterns, unauthorized network usage, or potential security threats by analyzing connection logs to assist with diagnosing connectivity problems. Include metadata such as signal strength, network type,types and errorauthentication codes to help technical teams quickly identify and resolve issues.methods.

        Use Case 5: UsagePerformance AnalyticsTroubleshooting

        Network diagnostic tools can capture detailed connection metrics including link speeds, signal quality, and Reportingdata

        Generatetransfer reportsvolumes onto applicationhelp usagetroubleshoot patterns,connectivity device activity,issues and connection statistics. Use the logged data to understand user behavior, optimize resource allocation, and plan network capacity.performance.


        Best Practices

        • Data Accuracy: Ensure network type and security values use the specified codes (wi, mo, bl, et for types; opn, wep, wpa, wp2, 3gp for security) to maintain data consistency
        Location Privacy: Only include GPS coordinates when necessary for your use case and ensure compliance with privacy regulations Batch LoggingProcessing: For high-volume environments,logging, consider implementing client-side batching multipleto connection events into singlereduce API calls toand improve performance Error Handling: Implement retry logic for failednetwork failures, but avoid duplicate log submissions,entries especiallyby forusing criticalclient-side security events that must be recordeddeduplication Data RetentionValidation: PlanValidate data locally before sending to avoid 400/422 errors, especially for lognumeric datafields retentionlike frequency and archivalquality strategies, as connection logs can accumulate quickly in active environmentsvalues SensitiveSecurity DataConsiderations: AvoidUse HTTPS for all requests and store API tokens securely, especially when logging sensitive network information like passwords or personal data in the metadata fields - focus on connection and technical details Timestamp Accuracy: Ensure timestamps are in UTC format and accurately reflect the actual connection time for proper chronological ordering Rate Limiting: Be aware of potential rate limits and implement appropriate queuing mechanisms for high-frequency logging scenarios Monitoring: SetTrack upAPI alertsresponse fortimes failedand logerror submissionsrates to ensure yourreliable auditlogging, trailas remainsmissing completeconnection andlogs reliablecan impact analytics accuracy