Skip to main content

Improving the new relic handler to push api input and output Parameters

In previous post I described how to publish API traffic to new relic[1]. I have done some modifications to the handler to cater $subject. You will need to change the code to match your exact requirements. And I did some improvements to the code as well. Please find my modified code attachment[2].

I have added following code segments to the handler let me describe of each segment.

Following segment is to build message when POST type is used. Otherwise inside handler we will get an empty envelop.

 try {  
   RelayUtils.buildMessage(((Axis2MessageContext)messageContext).getAxis2MessageContext());  
 } catch (Exception e) {  
   log.warn("Error occured while building message");  
   if(log.isDebugEnabled()){  
     log.debug("Exception thrown while building message", e);  
   }  
 }

Here I push data to new relic, each parameter as a different column. So please change the code as it match your requirement.

Following code segment will extract post data from the request. But this to work properly you will need to set content-type in requests and also backend responses.

 try {  
   OMElement bodyFirstElement = messageContext.getEnvelope().getBody().getFirstElement();  
   if (bodyFirstElement != null) {  
     Iterator iterator = bodyFirstElement.getChildElements();  
     while (iterator.hasNext()) {  
       OMElement element = iterator.next();  
       eventAttributes.put(element.getLocalName(), element.getText());  
     }  
   }   
 } catch (Exception e){  
   log.warn("Error occured while extracting data form the request, hense ignoring");  
   if(log.isDebugEnabled()){  
     log.debug("Exception thrown while extracting data from request", e);  
   }  
 }

Following code segment will capture the query params you provide the api.

 try {  
   Object urlPostfix = ((Axis2MessageContext) messageContext).getAxis2MessageContext().getProperty("REST_URL_POSTFIX");  
   else if (urlPostfix != null) {  
     String[] urlParts = urlPostfix.toString().split("\\?");  
     if (urlParts.length > 0) {  
       String queryParamString = urlParts[1];  
       String[] pairs = queryParamString.split("&");  
       for (String pair : pairs) {  
         String[] keyValues = pair.split("=");  
         if (keyValues.length > 0) {  
           eventAttributes.put(keyValues[0], keyValues[1]);  
         } else {  
           eventAttributes.put(keyValues[0], "");  
         }  
       }  
     }  
   }  
 } catch (Exception e){  
   log.warn("Error occured while extracting data form the request, hense ignoring");  
   if(log.isDebugEnabled()){  
     log.debug("Exception thrown while extracting data from request", e);  
   }  
 }

Good Luck!!! :)

References

Labels:

Comments

Post a Comment

Popular posts from this blog

Generate JWT access tokens from WSO2 Identity Server

In Identity Server 5.2.0 we have created an interface to generate access tokens. Using that we have developed a sample to generate JWT tokens. You can find that sample under msf4j samples[1][2]. If you are build it as it is you will need to use Java 8 to build since msf4j is developed on Java 8. So you will need to run Identity Server on Java 8 as well. After building the project[2] please copy the jar inside target directory to $IS_HOME/repository/components/dropins/ directory. And then please add the following configuration to Identity.xml which is placed under $IS_HOME/repository/conf/identity/ folder inside tag OAuth . <IdentityOAuthTokenGenerator>com.wso2.jwt.token.builder.JWTAccessTokenBuilder</IdentityOAuthTokenGenerator> Then go to the database you used to store oauth tokens (This is the database pointed from the datasource you mentioned in the $IS_HOME/repository/conf/identity/identity.xml) and then alter the size of the column ACCESS_TOKEN of the tab
6 comments
Read more

Oauth custom basic authenticator with WSO2 IS 5.1.0

WSO2 Identity Server supports Oauth2 authorization code grant type with basic authentication OOTB. But basic authentication is done only with WSO2 user store. So there could be use cases that basic authentication has to be done against some other system. In this case you follow below steps to achieve your requirement. First you need to create an class which extends AbstractApplicationAuthenticator and implements LocalApplicationAuthenticator. Because this class is going to act as your application authenticator so it needs to be an implementation of application authenticator interface and to achieve this it needs to be a local authenticator as well. [2] public class CustomBasicAuthenticator extends AbstractApplicationAuthenticator implements LocalApplicationAuthenticator {   Then you need to override the initiateAuthenticationRequest method so you can redirect to the page to enter user and password. In my sample I redirected to the page that is used by our default basic au
Post a Comment
Read more

Installing gluster in AWS EKS

This article is a continuance of [1] . Purpose of this article is to document the steps, issues and solutions to those issues we have to face when installing gluster in EKS (Elastic Kubernetes Service). For gluster we need a disk to be attached with the K8s node. In EKS easiest way of implementing this is, adding it to the node configuration. So every time a node comes up, it comes up with a disk attached to the defined path. You can use this path in the topology.josn as mentioned in [1] . Next step is to install gluster using the gk-deploy script. The challenge comes here after. To use gluster in pods, you need to define a storage class. The heketi url mentioned in the storage class definition, should be accessible from master node. But the given heketi url is a cluster IP type k8s service. But in EKS deployments masters are managed by AWS and master don't have access to cluster IPs. So how we can solve this? Actually I tried to contact AWS support on this and I didn't got
Post a Comment
Read more