Log Group Console Guide

This page provides a complete guide to using the Log Group section of the Namirasoft Log Console. It walks you through how to create and manage Log Groups, which serve as containers for collecting and organizing logs from your own systems or from supported Namirasoft applications. Each Log Group includes configurable retention settings, giving you control over how long logs are stored before they are automatically removed.

What Is a Log Group?

A Log Group is a logical unit that stores logs associated with a particular application or system. You can assign a unique name and configure a custom retention period for each Log Group. Logs sent via the Namirasoft Log API or generated by Namirasoft apps are routed to the designated Log Group, where they can be accessed, filtered, and reviewed in context.

 

Log Groups are central to how Namirasoft Log organizes data and controls storage behavior. Each group’s retention policy determines the lifecycle of its logs, allowing you to align storage duration with compliance, cost-efficiency, or operational needs. Note that the free tier includes default retention limits (see the Pricing page for specific details).

Why Log Groups Matter

Log Groups give you a structured way to separate and manage logs across different sources or environments. This makes it easier to troubleshoot issues, monitor activity by project or system, and apply different retention policies based on your needs.

How Namirasoft Log Uses Log Groups

Whenever your systems or Namirasoft applications emit logs, they must specify a target Log Group. That group governs how the logs are stored, viewed, and retained.

 

Namirasoft Log also works seamlessly with some other Namirasoft apps. For example, Namirasoft Bill Watch can analyze logs from a Log Group and, depending on your configuration, forward critical events to Namirasoft Notification Sender. This allows logs to not only serve as a record but also power automated alerting and observability workflows.

Overview of Log Group Fields and Options

This section explains each field visible when creating or managing a Log Group in the Console. Understanding these options will help you create meaningful groupings, apply suitable retention periods, and integrate with supported Namirasoft apps or external systems effectively.

• ID (String): This is a unique identifier automatically assigned to each Log Group when it’s created. It cannot be changed manually and is used internally by the system to reference and manage that group.

• User ID (Namirasoft Account’s ID): This is the unique ID of the Namirasoft Account that created the Log Group. It ties the log activity to a specific user. The user ID is used for ownership tracking, permission control, and audit history across all Namirasoft apps.

• Workspace ID (Namirasoft Workspace’s ID): This refers to the workspace the Log Group belongs to. Workspaces are created using the Namirasoft Workspace app and are used to organize different teams, projects, or environments. Log Groups are always tied to a specific workspace, and workspace details (name and ID) are shown in the console.

• Name (String): A human-friendly label you choose to identify this Log Group. This name helps users recognize and organize their groups. It does not affect the system’s behavior, it’s only used for identification and display.

• Retention Unit (Enum): It specifies the time unit that determines how long logs should be stored. Combined with Retention Value, this defines the full retention duration of the group. For example: “Week” with a value of 5 means logs will be stored for 5 weeks.

• Retention Value (Integer): The numerical value that determines how many units of time logs are retained. For example, if Retention Unit is “Day” and this value is 10, logs are kept for 10 days before being removed automatically.

• Show Logs (Action): This options displays all log entries recorded under a selected Log Group, including the time, severity level, and message for each event. This allows users to review activity and track system behavior in real time or historically.

• Created At (DateTime): The exact time when the Log Group was initially created. This timestamp is recorded and is useful for tracking and auditing.

• Updated At (DateTime): The most recent time the Log Group’s settings (such as name, retention, or tags) were changed.