Skip to main content

Logging to Graphite monitoring tool from java

We use Graphite as a tool for monitoring some stats and watch trends. A requirement is to monitor impact of new releases as build is deployed to app nodes to see if things like
1) Has the memcache usage increased.
2) Has the no of Java exceptions went up.
3) Is the app using more tomcat threads.
Here is a screenshot

We changed the installer to log a deploy event when a new build is deployed. I wrote a simple spring bean to log graphite events using java. Logging to graphite is easy, all you need to do is open a socket and send lines of events.


import org.slf4j.Logger;
import org.slf4j.LoggerFactory; 
import java.io.OutputStreamWriter;
import java.io.Writer;
import java.net.Socket;
import java.util.HashMap;
import java.util.Map;


public class GraphiteLogger {
private static final Logger logger = LoggerFactory.getLogger(GraphiteLogger.class);
 private String graphiteHost;

 private int graphitePort;

 public String getGraphiteHost() {
  return graphiteHost;
 }

 public void setGraphiteHost(String graphiteHost) {
  this.graphiteHost = graphiteHost;
 }

 public int getGraphitePort() {
  return graphitePort;
 }

 public void setGraphitePort(int graphitePort) {
  this.graphitePort = graphitePort;
 }

 public void logToGraphite(String key, long value) {
  Map stats = new HashMap();
  stats.put(key, value);
  logToGraphite(stats);
 }
 
 public void logToGraphite(Map stats) {
  if (stats.isEmpty()) {
   return;
  }

  try {
   String nodeIdentifier = java.net.InetAddress.getLocalHost().getHostName();
   logToGraphite(nodeIdentifier, stats);
  } catch (Throwable t) {
   logger.warn("Can't log to graphite", t);
  }
 }

 private void logToGraphite(String nodeIdentifier, Map stats) throws Exception {
  Long curTimeInSec = System.currentTimeMillis() / 1000;
  StringBuffer lines = new StringBuffer();
  for (Map.Entry entry : stats.entrySet()) {
   String key = nodeIdentifier + "." + entry.getKey();
   lines.append(key).append(" ").append(entry.getValue()).append(" ").append(curTimeInSec).append("\n"); //even the last line in graphite 
  }
  logToGraphite(lines);
 }

 private void logToGraphite(StringBuffer lines) throws Exception {
  String msg = lines.toString();
  logger.info("Writing [{}] to graphite", msg);
  Socket socket = new Socket(graphiteHost, graphitePort);
  try {
   Writer writer = new OutputStreamWriter(socket.getOutputStream());
   writer.write(msg);
   writer.flush();
   writer.close();
  } finally {
   socket.close();
  }
 }

 public static void main(String[]args) throws Exception {
  String host = args[0];
  int port = Integer.parseInt(args[1]);
  String nodeIdentifier ="tomcat.UI.planck_8080";
  Map stats = new HashMap();
  stats.put("memcache_calls", 900L);
  stats.put("num_threads", 50L);
  GraphiteLogger graphiteLogger = new GraphiteLogger();
  graphiteLogger.setGraphiteHost(host);
  graphiteLogger.setGraphitePort(port);
  graphiteLogger.logToGraphite(nodeIdentifier, stats);
 }
}


Comments

  1. Nice article , you have indeed covered topic in details with code examples and explanation. I have also blogged some of my experience as 10 tips on logging in Java

    Thanks
    Javin
    10 tips on logging in Java

    ReplyDelete
  2. How do you create the vertical line for deploys?

    ReplyDelete
  3. Thanks for posting your Java code. I'm guessing it will give me an hour head start on my project. ;)

    ReplyDelete
  4. It is a super article. and im getting some error in line
    #53 for (Map.Entry entry : stats.entrySet()) with stats.entrySet()
    #62 logger.info("Writing [{}] to graphite", msg); with logger.info
    please give some idea to fix this :)

    ReplyDelete
    Replies
    1. this code was just for a sample, I think I used slf4j wrapper that uses {} syntax. please change the code to use

      logger.info("Writing ["+msg +"] to graphite");

      and it should work fine.

      Delete
  5. That seems to have fixed the issue for the logger but I am also still getting the same issue Dhanushanth was getting on Line #53

    "
    Multiple markers at this line
    Map.Entry is a raw type. References to generic type Map.Entry should be parameterized
    Type mismatch: cannot convert from element type Object to Map.Entry
    "


    ReplyDelete
  6. I updated the imports (sorry I was using a different logger and I wanted to make the code simple). Anyways I converted the code to use slf4j so try now. or you can switch it to use your logger and replace the loging code or remove it.

    ReplyDelete

Post a Comment

Popular posts from this blog

RabbitMQ java clients for beginners

Here is a sample of a consumer and producer example for RabbitMQ. The steps are
Download ErlangDownload Rabbit MQ ServerDownload Rabbit MQ Java client jarsCompile and run the below two class and you are done.
This sample create a Durable Exchange, Queue and a Message. You will have to start the consumer first before you start the for the first time.

For more information on AMQP, Exchanges, Queues, read this excellent tutorial
http://blogs.digitar.com/jjww/2009/01/rabbits-and-warrens/

+++++++++++++++++RabbitMQProducer.java+++++++++++++++++++++++++++
import com.rabbitmq.client.Connection; import com.rabbitmq.client.Channel; import com.rabbitmq.client.*; public class RabbitMQProducer { public static void main(String []args) throws Exception { ConnectionFactory factory = new ConnectionFactory(); factory.setUsername("guest"); factory.setPassword("guest"); factory.setVirtualHost("/"); factory.setHost("127.0.0.1"); factory.setPort(5672); Conne…

What a rocky start to labor day weekend

Woke up by earthquake at 7:00 AM in morning and then couldn't get to sleep. I took a bath, made my tea and started checking emails and saw that after last night deployment three storage node out of 100s of nodes were running into Full GC. What was special about the 3 nodes was that each one was in a different Data centre but it was named same app02.  This got me curious I asked the node to be taken out of rotation and take a heap dump.  Yesterday night a new release has happened and I had upgraded spymemcached library version as new relic now natively supports instrumentation on it so it was a suspect. And the hunch was a bullseye, the heap dump clearly showed it taking 1.3G and full GCs were taking 6 sec but not claiming anything.



I have a quartz job in each jvm that takes a thread dump every 5 minutes and saves last 300 of them, checking few of them quickly showed a common thread among all 3 data centres. It seems there was a long running job that was trying to replicate pending…