Creating MunkiReport Modules Part 5

28 January 2019 on macOS and MunkiReport. 8 minutes

Processing the Data

If you have been following along with the tutorial, we should now have a module installed on a client that is pushing data to our server. Now we need to make sure that the server is ready to do something with the data. Our primary focus in this article will be on awesome_model.php, which is unsurprisingly the model component of the MVC framework, which will manage the data of the module. But before we get to the model, we need to first make sure that we have a table in the database to put it.

Creating the Table - (Migration)

While earlier versions of MunkiReport created the table within the model, the current version creates tables via a database migration which utilizes the Laravel migration framework. When we initially created the module from the template, a migrations folder and file was created. The file will look like this:

use Illuminate\Database\Schema\Blueprint;
use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Capsule\Manager as Capsule;

class AwesomeInit extends Migration
    public function up()
        $capsule = new Capsule();
        $capsule::schema()->create('awesome', function (Blueprint $table) {


    public function down()
        $capsule = new Capsule();

Luckily, the file contains the majority of what we need for a successful migration. We just need to correct the names and types of data that we would like to have in our table.

The first field is the id field which we can just leave alone.

The second is the serial_number, which is most likely going to be used to join different tables together. The decision must be made whether there will be one record per machine, or if there will be many records for each machine. If you have many records, make sure to take out the unique constraint. In our example, we may have many launch daemons, so we need to remove it so that it is simply $table->string('serial_number');.

We then need to create the rest of our fields and assign them the proper type based on the values that will be stored in them.


You are also able to define indexes for the table. Indexes speed up queries, but result in slower writes. MySQL can have up to 64 indexed columns. You cannot index big integers or text or blobs. Generally only the fields that are used in widgets or listings should be indexed, if they can be. (thanks to tuxudo and bochoven for this information!)

If the table needs to be altered in the future (new/remove field, change names, change type, etc.), a new migration must be created. More instructions concerning this can be found on the MunkiReport wiki.

Understanding the Model

Now let’s turn our attention toward the model and take a look at the file that was generated for us. Ignoring the comments and the actual functions, we get the following:


use munkireport\models\MRModel as Eloquent;

class awesome_model extends Eloquent
    protected $table = 'awesome';

    protected $fillable = [

    public $timestamps = false;


Creating a New Class

The first thing this file does is extends the Model class by creating the awesome_model class. We will change the lowercase a to uppercase A to follow the PSR-0 Style Guide. There is no style police for the project, but we want the code to look similar, so be polite and check out other modules or simply ask.

class Awesome_model extends Eloquent

Defining Models

MunkiReport has recently changed to the Eloquent model. In this model a table is defined with protected $table = 'awesome'; which has been created for us. After that, the $fillable array tells us what items in the table can be mass-assigned.

    protected $fillable = [

    public $timestamps = false;


The processor will vary a bit more based on what kind of data is sent in the postflight. The basic concept is that you need to read the data in, replace (or write more data) and save it back to the table.


use munkireport\processors\Processor;

class Awesome_processor extends Processor
    public function run($data)
        $modelData = ['serial_number' => $this->serial_number];

		// Parse data
        $sep = ' = ';
		foreach(explode(PHP_EOL, $data) as $line) {
                list($key, $val) = explode($sep, $line);
                $modelData[$key] = $val;
		} //end foreach explode lines

            ['serial_number' => $this->serial_number], $modelData

        return $this;


You may run into issue with trying to get the correct data in the correct place.

Go back to the source

You are processing the data from the file we created in /usr/local/munkireport/scripts/cache/ so make sure that the data is there to begin with.


Remember that MunkiReport caches the data and only sends if the data has changed. If you make changes and want to try sending again, the hash of the file must change, so be sure to alter the data (manually if needed) and then run the following command to send it:

sudo /usr/local/munkireport/munkireport-runner


If you have print statements in the model, they should print out during the postflight run.


Because we have not created to view the data at this point, make sure that you are comfortable returning data from the database whether that be from the command line or a GUI application.


There is a lot of information here and it’s as much for me as it is for everyone else. Hope that this is helpful, and if any corrections are needed or questions arise, please let me know on Slack!

More in this Series


MunkiMDM Updates

I few months back I put together a little proof of concept utilizing the MicroMDM api to control UAMDM profiles with Munki by having Munki trigger the MDM profile install.