Runtime Data Acquistion about silverback

[linear]

SBK-427 Runtime Signal Data Acquistion

[mikeshultz]

This all sounds good and seems pretty clear.

Only thing I wonder is if we should either error or otherwise handle other return types for backwards compatibility and flexibility. Like maybe we could coerce that return to the default key/tag/label in the wanted return type. For example:

if not is_dict_of_datapoints(return_value):
    return_value = {"default": BlobDatapoint(data=return_value)}

Then that would get ignored in the blackbox metrics displays but be available via the UI to the user. I still think blob returns could be powerful for users.

[fubuloubu]

This all sounds good and seems pretty clear.

Only thing I wonder is if we should either error or otherwise handle other return types for backwards compatibility and flexibility. Like maybe we could coerce that return to the default key/tag/label in the wanted return type. For example:

if not is_dict_of_datapoints(return_value):
    return_value = {"default": BlobDatapoint(data=return_value)}

Then that would get ignored in the blackbox metrics displays but be available via the UI to the user. I still think blob returns could be powerful for users.

Wanted to mention I'm doing a version of this, but only if it's a valid numeric type that we can actually display, not for any random return value type

My implementation so far is to support simple numeric datapoints, or you can subclass BaseDatapoint for a more powerful model type (we can serialize it for storage as <task_name>.<key_name> to pull for timeseries data)