Re: [firebase-br] Auditoria Firebird 2.5

Bom dia!

Fiz uma cópia do do fbtrace.conf para tentar fugir de parâmetros que não
existem:
No windows (meu teste que funcionou) exigiu que o log_filename estivesse no
formato:  "C:/meucaminho/meuarquivo.log"
Vou testar isso e também remover a parte abaixo de </database> toda.

<database>
# Do we trace database events or not
enabled true

# Operations log file name. For use by system audit trace only
log_filename /var/log/firebird_audit_database.log

# Maximum size of log file (megabytes). Used by system audit trace for
# log's rotation : when current log file reached this limit it is renamed
# using current date and time and new log file is created. Value of zero
# means that the log file size is unlimited and rotation will never happen.
max_log_size 10


# SQL query filters.
#
# Only SQL statements falling under given regular expression are reported
# in the log.
#include_filter

# SQL statements falling under given regular expression are NOT reported
# in the log.
#exclude_filter


# Put attach/detach log records
log_connections true

# Trace only given connection id. If zero - trace all connections
#connection_id 0

# Put transaction start/end records
log_transactions false


# Put sql statement prepare records
log_statement_prepare false

# Put sql statement free records
log_statement_free false

# Put sql statement execution start records
log_statement_start false
# Put sql statement execution finish\fetch to eof records
log_statement_finish false

# Put record when stored procedure is start execution
log_procedure_start false

# Put record when stored procedure is finish execution
log_procedure_finish false

# Put trigger execute records
log_trigger_start false

# Put trigger execute records
log_trigger_finish false

# Put context variable change records (RDB$SET_CONTEXT)
#log_context false

# Put errors happened
#log_errors false

# Sweep activity
#log_sweep false


# Print access path (plan) with sql statement
print_plan false

# Print detailed performance info when applicable
print_perf false


# Put blr requests compile/execute records
log_blr_requests false

# Print blr requests or not
print_blr false

# Put dyn requests execute records
log_dyn_requests false

# Print dyn requests or not
print_dyn false


# Put xxx_finish record only if its timing exceeds this number of
milliseconds
time_threshold 100

# Maximum length of SQL string logged
# Beware when adjusting max_xxx parameters! Maximum length of log record
# for one event should never exceed 64K.
max_sql_length 300

# Maximum length of blr request logged
max_blr_length 500

# Maximum length of dyn request logged
max_dyn_length 500

# Maximum length of individual string argument we log
max_arg_length 80

# Maximum number of query arguments to put in log
max_arg_count 30
</database>

<services>
# Do we trace services events or not
enabled false
</services>

<database %[\\/]my_database.fdb>
enabled true
</database>

<database %[\\/](test|azk2|rulez).fdb>
enabled true
log_filename \1.log
</database>




On Mon, 22 Apr 2024 at 19:02, Marcelo Daibert <[email protected]> wrote:

> Oi Frederico!
>
> Tudo bem?
> Tem como vc colocar este arquivo ai para a gente ver? O de configuração do
> trace que vc ta colocando.
>
> É alguma coisa no parâmetro log_warnings. Eu sugiro comentar esta linha e
> testar. Mas manda ai para nós.
>
> Obrigado!
> Grande Abraço,
> *Marcelo Daibert*
> Email/MSN/Gtalk: [email protected]
> Telefone: +55(32)98435-8979
> Skype: MSDaibert
> Perfil Completo <https://plus.google.com/u/0/+MarceloDaibert/about>
> <http://lattes.cnpq.br/2823279949488775>
> <http://www.facebook.com/msdaibert>  <http://twitter.com/msdaibert>
> <http://www.delicious.com/msdaibert>
> <http://picasaweb.google.com/msdaibert>
> <http://youtube.com/user/MSDaibert>  <http://daibert.pro/>
> <http://www.appbrain.com/user/msdaibert/>Site: http://daibert.pro
>
>
> Em seg., 22 de abr. de 2024 às 18:36, Frederico Godoi via lista <
> [email protected]> escreveu:
>
>> Pessoal boa noite,
>>
>> Estou tentando implementar uma auditoria em um Firebird 2.5 vanilla
>> (Classic) e estou apanhando um pouco no Linux.
>> Quando liguei o parâmetro no firebird.conf apontando para o meu arquivo
>> auditoria.conf (copia do fbtrace.conf , porém com os parâmetros básicos )
>> só estou enfrentando esse erro no firebird.log
>>
>> Trace plugin libfbtrace.so returned error on call trace_create.
>> Error details: error while parsing trace configuration
>> line 17: element "log_warnings" is unknown
>>
>> Alguém já fez em Linux? alguma dica?
>>
>> Obrigado
>> --
>> Frederico Godoi
>> ______________________________________________
>> FireBase-BR (www.firebase.com.br) - Hospedado em www.locador.com.br
>> Para saber como gerenciar/excluir seu cadastro na lista, use:
>> http://www.firebase.com.br/fb/artigo.php?id=1107
>> Para consultar mensagens antigas:
>> http://www.firebase.com.br/pesquisa_lista.html
>>
>

-- 
Frederico Godoi
______________________________________________
FireBase-BR (www.firebase.com.br) - Hospedado em www.locador.com.br
Para saber como gerenciar/excluir seu cadastro na lista, use: http://www.firebase.com.br/fb/artigo.php?id=1107
Para consultar mensagens antigas: http://www.firebase.com.br/pesquisa_lista.html