Configuring Loggly Operations

To use the Loggly connector, add the <loggly.init> element in your configuration before carrying out any other Loggly operations. This API uses two types of authentication schemes: authentication via the customer token and basic HTTP access authentication.

Authentication via the customer token is required to execute the uploadLogFile and sendBulkLogs methods. For the rest of the methods, this connector uses basic HTTP access authentication, which uses the user credentials as shown below (user email and password). Click here for further reference on the authentication process.

init

<loggly.init>
	<apiUrl>{$ctx:apiUrl}</apiUrl>
	<username>{$ctx:username}</username>
	<password>{$ctx:password}</password>
</loggly.init>

Properties

username: The user name used for authentication.
apiUrl: The API URL.
password: The password used for authentication.

Additional information

Ensure that the following Axis2 configurations are added and enabled in the <ESB_HOME>\repository\conf\axis2\axis2.xml file.

Required message formatters

messageFormatters

<messageFormatter contentType="text/html" class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>
<messageFormatter contentType="multipart/form-data" class="org.wso2.carbon.relay.ExpandingMessageFormatter"/>

Required message builders

messageBuilders

<messageBuilder contentType="text/html" class="org.wso2.carbon.relay.BinaryRelayBuilder"/>
<messageBuilder contentType="multipart/form-data" class="org.wso2.carbon.relay.BinaryRelayBuilder"/>

Now that you have connected to Loggly, use the information in the following topics to perform various operations with the connector.

To ensure the security of the customer's sensitive data (e.g., user name and password), proxy services should only allow HTTPS access to ensure transport-level security. The transports property in the <proxy> element in your ESB configuration restricts the access to HTTPS only (<proxy transports="https"/>).