javiermatos / logstash-output-sentry Goto Github PK

I am trying to send events to sentry but I keep getting some issues..
Here is a gist of my config, and what is happening.
https://gist.github.com/joshzitting/acea502208c17aa95626fac90a5912d0

Hello,
I try to send Exception like this

...
 add_field => {
        ...
	"[@metadata][sentry][exception]" => "test text"
   }

sentry {
	        ...
		exception => "[@metadata][sentry][exception]"
                ...
	}

But it doesn`t work.
How to send Exception right?

My output looks like this:

  sentry {
    key => "..."
    secret => "..."
    project_id => "..."
    user => "ip_address:%{clientip}"
    message => "errorcode"
    level => "[@metadata][sentry][level]"
  }

Unfortunately, it seems like Sentry is ignoring the user value. I also tried:

    user => { "ip_address" => "%{clientip}" }

No luck. This actually throws an error. But, really, user should take a hash ... so, what needs to happen to make this possible?

Actually trying to use a hash like the example shown is faced with this error message:

[2019-02-18T04:07:50,232][WARN ][logstash.outputs.sentry  ] Unhandled exception {:exception=>java.lang.ClassCastException: Cannot cast org.jruby.specialized.RubyArrayTwoObject to org.jruby.RubyString}

Any ideas?

hi， How do I use the latest version of sentry?

Hi,

Everything works fine but all my events from logstash into Sentry are seen as "<unlabeled event>".
Setting exception doesn't work, tried:
sentry { .. 'exception' => "Test" }

Please advise.

References

From sentry docs: https://docs.sentry.io/product/sentry-basics/concepts/dsn-explainer/

The secret part of the DSN is optional and effectively deprecated. While clients will still honor it, if supplied, future versions of Sentry will entirely ignore it.

Purpose

Not require secretkey and adapt sentry plugin to this latest version

Motivation

Stop using deprecated features

Hi ,

Can you explain me how can i create a new tag using one of my fields in logstash o/p

Is it possible to make the plugin usable with the latest logstash-core ?