Uploaded image for project: 'Logback-Beagle - the console plugin for Eclipse'
  1. Logback-Beagle - the console plugin for Eclipse
  2. CONSPLUG-21

filtering by logger name is disallowed by filter entry dialog

    XMLWordPrintable

Details

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • None
    • None
    • None
    • None
    • Eclipse 3.5.2, console plugin 1.1

    Description

      Filtering by logger name doesn't appear to work. Dialog says "The new expression is not correct." for a number of filter expressions that seem correctly formed.

      Example use case: I'm trying to filter to accept DEBUG messages from my code, but deny such messages from Spring, whose loggers are called "org.springframework...".

      Example reproduction: I try the following and keep getting "The new expression is not correct." There is no error in the Eclipse error log or in the console.
      logger.contains("org.springframework")
      event.getLoggerName().contains("org.springframework")

      (Guessing types of these supplied variables from http://logback.qos.ch/manual/filters.html#evalutatorFilter.)

      Filtering on the message appears to be accepted by the config window:
      message.contains("org.springframework")
      but it doesn't apply any filtering to the logger name. (Here the logger name actually gets compacted to "o.s...." but trying other, non-compacted, segments of the name doesn't help either.) I assume that this is intended behaviour.

      For now I can filter out things like "reating instance" or "bean", but that's hardly satisfactory. Some more examples in the plugin documentation would be mighty handy.

      Attachments

        Activity

          People

            logback-dev Logback dev list
            joekearney Joe Kearney
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated: