logback-awslogs-appender | An Amazon Web Services Logs appender | AWS library

by pierredavidbelanger Java Version: 1.7.2 License: LGPL-3.0

X-Ray Key Features Code Snippets(3)Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | logback-awslogs-appender Summary

logback-awslogs-appender is a Java library typically used in Cloud, AWS applications. logback-awslogs-appender has no vulnerabilities, it has build file available, it has a Weak Copyleft License and it has low support. However logback-awslogs-appender has 4 bugs. You can download it from GitHub, Maven.

An Amazon Web Services CloudWatch Logs appender for Logback.

Support

Quality

Security

License

Reuse

Support

logback-awslogs-appender has a low active ecosystem.

It has 40 star(s) with 24 fork(s). There are 4 watchers for this library.

It had no major release in the last 12 months.

There are 3 open issues and 15 have been closed. On average issues are closed in 5 days. There are 1 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of logback-awslogs-appender is 1.7.2

Quality

logback-awslogs-appender has 4 bugs (0 blocker, 0 critical, 3 major, 1 minor) and 33 code smells.

Security

logback-awslogs-appender has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

logback-awslogs-appender code analysis shows 0 unresolved vulnerabilities.

There are 3 security hotspots that need review.

License

logback-awslogs-appender is licensed under the LGPL-3.0 License. This license is Weak Copyleft.

Weak Copyleft licenses have some restrictions, but you can use them in commercial projects.

Reuse

logback-awslogs-appender releases are not available. You will need to build from source code and install.

Deployable package is available in Maven.

Build file is available. You can build the component from source.

Installation instructions, examples and code snippets are available.

It has 946 lines of code, 88 functions and 11 files.

It has medium code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed logback-awslogs-appender and discovered the below as its top functions. This is intended to give you an instant insight into logback-awslogs-appender implemented functionality, and help decide if they suit your requirements.

Appends an event to the client
Trim off the event size
Log events
Constructs the AWS logs client
Waits for the logs to be flushed
Flush events to AWS logs
Returns the total number of events in the batch
Drains a batch of messages from the queue
Retrieves and computes the result
Tries to compute the value if necessary
Set the CloudWatch endpoint
Returns true if the given text is not empty
Stop the scheduler
Stops AWS logs
Appends an event to the log
Get the max time in milliseconds
Append logging event
Set the prefix for the log stream to use
Starts the asynchronous worker
This method initializes log group
Stops the thread
Start logging
Sets the metrics

Get all kandi verified functions for this library.

logback-awslogs-appender Key Features

No Key Features are available at this moment for logback-awslogs-appender.

logback-awslogs-appender Examples and Code Snippets

Logback AWSLogs appender,More configurations

Java

Lines of Code : 69

License : Weak Copyleft (LGPL-3.0)

Copy



    
    
    
    

    
    

    
    
    
        
        
            WARN
        
        
        
        
            %d{yyyyMMdd'T'HHmmss} %thread %level %logger{15} %msg%n
        
        
        
        /com/acme/myapp

Logback AWSLogs appender,Quick start,logback.xml

Java

Lines of Code : 22

License : Weak Copyleft (LGPL-3.0)

Copy

{
  "Statement": [
    {
      "Action": [
        "logs:CreateLogGroup",
        "logs:CreateLogStream",
        "logs:PutLogEvents"
      ],
      "Effect": "Allow",
      "Resource": "arn:aws:logs:*:*:*"
    }
  ]
}

Logback AWSLogs appender,Quick start,pom.xml

Java

Lines of Code : 14

License : Weak Copyleft (LGPL-3.0)

Copy


    
        
            org.slf4j
            slf4j-api
            1.7.21
        
        
            ca.pjer
            logback-awslogs-appender
            1.4.0

Community Discussions

Trending Discussions on logback-awslogs-appender

AWS Cloudwatch Logback Appender for Spring Boot Applications

Where does this ClientAbortException come from?

QUESTION

AWS Cloudwatch Logback Appender for Spring Boot Applications

Asked 2018-Feb-15 at 11:49

I'm trying to send Logs directly to Cloudwatch from my Spring Boot Application. The Logback Appender I'm using, of course needs AWS Credentials. Since most developers doesn't have AWS Credentials on their local machines and just want to log into a file according to the the logback-spring.xml configuration. Most tests fail locally, because of missing aws credentials.
Is there a way to initialize the logback appender only for a specific profile?
Here's a snapshot of the logback-spring.xml:

...

ANSWER

Answered 2018-Feb-15 at 11:49

Already solved. You just need to extract the appender to another logback-file:

logback-spring.xml

Source https://stackoverflow.com/questions/46281813

QUESTION

Where does this ClientAbortException come from?

Asked 2017-Apr-12 at 22:09

I have a Spring-Boot application, which constantly shows this error in its logs:

