Warning

Tase is well-tested on limited environments but not battle-tested fully.

Tase

Table of Contents

• Tase
  • Table of Contents
  • What is Tase?
  • Features
  • Installation
  • CLI Arguments
  • Configuration Reference
    • Configuration File Structure
      • 1. Configs (configs)
      • 2. Action Strategies
        • Truncate Strategy
        • Rotate Strategy
        • Delete Strategy
      • 3. Agents Configuration
      • 4. Server Configuration
  • Example Configuration
  • License
  • Contributing
  • Roadmap
  • Author

What is Tase?

Tase is a lightweight log management system written in Zig. It consists of a daemon running on a master server and lightweight agents deployed across multiple servers. With a single config.yaml, Tase allows centralized control over log file management, including deletion, rotation, and truncation.

Features

1. Master-Agent Architecture: The master server manages configurations and schedules, while agents execute log management tasks.
2. YAML-Based Configuration: The master server reads a config.yaml file to determine agent behavior and scheduling.
3. Cron-based Scheduling: The application uses cron-based scheduling to execute the log management tasks at predefined intervals.
4. Delete Logs: The application can delete log files that are older than a specified number of days or exceed a certain size.
5. Rotate Logs: The application can rotate log files, optionally compressing the archived files using the GZip algorithm. It can also delete archived logs older than a specified number of days or size same as delete action.
6. Truncate Logs: The application can truncate log files that are older than a specified number of days or exceed a certain size.

Installation

Tase is written in Zig, and to build and install it, follow these steps:

# Clone the repository
git clone https://github.com/Gnyblast/tase.git
cd tase

# Build the application
zig build

# Run the master daemon
zig-out/bin/tase -m master -c /path/to/config.yml

# Run the agent daemon on other servers that can communicate with master server
zig-out/bin/tase --agent --secret <a-generated-secret-that-matches-to-config> --port 7423 --master-host localhost --master-port 7423

CLI Arguments

Argument	Type	Description	Default	Required
--log-dir	string	Directory for tase self logs	/var/log/tase	No
--log-level	string	Logging level (debug, info, warn, error)	info	No
--master	bool	For server type master	-	Either --master or --agent required
--agent	bool	For server type agent	-	Either --master or --agent required
--config	string	absolute path for configuration file	/etc/tase/app.yaml	No
--secret	string	Agents only - Secret for master/agent communication (JWT secret)	-	Yes - Only for --agent
--host	string	Agent Server host address (Only for agents)	127.0.0.1	No
--port	string	Agent Server port (Only for agents)	7423	No
--server-type	string	Agent Server type, only tcp atm (Only for agents)	tcp	No
--master-host	string	Host address of the master for agent to connect (Only for agents)	-	Yes
--mastger-port	string	Port address of the master for agent to connect (Only for agents)	-	Yes
--help	bool	Print help menu	-	No

Configuration Reference

Configuration File Structure

The application uses a YAML configuration file with the following main sections:

1. Configs (configs)

Each config defines a log management task with the following properties:

Property	Type	Description	Default	Required
app_name	string	Name of the application	-	Yes
logs_dir	string	Directory containing log files	-	Yes
log_files_regexp	string	Regular expression to match log files. Always use single quotes ' because of Library Limitations	-	Yes
cron_expression	string	Cron schedule for the log management task	-	Yes
run_agent_names	string[]	List of agents to run this task ("local" is a reserved word to run against master server itself)	-	Yes
action	object	Log management strategy details	-	Yes

2. Action Strategies

The action object supports three strategies:

Truncate Strategy

Property	Type	Description	Default	Required
strategy	string	Must be "truncate"	-	Yes
truncate_settings.from	string	Truncate from top or bottom ("top" or "bottom")	-	Yes
truncate_settings.lines	int	Truncate by lines (it's mutually exclusive with "size")	-	Either "lines" or "size"
truncate_settings.size	int	Truncate by size in MB (it's mutually exclusive with "lines")	-	Either "lines" or "size"
truncate_settings.action	string	Keep or Delete matching truncate_settings ("delete" or "keep")	-	Yes
if.condition	string	Condition type ("days" or "size" in MB)	-	Yes
if.operator	string	Comparison operator ("gt", "lt", "eq")	-	Yes
if.operand	number	Threshold value	-	Yes

Rotate Strategy

Property	Type	Description	Default	Required
strategy	string	Must be "rotate"	-	Yes
rotate_archives_dir	string	Directory for archiving rotated files	same directory with log file	No
if.condition	string	Condition type ("days" or "size" in MB)	-	Yes
if.operator	string	Comparison operator ("gt", "lt", "eq")	-	Yes
if.operand	number	Threshold value	-	Yes
keep_archive.condition	string	Condition type ("days" or "size" in MB)	-	Yes if keep_archive is defined
keep_archive.operator	string	Comparison operator ("gt", "lt", "eq")	-	Yes if keep_archive is defined
keep_archive.operand	number	Threshold value	-	Yes if keep_archive is defined
compress	string	Compression algorithm ("gzip")	-	No
compression_level	number	Compression level (4-9)	4	No

Delete Strategy

Property	Type	Description	Default	Required
strategy	string	Must be "delete"	-	Yes
if.condition	string	Condition type ("days" or "size" in MB)	-	Yes
if.operator	string	Comparison operator ("gt", "lt", "eq")	-	Yes
if.operand	number	Threshold value	-	Yes

3. Agents Configuration

Property	Type	Description	Default	Required
name	string	Agent name ("local" is reserved cannot be used)	-	Yes
hostname	string	Agent hostname	-	Yes
port	number	Agent port	-	Yes
secret	string	Authentication secret	-	Yes

4. Server Configuration

Property	Type	Description	Default	Required
host	string	Server hostname	"127.0.0.1"	No
port	number	Server port	7423	No
type	string	Server type	"tcp"	No
time_zone	string	Server time zone	"UTC"	No

Example Configuration

server:
  host: "127.0.0.1"
  port: 7423
  time_zone: "UTC"

agents:
  - name: agent_1
    hostname: "192.xxx.xxx.xxx"
    port: 7423
    secret: "your-secret-key"

configs:
  - app_name: "rotate_logs"
    logs_dir: "/var/log/myapp"
    log_files_regexp: 'test\.log'
    cron_expression: "0 0 * * *"
    run_agent_names:
      - agent_1
    action:
      strategy: rotate
      if:
        condition: days
        operator: "gt"
        operand: 7
      compression_type: gzip
      compression_level: 5

  - app_name: "delete_logs"
    logs_dir: "/var/log/myapp2"
    log_files_regexp: 'test\.log'
    cron_expression: "30 08 * * 7"
    run_agent_names:
      - agent_1
      - local
    action:
      strategy: delete
      if:
        condition: size
        operator: "gt"
        operand: 20

  - app_name: "truncate_by_lines_delete_top"
    logs_dir: "/var/log/myapp3"
    log_files_regexp: 'test\.log'
    cron_expression: "30 09 * * 1"
    run_agent_names:
      - agent_1
    action:
      strategy: truncate
      if:
        condition: days
        operator: "gt"
        operand: 2
      truncate_settings:
        action: "delete"
        from: "top"
        lines: 1000

For more example please see: config

Contributing

Contributions are welcome! Feel free to submit issues and pull requests on GitHub.

Please read Contiribution guide

Roadmap

Version 1.0.0

• Create a builder for different CPU architectures and OS and implement a released inside

Version 2.0.0

1. Log file monitoring
2. Parse and process monitored log files
3. Save processed log files to a database for future consumption by a UI application

License

This project is licensed under the MIT License.

Author

Developed by Gnyblast.