Sobe Yazılım is a software company based in Turkey. "ASGER" stands for "Askeri Geçiş ve Raporlama" in Turkish, which translates to "Military Access and Reporting" in English. It is a software solution developed by Sobe Yazılım specifically for military organizations to manage access control and generate reports related to military facilities or installations. The ASGER system provides functionality for managing access permissions, monitoring entry and exit of personnel, generating access reports, and ensuring security within military premises.
- All Logsign versions support this integration.
To configure logging for Sobe Yazılım ASGER, you can follow these general steps:
- Identify the logging requirements: Determine what types of events or activities you want to log in ASGER. This may include login attempts, system events, network activities, security incidents, etc.
- Access the ASGER administration interface: Log in to the ASGER administration interface using the appropriate credentials.
- Navigate to the logging configuration: Look for the logging or audit trail configuration settings within the ASGER administration interface. The exact location and naming of these settings may vary depending on the version and specific configuration of ASGER.
- Configure logging options: In the logging configuration section, you will typically find options to enable or disable logging, specify log file paths or destinations, set log levels, define log retention periods, and configure log rotation or archival settings. Adjust these settings according to your logging requirements.
- Choose log formats and details: Determine the format in which you want the logs to be generated, such as plain text, JSON, or syslog. Additionally, decide on the level of detail you want to include in the logs, such as timestamps, source IP addresses, usernames, or event descriptions.
- Save and apply the configuration: Once you have configured the logging settings according to your requirements, save the changes and apply the configuration. ASGER will start generating logs based on the specified settings.
- Test and monitor the logs: Verify that the logs are being generated as expected by performing test activities or monitoring the system events. Regularly review the logs to ensure they capture the desired information and provide the necessary insights for monitoring and troubleshooting.
Sample Log Examples
May 29 14:18:15 asgermanager docker: 14:19:25.493 [https-openssl-apr-8443-exec-31] INFO o.a.g.tunnel.TunnelRequestService - node=proxy type=tunnel account=john.hanks connected to application="DATASKOPE" proto=rdp id=3127