Python Extensions 2.0 with NO required configuration? (i.e. activationSchema.json Documentation?)

[Joseph_Hobbs]

Does anyone know if there is a detailed document around the activationSchema.json available?  I've reviewed a couple of examples (like those provided by the sdk itself) and I just can't seem to find one that handles the use case I'm after...

I'm in the process of putting together a Python-based Extension (2.0) to be deployed to a handful of our Linux-based hosts.  These hosts are running something I'd like to query for information that I will then roll up as metrics.  The issue is, I don't need any extra configuration for this to work beyond deploying it to the host.  I'm trying to figure out how to remove the default parts that control the configuration screen, but I can't seem to find the right combination of items to keep vs remove that will allow the schema to upload/work properly...

Thoughts/Examples?  Thanks!

[JamesKitson · Accepted solution]

I can't think of any existing examples of something like this because we typically always have some configuration, even if it is just the log level. I did a few quick tests and couldn't find anything that allows for a completely empty pythonLocal activation. It won't allow an activation object with no properties.

My recommendation would be to go with a bare minimum activation with perhaps just a toggle for debug logging that you can have off by default. This would be something to build off in the future as well in case you do come across scenarios that require some configurations.

[Joseph_Hobbs]

I came to the same conclusion in that 'something' has to be present.  Thanks for the info/insight!

[36Krazyfists]

Nice, I'll check it out.  Thanks!

[36Krazyfists]

Yeah, I've searched and searched and there is nothing comprehensive about the activationSchema.json file that I can find.  Kind of crazy considering how important this file seems to be.   Plus, it seems to have a lot of things you can maybe do with it, I think...  

[Joseph_Hobbs]

Yes, that's been my struggle as well.  I've been able to patch together something that works, but having a complete reference would be awesome.
I was lucky in finding an app that had a pretty comprehensive configuration associated with it at (https://www.dynatrace.com/hub/detail/remote-unix-monitoring-20/?query=linux+remote&filter=all#overvi...).  It has really helped me figure out some of the specific usage cases I was after.