> ## Documentation Index
> Fetch the complete documentation index at: https://help.freakhosting.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to View the Activity Log

> Track every action on your FREAKHOSTING Game Panel account and servers using the activity log. Monitor file changes, power events, and admin operations.

## Know Exactly What Happened and When

The Activity Log is your account's complete audit trail. Every action you (or anyone with access to your account) take on the Game Panel is recorded here -- server starts and stops, file reads and writes, configuration changes, and more. It is the first place to check when something looks off, when you need to trace what happened before a crash, or when you want to verify that a teammate made the changes they said they did.

You will find it on the **Activity** tab at [games.freakhosting.com](https://games.freakhosting.com), accessible from the navigation bar on your Account page.

<CardGroup cols={2}>
  <Card title="Difficulty" icon="gauge-low">
    Beginner
  </Card>

  <Card title="Time" icon="clock">
    1 Minute
  </Card>
</CardGroup>

***

## Getting to the Activity Log

<Steps>
  <Step title="Log In to the Game Panel">
    Open your browser and go to [games.freakhosting.com](https://games.freakhosting.com). Enter your email and password, then click **Login**.
  </Step>

  <Step title="Open the Activity Tab">
    Click your **Account** link (with your avatar icon) in the **top-right corner**, then navigate to the **Activity** tab. This opens the full chronological activity log for your account.
  </Step>
</Steps>

***

## Reading the Activity Log

The Activity Log displays a chronological list of events, with the most recent actions at the top. Each entry contains several pieces of information that tell you exactly what happened, who did it, and when.

Here is what each part of an activity entry means:

<CardGroup cols={2}>
  <Card title="User Avatar and Name" icon="user">
    Each entry starts with a **purple avatar circle** showing the user's initials (for example, **FR**) followed by the **username** (for example, **freak0705**). This identifies who performed the action. If you are the only person with access, this will always be your account.
  </Card>

  <Card title="Event Type" icon="tag">
    Next to the username, you will see the **event type** in a structured format like `server:power.start`, `server:power.stop`, `server:file.read`, or `server:file.write`. This tells you the category and specific action that was logged.
  </Card>

  <Card title="Description" icon="align-left">
    Each entry includes a **human-readable description** of what happened. Instead of deciphering event codes, you can read plain text like "Started the server", "Killed the server process", or "Viewed the contents of /config.yml".
  </Card>

  <Card title="Location and Timestamp" icon="clock">
    On the right side of each entry, you will see a **country flag icon** indicating the geographic origin of the action, a **blurred IP address** for privacy, and a **relative timestamp** (for example, "29 days ago" or "1 month ago") showing when the event occurred.
  </Card>
</CardGroup>

***

## Common Event Types

The activity log tracks a wide range of actions. Here are the event types you will see most frequently:

### Power Events

| Event Type             | Description               | What It Means                                                                 |
| ---------------------- | ------------------------- | ----------------------------------------------------------------------------- |
| `server:power.start`   | Started the server        | Someone clicked Start or triggered a start via the API                        |
| `server:power.stop`    | Stopped the server        | A graceful shutdown was initiated                                             |
| `server:power.kill`    | Killed the server process | The server process was force-killed (used when a graceful stop does not work) |
| `server:power.restart` | Restarted the server      | A restart was triggered from the panel or API                                 |

### File Events

| Event Type           | Description                   | What It Means                                                                                                      |
| -------------------- | ----------------------------- | ------------------------------------------------------------------------------------------------------------------ |
| `server:file.read`   | Viewed the contents of a file | Someone opened a file in the File Manager -- for example, "Viewed the contents of //.ts3server\_license\_accepted" |
| `server:file.write`  | Wrote new content to a file   | A file was edited and saved -- for example, "Wrote new content to /.ts3server\_license\_accepted"                  |
| `server:file.delete` | Deleted a file                | A file was removed from the server                                                                                 |
| `server:file.upload` | Uploaded a file               | A file was uploaded through the File Manager                                                                       |

### Other Events

| Event Type                | Description               | What It Means                                           |
| ------------------------- | ------------------------- | ------------------------------------------------------- |
| `server:backup.start`     | Started a backup          | A backup was initiated either manually or by a schedule |
| `server:schedule.execute` | Executed a scheduled task | An automated task ran on schedule                       |
| `server:settings.rename`  | Renamed the server        | The server's display name was changed                   |
| `auth:login`              | Logged in                 | Someone successfully authenticated with your account    |

<Info>
  The activity log captures actions from both the web interface and API calls. If you use automation scripts with API keys, those actions will appear in the log too -- making it easy to verify your automations are running as expected.
</Info>

***

## Practical Uses for the Activity Log

The activity log is not just a record -- it is a troubleshooting and security tool. Here are real scenarios where it comes in handy:

| Scenario                                                       | How the Activity Log Helps                                                                                 |
| -------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- |
| Your server crashed and you want to know what led up to it     | Check for `server:file.write` events right before the crash -- a bad config edit is often the culprit      |
| You suspect unauthorized access to your account                | Look for `auth:login` events from unfamiliar IP addresses or countries                                     |
| A teammate says they restarted the server but it is still down | Verify whether a `server:power.start` or `server:power.restart` event actually occurred                    |
| You cannot remember which config file you edited yesterday     | Filter through `server:file.write` events to find the exact file path and timestamp                        |
| Your server settings changed and you did not change them       | Check for `server:settings.rename` or other settings events to see when and from where the change was made |
| An automated backup did not run                                | Look for the absence of `server:backup.start` events at the scheduled time                                 |

***

## Understanding the Location Data

Each activity entry includes geographic information about where the action originated:

* **Country flag icon** -- A small flag next to the entry indicates the country from which the action was performed. This is derived from the IP address.
* **Blurred IP address** -- The IP address is partially obscured in the interface for privacy. You can see enough to recognize whether it is your usual IP or something unfamiliar.

<Tip>
  If you see login events or power actions originating from a country you have never been to, that is a red flag. Change your password immediately and enable two-factor authentication if you have not already. Then check your email account for signs of compromise as well.
</Tip>

***

## Tips for Getting the Most Out of the Activity Log

<CardGroup cols={2}>
  <Card title="Check After Every Crash" icon="triangle-exclamation">
    The first thing to do after an unexpected crash is check the activity log. Look at the last few events before the server went offline -- a file edit, a plugin upload, or a forced restart can explain what went wrong.
  </Card>

  <Card title="Review After Shared Access" icon="users">
    If you have given subuser access to someone else, periodically review the activity log to see what actions they have performed. Trust but verify.
  </Card>

  <Card title="Verify Automation Runs" icon="robot">
    If you use schedules or API-driven automation, the activity log confirms that tasks actually executed. No guessing whether your 3 AM backup script ran or not.
  </Card>

  <Card title="Spot Patterns" icon="magnifying-glass-chart">
    If your server keeps crashing at the same time every day, cross-reference the activity log with the crash times. A scheduled task, automated restart, or recurring file write might be the cause.
  </Card>
</CardGroup>

***

<AccordionGroup>
  <Accordion title="How far back does the activity log go?">
    The activity log retains events for a significant period, but the exact retention window depends on the panel configuration. For most FREAKHOSTING accounts, you can expect several months of history. If you need logs beyond the available window, contact support.
  </Accordion>

  <Accordion title="Can I export or download the activity log?">
    The panel interface does not currently offer a direct export button for the activity log. However, if you need a copy of your activity history for security review or record-keeping, contact FREAKHOSTING support and they can assist.
  </Accordion>

  <Accordion title="Why is the IP address blurred?">
    IP addresses are partially masked in the activity log as a privacy measure. You can still see enough of the address to recognize your own IP or spot an unfamiliar one. If you need full IP details for a security investigation, contact support.
  </Accordion>

  <Accordion title="Do API key actions show up in the activity log?">
    Yes. Actions performed via API keys are logged just like actions performed through the web interface. This includes power commands, file operations, and any other API-driven changes.
  </Accordion>

  <Accordion title="Can subusers see the activity log?">
    Activity log visibility depends on the permissions assigned to the subuser. If they have access to the Account or Activity section, they can see the log. Check your subuser permission settings if you want to restrict this.
  </Accordion>

  <Accordion title="I see a login from an unfamiliar location -- what should I do?">
    Change your password immediately. Enable two-factor authentication if it is not already active. Check your email account for signs of compromise (password reset emails you did not request). Then open a support ticket with FREAKHOSTING so the team can investigate and help secure your account.
  </Accordion>
</AccordionGroup>

***

<Note>
  ### Need Extra Help?

  If you encounter any issues, our support team is ready to assist:

  * **Live Chat:** Quick assistance via our website.
  * **Support Ticket:** [Open a Ticket](https://freakhosting.com/clientarea/submitticket.php)
  * **Discord:** [Join our Community](https://discord.gg/freakhosting)
  * **Email:** [support@freakhosting.com](mailto:support@freakhosting.com)
</Note>

<Tip>
  ### Save on Your Hosting

  Ready to manage more game servers? Use code **KB20** at checkout for **20% off** your first month!
</Tip>

***

<div align="center">
  **Last Updated:** March 2026 | **Game Panel Support:** Activity tracking simplified.
</div>