Project Token Configuration
The project token connects your application to the ByteHide cloud platform. With a token, logs are automatically sent to the cloud. Without it, logs are only stored locally.
Setting the Project Token
Configure your project token using the setProjectToken method:
import com.bytehide.logs.core.Log;
// Set your project token
Log.setProjectToken("your-project-token-here");import com.bytehide.logs.core.Log;
// Set your project token
Log.setProjectToken("your-project-token-here");Using Environment Variables
The SDK can automatically load your project token from environment variables:
// Reads from BYTEHIDE_LOGS_TOKEN, BYTEHIDE_PROJECT_TOKEN, or PROJECT_TOKEN
Log.setProject();// Reads from BYTEHIDE_LOGS_TOKEN, BYTEHIDE_PROJECT_TOKEN, or PROJECT_TOKEN
Log.setProject();Obtaining Your Project Token
To get your project token, you first need to create a Logs project in the ByteHide dashboard.
Create Logs Project
If you haven't created a Logs project yet, follow our step-by-step guide: Create a Logs project
Once your project is created:
- Navigate to your Logs project dashboard
- Copy your project token from the project settings
- Use the token in your application configuration
Environment-Based Configuration
Using Environment Variables
// Get token from environment variable
String projectToken = System.getenv("BYTEHIDE_LOGS_TOKEN");
Log.setProjectToken(projectToken);// Get token from environment variable
String projectToken = System.getenv("BYTEHIDE_LOGS_TOKEN");
Log.setProjectToken(projectToken);Using System Properties
// Pass via -DBYTEHIDE_LOGS_TOKEN=your-token
String projectToken = System.getProperty("BYTEHIDE_LOGS_TOKEN");
if (projectToken != null) {
Log.setProjectToken(projectToken);
}// Pass via -DBYTEHIDE_LOGS_TOKEN=your-token
String projectToken = System.getProperty("BYTEHIDE_LOGS_TOKEN");
if (projectToken != null) {
Log.setProjectToken(projectToken);
}Spring Boot Configuration
In application.properties:
bytehide.logs.token=your-project-token-herebytehide.logs.token=your-project-token-hereIn your application:
@Value("${bytehide.logs.token}")
private String projectToken;
@PostConstruct
public void initLogger() {
Log.setProjectToken(projectToken);
}@Value("${bytehide.logs.token}")
private String projectToken;
@PostConstruct
public void initLogger() {
Log.setProjectToken(projectToken);
}Token Behavior
| Scenario | Behavior |
|---|---|
| Token Set | Logs sent to ByteHide cloud + local files (if enabled) |
| No Token | Logs only stored in local files |
| Invalid Token | Logs fallback to local files only |
Security Best Practices
Token Security
Never hardcode tokens in your source code. Use environment variables or a secrets management solution for maximum security.
Option 1: Environment Variables (Recommended)
// ❌ Don't do this
Log.setProjectToken("bh_1234567890abcdef");
// ✅ Do this instead
Log.setProjectToken(System.getenv("BYTEHIDE_LOGS_TOKEN"));// ❌ Don't do this
Log.setProjectToken("bh_1234567890abcdef");
// ✅ Do this instead
Log.setProjectToken(System.getenv("BYTEHIDE_LOGS_TOKEN"));Option 2: Automatic Environment Variable Loading
// ✅ Reads from BYTEHIDE_LOGS_TOKEN, BYTEHIDE_PROJECT_TOKEN, or PROJECT_TOKEN
Log.setProject();// ✅ Reads from BYTEHIDE_LOGS_TOKEN, BYTEHIDE_PROJECT_TOKEN, or PROJECT_TOKEN
Log.setProject();Validation
Check if your token is working:
Log.setProjectToken("your-token");
Log.info("Test log message");
// Check ByteHide dashboard to confirm logs are receivedLog.setProjectToken("your-token");
Log.info("Test log message");
// Check ByteHide dashboard to confirm logs are received