Hi,
For the past weeks we've been having some issues with this and and couln't manage to make it work. It looked like the app was trying to create a checkpointer object using Splunk's solnlib library but failed every time making it impossible to store and retrieve checkpoints as well as access tokens.
And if you try to create the lookup manually, either using the API or the lookup editing app, it also fails with an error:
After getting in touch with Splunk's support team, they've told us that the issue comes from the app configuration, which is missing some .conf files, which should be quite easy to fix.
Here's their reponse regarding the issue:
I want to inform you that the issue is caused by a packaging defect in the Cisco Webex Add-on for Splunk versions 1.4.1 and 1.4.2. This is not a problem with Splunk Cloud, KV Store, the search head, or MongoDB. Specifically, the add-on package is missing several critical configuration files required for KV Store operations. These include the absence of a collections.conf file defining the collection schema, a transforms.conf file for necessary lookups, and appropriate ACL entries in the metadata/default.meta file. Additionally, the default/app.conf file has the [install] is_configured setting set to false.
The add-on depends entirely on dynamically creating the ta_cisco_webex_add_on_for_splunk_checkpointer collection at runtime using the solnlib library’s get_collection_data() function during the first run. However, because there is no shipped collection schema, no transforms definition, no [collections] ACL, and the app is marked as not configured, the REST POST request to create the collection is rejected with an HTTP 500 error. The earlier HTTP 404 error on GET is expected since the collection does not exist yet. The 500 error on POST results from the missing package declarations that prevent runtime configuration writes within the add-on’s namespace on Splunk Cloud.
The subsequent Python error (TypeError: cannot unpack non-iterable NoneType object) is a downstream symptom caused by the failure to create the collection.
We have confirmed that the Splunk Cloud platform and KV Store are healthy. The KV Store status on your search head is ready, MongoDB logs show no errors, and other apps with proper configuration files can create collections successfully. The failure occurs only when creating collections within the Webex add-on’s app namespace, confirming the problem is isolated to the add-on’s packaging and configuration.
While it is technically possible to manually add a collections.conf file and repackage the add-on as a workaround, this approach is not recommended. Manual modifications may be overwritten by future upgrades, could cause conflicts or unsupported states, and would limit support options.
The recommended path forward is to contact the Cisco team responsible for the Webex Add-on for Splunk via the Splunkbase listing or directly. Request that the next add-on release includes a proper collections.conf defining the ta_cisco_webex_add_on_for_splunk_checkpointer collection schema, a transforms.conf file with necessary lookup definitions, updated ACL entries in metadata/default.meta, and a review of the [install] is_configured setting and setup flow.
Do you think you could fix it and include thos files in a future release?
Hi,
For the past weeks we've been having some issues with this and and couln't manage to make it work. It looked like the app was trying to create a checkpointer object using Splunk's solnlib library but failed every time making it impossible to store and retrieve checkpoints as well as access tokens.
And if you try to create the lookup manually, either using the API or the lookup editing app, it also fails with an error:
After getting in touch with Splunk's support team, they've told us that the issue comes from the app configuration, which is missing some
.conffiles, which should be quite easy to fix.Here's their reponse regarding the issue:
Do you think you could fix it and include thos files in a future release?