https://github.com/dmuth/mac-osx-ram-usage
Uses Splunk and Docker to get a real-time look at OS/X Ram Usage
https://github.com/dmuth/mac-osx-ram-usage
Last synced: 11 months ago
JSON representation
Uses Splunk and Docker to get a real-time look at OS/X Ram Usage
- Host: GitHub
- URL: https://github.com/dmuth/mac-osx-ram-usage
- Owner: dmuth
- License: gpl-3.0
- Created: 2019-03-27T01:58:16.000Z (about 7 years ago)
- Default Branch: main
- Last Pushed: 2020-09-03T22:21:53.000Z (almost 6 years ago)
- Last Synced: 2025-04-12T14:51:27.882Z (about 1 year ago)
- Language: Shell
- Size: 307 KB
- Stars: 2
- Watchers: 2
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# Mac OS/X RAM Usage
This app lets you graph RAM usage of applications on your Mac. It was built
and tested on Mac OS/X 10.13.6.
## Screenshots
## Requirements
- Python 3
- Docker
## Installaton
- Clone this repo
- Run `pip3 install -r ./requirements.txt` to install the necessary Python modules
## Usage
- Run `sudo ./get-ram-loop.sh` in one shell to start fetching RAM usage in logs.
- You will be prompted for your password--this is normal so that the script can sudo to root.
- If you want to run without `sudo`, that is fine, but you will get stats only on your processes.
- Run `start-splunk.sh` to start up Splunk.
- You will be presented with a list of how Splunk is configured. If you're happy, press ENTER, if not, press ctrl-C and adjust your environment variables.
Once Splunk is started, it will spin up an instance of
Splunk Lab and then run Splunk.
If you already have Splunk Lab, this will take about 10 seconds, if not, it could take
a minute or more for the Docker container to be downloaded.
Once started, the Splunk instance can be accessed at https://localhost:8000/, unless
you chose a different port.
## How It Works
I wrote a version of PS in Python called **Better PS**, and it uses the
PSUtil module to query the process list
and extract important process attributes and then print them up in a format that Splunk
can parse natively. This is far FAR saner than trying to parse the output of `ps`.
## Why are you using SSL for talking to localhost?
Why are you not?
## Credits
## Contact
Feel free to hit me up on ,
Facebook,
or via email if you
would like to get in touch.