It will be stored on our cloud storage system, and then (soon) you will be able to configure the dashboard to load your custom data, and display it in a chart etc. So when a job executes, and the returner is set to ‘cloud’ - the result is (today) uploaded to our cloud and stored - but you are unfortunately not yet able to retrieve it.
When setting up a job, you can set specific arguments to that job, but I don’t believe it’s possible to pass parameters to the returner - at least not via the --return_kwargs argument.
So you could go and add the necessary configuration fields to the minion config. Currently the minion config lives on the cloud, and is retrieved to the minion on startup, so it will overwrite any local changes.
But it may be possible to have custom sections of the minion config in the minion.d directory inside /etc/salt/minion, but this is solely a saltstack feature and is not yet managed and or supported by us.
You can actually fire events from the custom modules, but only events with a specific prefix are uploaded to the cloud.
But it’s a great idea to be able to fire custom events and show them in the events list. To be able to do so we are adding a custom prefix that people can use to create custom events.
To see an example of sending events, you can check out the core repository on github
Saltstack documentation about sending events.
We have a new release coming out monday (i hope) with a bunch of stuff - and the next thing I will start working on after the release, is being able to retrieve all custom data from the API, and show it in the configurable dashboard.
So we are talking weeks, not months before you will be able to retrieve the data in the API and configure the dashboard to show it in a chart.