A unique identifier, called a customer token, is used when sending logs to Loggly to ensure that the logs are sent to the right organization account. The customer token is an alpha-numeric string that needs to be included with each log event. You can use the same token for all of your logs. The token is used when you send log data to Loggly.
To access your Logs' customer tokens, select the Source Setup option in the side menu and click Customer Tokens.
The customer token must be provided within the Structured Data section of your syslog header. Here’s an example header:
The customer token must be provided within the URL of your request. Here’s an example:
For more information on sending log events over our API, check out our API docs.
Customer Tokens aren’t available within the search interface and should not be used to categorize logs. Instead, use Source Groups to categorize and organize logs from your infrastructure. However, customer tokens can be used to assign tokens to various groups of logs, e.g. public client-based log data vs. private syslog. Each organization must have at least one customer token active at any time and cannot have more than two active tokens.
To create a new token, from the Customer Tokens page click Add New, enter a description of the token, and click Save. A new token will be generated and can be used to send logs to Loggly. See Using a Customer Token or Logging Setup.
A customer token's description can be helpful to clarify the purpose of a token, when there are multiple tokens in use, but is not used or visible when setting up new sources. To edit the description, from the Customer Tokens page move your mouse to hover over the row containing your token and click the edit button at the end of the row, enter a description in the field provided, and click Save.
To copy the customer token to your clipboard so it can be easily pasted into your source configuration, from the Customer Tokens page click the copy button .
If a customer token has been compromised or otherwise misused, you can permanently retire a customer token to ensure it cannot be used again. Retired tokens are not removed from our system, but cannot be used again once retired.
Before you retire a token, make sure you have a second token already created. Each organization must have at least one customer token active at any time and cannot have more than two active tokens.
To retire a token, from the Customer Tokens page move your mouse to hover over the row containing your token and click the X at the end of the row and click Retire in the confirmation window. The token is moved to 'Retired' and, after a short delay, data with that token ID will no longer be accepted.
When the APM Integrated Experience is enabled, Loggly shares a common navigation and enhanced feature set with the other integrated experiences' products. How you navigate the product and access its features may vary from these instructions. For more information, go to the APM Integrated Experience documentation.