13 Jan 2025 01:58 PM
Hi all,
Just wondering on what metrics are useful to monitor/alert? Curious how everyone has set it up in their environment.
13 Jan 2025 03:23 PM
My suggestion as minimum:
14 Jan 2025 11:15 AM
Thanks. This is a good starter 🙂
I noticed in the extension that it mentioned that you could pull up login calls through the logs. I've tried logging in several times but I've not been able to find an entry relating to logins at all within the logs. Just wondering if you know how to get the most out of the logs.
14 Jan 2025 11:24 AM
Check the extension information you can find it under
Log Management and Analytics
OS means that the audit logs are stored locally in the file.
specifies the log file's location
Configure LogAgent's security rules to allow access to local files, by adding the oracle.json file under :
{ "@version": "1.0.0", "allowed-log-paths-configuration": [ { "directory-pattern": "/u01/app/oracle/admin/oracle_standalone/adump/", "file-pattern": "*.aud", "action": "INCLUDE" } ] }
Agent restart is not required, this config will be applied within 1 minute.
Use the log file location fetched via the query executed in the first step, e.g. /u01/app/oracle/admin/oracle_standalone/adump/*.
An example configuration that includes only ORA-01017 that reports invalid username or password logon attempts could be configured using: Log content is any of: (.*)RETURNCODE:\[(\d+)\] "1017 AND Log source is any of: /u01/app/oracle/admin/oracle_standalone/adump/*
Logs collected the way described above can be accessed using following DQL query: fetch logs | filter matchesValue(log.source, "/u01/app/oracle/admin/oracle_standalone/adump/*").
Configure log processing rule to extract log attributes out of the log content:
PARSE(content, " DATA ' RETURNCODE:['INT']' SPACE '\"' INT:ora.returncode LD") | PARSE(content, " DATA ' USERID:['INT']'SPACE CSVDQS:ora.userid LD") | PARSE(content, " DATA ' USERHOST:['INT']'SPACE CSVDQS:ora.userhost LD")
Extract metrics from log entries to enable alerting:
14 Jan 2025 11:40 AM
Does this require a OneAgent on the actual database server itself?