graylog-labs / play2-graylog2 Goto Github PK

[DEPRECATED] How to send logs from the Play! framework to Graylog

License: Apache License 2.0

Scala 43.55% Java 56.45%

play2-graylog2's Introduction

Caution

This repository is deprecated and not in use anymore. It is kept for historical purposes, but no PRs will be merged, no issues will be worked on.

play2-graylog2

Play 2 module for sending application logs to Graylog2

See the project-code/README for an introduction, or play around with the provided sample application.

Please refer to the Ivy repository overview page for instructions on how to include the module in your Play application

License

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

play2-graylog2's People

Contributors

Stargazers

Watchers

Forkers

drexin pawank nsanitas mcornejo pabloluisperez neowinx sheavner tusharm58 learnnext panshin isabella232

play2-graylog2's Issues

Write apache httpd log format string parser

To support writing a local access log as well as a structured one, we would like to reuse apache's log format strings.

Parse the string, and include the mentioned fields in the GELF packet, as well as format the string accordingly for writing to disk.

Add support for UDP transport

The TCP implementation has an in-memory queue between logging and sending the request to decouple the application from logging problems.
Optionally allow logging over UDP as well, for those that really don't care if they lose the occasional message.

This needs a proper GELF chunking implementation.

Support multiple graylog2 servers

The module only supports a single server currently.

Make use of an entire cluster of nodes to support sending more logs, more reliably.

For use in graylog2-web-interface the list must also be configurable from within the application itself.

Understanding Scala example

In the example for sending a structured access log using Scala looks like:
import play.api.mvc._
import org.graylog2.logback.appender.AccessLog

object Global extends WithFilters(AccessLog) {
    ...
}

I'm unclear what would replace the ellipsis. Can someone point me in the right direction?

[error] Modules were resolved with conflicting cross-version suffixes in {file:/Users/mariussoutier/Workspace/Play.workspace/graylog2-demo/}root:
[error]    com.typesafe.play:play-functional _2.11, _2.10
[error]    com.typesafe.akka:akka-actor _2.11, _2.10
[error]    com.typesafe.play:play-json _2.11, _2.10
[error]    com.typesafe.play:play _2.11, _2.10
[error]    com.typesafe.play:play-iteratees _2.11, _2.10
[error]    com.typesafe.play:twirl-api _2.11, _2.10
[error]    com.typesafe.akka:akka-slf4j _2.11, _2.10
[error]    org.scala-stm:scala-stm _2.11, _2.10
[error]    com.typesafe.play:play-datacommons _2.11, _2.10

Resolver can't be found - version 1.1 needed

Hi,

I use Play 2.2.3 and I want to use this module for sending application logs to Graylog2. As I see here: https://graylog2.github.io/play2-graylog2/index.html, I need version 1.1. The problem is the resolver http://graylog2.github.io/play2-graylog2/releases/ doesn't work and 1.1 is not in the Maven Central Repository.

Thanks for your help.

Double check way we check response.body size

cuz it can't be right. Please let it not be like this.