Chris Burroughs

My multicolins config is ``` multicollins { enabled = true instanceAssetType = DATA_CENTER locationAttribute = LOCATION thisInstance = IAD } ``` which is what worked until yesterday.

Yep, there is still an asset of type 'Data Center' with the tag `IAD`.

No I have not figured this out and I have not debugged further since `features.syslogAsset` workaround put out the fire.

I don't think the Dockerfile has a precedent for configuration like this. For example the port is just hard coded as `-Dhttp.port=9000``and that is relied upon by the`EXPOSE` statement.

I was thinking it would be an attribute of the Asset Type, but now that I look it doesn't seem that Asset Type's have attributes. Maybe they should? But that...

More magic from vendor kernels. Despite the version string starting with 2.6.32 it looks like the newer `kprobe='r:getnameprobe getname +0(+0($retval)):string'` is required.

RedHat kernels are an interesting area, it's hard to tell what's in them. Reported for the vendor kernel https://bugzilla.redhat.com/show_bug.cgi?id=1171943 (still private?) and appears to have been reported upstream in http://marc.info/?l=linux-kernel&m=140475133707722&w=2...

The gist in the original report is gone. What I see with current `master` is: ``` $ export TRITON_PROFILE=doesnotexist $ ./bin/triton ls triton: error (Config): no such profile: doesnotexist ```...

The linked tickets in 68e5b685832293bff25c888733c963dbcbe9ed6e for context on the current state of affairs.

Example prior art for the folder approach , very specific to CPython.