ruby icon indicating copy to clipboard operation
ruby copied to clipboard

Ruby library for logging to LogDNA

Results 10 ruby issues
Sort by recently updated
recently updated
newest added

Found that any uses of `Logdna::Client` within the boot sequence of rails results in subsequent logs never flushing. For background, using logdna 1.5.0 w/ rails 6.1.7.5 on ruby 3.2.2. Configuring...

I recently tried upgrading to Rails 7.1, but this gem seems to be causing an error: ``` ArgumentError: comparison of String with 0 failed ``` The issue does not occur...

The `timestamp` passed to the `log` method via options here https://github.com/logdna/ruby/blob/v1.5.0/lib/logdna.rb#L79-L81 is ignored here https://github.com/logdna/ruby/blob/v1.5.0/lib/logdna/client.rb#L64 Seems that this line should be changed to something like `timestamp: opts[:timestamp]`

`Logdna::Ruby` logger overrides its parent `Logger` class behavior for helper methods such as `#info?`. It also defines a 5th level `TRACE` that seems to be the same as `Loger::Severity::UNKNOWN`. So...

D, [2022-05-01T09:09:23.361998 #45439] DEBUG -- : add not supported in LogDNA logger This litters our development logs. Any reason why it's been built to not support this operation?

Was tracking down some mystery "DEBUG -- : provide either a message or block" messages in my logs. Finally found _one_ reference to it, in another issue here for logdna....

According to the [Ruby docs for the Logger class](https://ruby-doc.org/stdlib-2.4.0/libdoc/logger/rdoc/Logger.html#method-i-info), `#log` has a call pattern where a `progname` is provided and a block is executed only if the log level is...

Hi, I'm getting this error on Rails 7.0.2.3, Ruby 3.0.3: My config/environments/production.rb file contains this line: `config.logger = Logdna::Ruby.new(Rails.application.credentials.dig(:logdna, :secret))`

I've made this change locally. But I think it could go in the public gem. I'm using `ActiveSupport::TaggedLogging` in Rails to include log tags like this: ```ruby # This is...