[xec-104] ERROR Exception Processing ErrorPage[errorCode=0, location=/error] org.apache.catalina.connector.ClientAbortException: java.io.IOException: Connection reset by peer at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:340) at org.apache.catalina.connector.OutputBuffer.flush(OutputBuffer.java:303) at org.apache.catalina.connector.CoyoteOutputStream.flush(CoyoteOutputStream.j ava:109) at com.fasterxml.jackson.core.json.UTF8JsonGenerator.flush(UTF8JsonGenerator.j ava:1048) at com.fasterxml.jackson.databind.ObjectWriter.writeValue(ObjectWriter.java:95 3) at org.springframework.http.converter.json.AbstractJackson2HttpMessageConverte r.writeInternal(AbstractJackson2HttpMessageConverter.java:285) at org.springframework.http.converter.AbstractGenericHttpMessageConverter.writ e(AbstractGenericHttpMessageConverter.java:100) at org.springframework.web.servlet.mvc.method.annotation.AbstractMessageConver terMethodProcessor.writeWithMessageConverters(AbstractMessageConverterMethod Processor.java:231) at org.springframework.web.servlet.mvc.method.annotation.HttpEntityMethodProce ssor.handleReturnValue(HttpEntityMethodProcessor.java:203) at org.springframework.web.method.support.HandlerMethodReturnValueHandlerCompo site.handleReturnValue(HandlerMethodReturnValueHandlerComposite.java:81) at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandl erMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:132) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandler Adapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:827) at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandler Adapter.handleInternal(RequestMappingHandlerAdapter.java:738) at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.han dle(AbstractHandlerMethodAdapter.java:85) at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServ let.java:963) at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServl et.java:897) at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkSe rvlet.java:970) at org.springframework.web.servlet.FrameworkServlet.doGet(FrameworkServlet.jav a:861) at javax.servlet.http.HttpServlet.service(HttpServlet.java:622) at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.j ava:846) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Applicatio nFilterChain.java:230) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterC hain.java:165) at org.apache.catalina.core.ApplicationDispatcher.invoke(ApplicationDispatcher .java:726) at org.apache.catalina.core.ApplicationDispatcher.processRequest(ApplicationDi spatcher.java:471) at org.apache.catalina.core.ApplicationDispatcher.doForward(ApplicationDispatc her.java:394) at org.apache.catalina.core.ApplicationDispatcher.forward(ApplicationDispatche r.java:311) at org.apache.catalina.core.StandardHostValve.custom(StandardHostValve.java:39 5) at org.apache.catalina.core.StandardHostValve.status(StandardHostValve.java:25 4) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:17 7) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79 ) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.jav a:87) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:349) at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:784) at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.jav a:66) at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtoc ol.java:802) at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.ja va:1410) at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java :49) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1 142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java: 617) at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.j ava:61) at java.lang.Thread.run(Thread.java:745) Caused by: java.io.IOException: Connection reset by peer at sun.nio.ch.FileDispatcherImpl.write0(Native Method) at sun.nio.ch.SocketDispatcher.write(SocketDispatcher.java:47) at sun.nio.ch.IOUtil.writeFromNativeBuffer(IOUtil.java:93) at sun.nio.ch.IOUtil.write(IOUtil.java:65) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:471) at org.apache.tomcat.util.net.NioChannel.write(NioChannel.java:134) at org.apache.tomcat.util.net.NioBlockingSelector.write(NioBlockingSelector.ja va:101) at org.apache.tomcat.util.net.NioSelectorPool.write(NioSelectorPool.java:157) at org.apache.tomcat.util.net.NioEndpoint$NioSocketWrapper.doWrite(NioEndpoint .java:1221) at org.apache.tomcat.util.net.SocketWrapperBase.flushBlocking(SocketWrapperBas e.java:451) at org.apache.tomcat.util.net.SocketWrapperBase.flush(SocketWrapperBase.java:4 41) at org.apache.coyote.http11.Http11OutputBuffer.flushBuffer(Http11OutputBuffer. java:514) at org.apache.coyote.http11.Http11OutputBuffer.flush(Http11OutputBuffer.java:2 43) at org.apache.coyote.http11.Http11Processor.flush(Http11Processor.java:1495) at org.apache.coyote.AbstractProcessor.action(AbstractProcessor.java:284) at org.apache.coyote.Response.action(Response.java:167) at org.apache.catalina.connector.OutputBuffer.doFlush(OutputBuffer.java:336) ... 41 common frames omitted

As you can see, the stack trace does not reveal anything from my application. This exception happens purely in the infrastructure. What does it mean and how can I reproduce that? Also, I don't get why there's Jackson in the stack trace. I have no where any JSON output in my application.

At the end I want to understand if my application has an issue. If so, fix that. If not, I don't want to have this in my log as an ERROR.

Edit: As requested, this is the pom.xml:

...

ANSWER

Answered 2017-Apr-12 at 22:09

This is caused because the client is closing the connection before Tomcat has the chance to write out the response.

The main perpetrator of this exception tends to be "Internet Explorer" because of how it handles resource connections (like downloading JavaScript, css, icons etc); if it decides it no longer needs the resource, it closes the connection before the server has a chance to write out to it. I also see it more when you are using Angularjs, or other SPA frameworks, in IE. You will know it is caused by IE because the request resource path with be to a resource file (as described previously).

The second (or equally?) most common culprit could be users refreshing the page multiple times before it has a chance to finish loading, or the user navigating away before the page finishes loading.

The third culprit, and less common but WAY more infuriating, is when you are calling services on your own network. You will see a "ClientAbortException" on the called service and a "SocketException: connection reset" on the client service. The cause is normally because of badly configured firewalls. I talked with my Systems Administrator, and she said that the last time it happened to me it was because the replication traffic was too high during peak usage so the firewall could not return the packet in time. The solution was to throttle traffic from specific sources (such as replication) during peak usage of other essential applications. I suppose you could duplicate this error by simulating heavy usage and traffic through the firewall.

Source https://stackoverflow.com/questions/41752535

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install logback-awslogs-appender

The simplest config that actually (synchronously) send logs to CloudWatch (see More configurations section for a real life example):.
The Layout will default to EchoLayout.
The Log Group Name will default to AwsLogsAppender.
The Log Stream Name will default to a timestamp formated with yyyyMMdd'T'HHmmss.
The AWS Region will default to the AWS SDK default region (us-east-1) or the current instance region.
The maxFlushTimeMillis will default to 0, so appender is in synchronous mode.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: