Identification of Actors in a Logger System

Application Developer

• The person who integrates and uses the logger within the application code.
• Responsibilities:

• • • Instantiates logger instances.

    • Calls logging methods like logInfo(), logError(), etc.

    • Configures log levels, formats, and outputs.

System Administrator (or DevOps Engineer)

• The person responsible for configuring the logging system in production.
• Responsibilities:

• • • Sets up log file paths and rotation policies.

    • Monitors log storage and archival.

    • Adjusts runtime log levels for troubleshooting.

Logger System (Internal Actor)

• The component or service that processes and handles logging requests.
• Responsibilities:

• • • Formats log messages.

    • Filters based on log levels.

    • Sends logs to appropriate destinations like files or consoles.

External Systems (Optional Actor)

• Third-party tools or systems that consume or process logs.
• Examples:

• • • Monitoring systems (e.g., ELK Stack, Prometheus).

    • Cloud logging services.

    • Remote log aggregators.

Explanation to Students

• Emphasize the distinction between human actors (Developer, Admin) and system actors (Logger System, External Tools).
• Explain that each actor has specific interactions with the Logger, and these interactions help define system behavior and interfaces.
• Discuss how these actors influence design decisions such as configurability, usability, and scalability.