https://github.com/tidalmigrations/machine_stats

A simple and effective way to gather machine statistics (RAM, Storage, CPU, etc.) from a Windows or Unix server environment.
https://github.com/tidalmigrations/machine_stats

ansible cloud-migration gather-machine-statistics machine-stats tidal-migrations

Last synced: about 1 month ago
JSON representation

A simple and effective way to gather machine statistics (RAM, Storage, CPU, etc.) from a Windows or Unix server environment.

• Host: GitHub
• URL: https://github.com/tidalmigrations/machine_stats
• Owner: tidalmigrations
• License: mit
• Created: 2017-12-12T15:54:03.000Z (almost 7 years ago)
• Default Branch: master
• Last Pushed: 2024-05-21T05:20:12.000Z (6 months ago)
• Last Synced: 2024-05-21T06:35:01.153Z (6 months ago)
• Topics: ansible, cloud-migration, gather-machine-statistics, machine-stats, tidal-migrations
• Language: Python
• Homepage: https://pypi.org/project/machine-stats/
• Size: 16.4 MB
• Stars: 7
• Watchers: 7
• Forks: 1
• Open Issues: 15
• Metadata Files:
  • Readme: README.md
  • License: LICENSE
  • Security: SECURITY.md

Awesome Lists containing this project

README

        
# Machine Stats

A simple and effective way to gather machine statistics (RAM, Storage, CPU)

from a server environment as a first layer of a [Tidal discovery process](https://guides.tidal.cloud/).

Supports Windows and Unix-like platforms.

> _NB: For other platforms or custom integrations, see [the guides

> here](https://guides.tidal.cloud/sync-servers.html)._

## Overview

Getting an accurate view of your infrastructure needs is useful when planning a

cloud migration.  Most datacenter operations groups have a good view of their

overall storage utilization from various SAN and virtualization management

tools, but relying on these aggregated data points often causes teams to

underestimate the storage needs of their applications in the cloud.

When taking an _application-centric_ approach to cloud migration, getting the

resource utilization from each individual server gives you a more accurate view

of each application's resource requirements in the cloud and ignores the

trickery of thin-provisioning from SAN tools.  This allows you to confidently

plan data replication time, or other migration metrics on an app-by-app basis.

```

┌ Machine Stats ─────────────┐                           ╔═════════ TIDAL CLOUD ═════════╗

│                            │                           ║                               ║

│  CPU, RAM, Storage etc.    │                           ║  - Single Source of Truth     ║

│                            │   `tidal sync servers`    ║  - Server, Database, and      ║

│                            │──────────────────────────>║    Application Inventory      ║

│                            │                           ║                               ║

│                            │                           ║                               ║

└────────────────────────────┘                           ╚═══════════════════════════════╝

```

As your cloud migration will likely take place over many months or years, it's

important to have current resource requirements throughout your journey. To

accomplish this, setup `machine_stats` in a cron job or Scheduled Task and

synchronize your data on a _daily_ basis to Tidal. You can find more information

about it [here](https://guides.tidal.cloud/machine_stats.html#run-machine-stats-on-a-cron-job).

## Table of Contents

* [Machine Stats for Windows](/windows/README.md)

* [Machine Stats for Unix-like systems](/unix/README.md)