Updated

Author: syncmachineuser

.gitignore

@@ -0,0 +1,123 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+parts/
+sdist/
+var/
+wheels/
+pip-wheel-metadata/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+.python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/

README.md

@@ -1,30 +1,26 @@
-# spark_log_parser
-The **Spark log parser** parses unmodified Spark output logs.
+# log_parser
+The **Parser for Apache Spark** parses unmodified Apache Spark History Server Event logs.
 
-Parsed logs contain metadata pertaining to your Spark application execution. Particularly, the runtime for a task, the amount of data read & written, the amount of memory used, etc. These logs do not contain
-sensitive information such as the data that your Spark application is processing. Below is an example of the output of the log parser
-![Output of Log Parser](https://github.com/synccomputingcode/spark_log_parser/blob/main/docs/output.png)
+Parsed logs contain metadata pertaining to your Apache Spark application execution. Particularly, the runtime for a task, the amount of data read & written, the amount of memory used, etc. These logs do not contain
+sensitive information such as the data that your Apache Spark application is processing. Below is an example of the output of the log parser
+![Output of Log Parser](docs/output.png)
 
 # Installation
 Clone this repo to the desired directory.
 
 # Getting Started
-### Step 0: Generate the appropriate Apache Spark EMR log
-If you have not already done so, complete the [instructions](https://github.com/synccomputingcode/spark_log_parser/blob/main/docs/event_log_download.pdf) to download the spark event log.
+### Step 0: Generate the appropriate Apache Spark History Server Event log
+If you have not already done so, complete the [instructions](docs/event_log_download.pdf) to download the Apache Spark event log.
 
 ### Step 1: Parse the log to strip away sensitive information
 1. To process a log file, execute the parse.py script in the sync_parser folder, and provide a
 log file destination with the -d flag.
 
     `python3 sync_parser/parse.py -d [log file location]`
 
-    The parsed file `[log file name].spk` will appear in the sync_parser/results directory.
-    
-    To re-process and overwrite a previously generated parsed log add the -o flag:
+    The parsed file `parsed-[log file name]` will appear in the results directory.
 
-    `python3 sync_parser/parse.py -d [log file location] -o`
 
-3. Send Sync Computing the parsed log
+2. Send Sync Computing the parsed log
 
-    The parsed file `[log file name].spk` will appear in the sync_parser/results directory. Email
-your contact at Sync Computing the parsed file.
+Email Sync Computing (or upload to the Sync Auto-tuner) the parsed event log.