Skip to content
This repository has been archived by the owner on Aug 30, 2023. It is now read-only.

Cannot "override" the packet.Level when calling CaptureMessage #83

Closed
francoishill opened this issue Jun 4, 2016 · 4 comments
Closed

Comments

@francoishill
Copy link

It seams like there is no way to currently override the packet.Level when we call CaptureMessage. The call to client.context.interfaces() is also private so we cannot use the raw client.Capture() method to achieve the same result.

Is there any way to do this as we need to set the level tag to the "log level" on our side?

@goofansu
Copy link

goofansu commented Nov 1, 2016

Have the same problem, I want to set some information to warning level.

@ElPincheTopo
Copy link

Having the same problem

@cpnielsen
Copy link

We are looking to interface Sentry with alerting (OpsGenie and co) for some projects, and being able to set log level to WARNING at least is critical to making this useful.

@kamilogorek
Copy link
Contributor

Moved to #237

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants