guilhemmarchand / TA-jira-service-desk-simple-addon

Atlasian JIRA add-on for Splunk alert actions
11 stars 9 forks source link

JSONDecodeError #120

Closed jackchankl closed 2 years ago

jackchankl commented 2 years ago

In all Splunk dashboard items, the below error is appeared: JSONDecodeError at “/data/splunk/lib/python3.7/json/decoder.py”, line 353: Expecting “,” delimiter: line 1 column 77 (char 76)

jackchankl commented 2 years ago

Here is relevant result of “splunk btool check —debug”:

Checking: /data/splunk/etc/apps/TA-jira-service-desk-simple-addon/local/ta_service_desk_simple_addon_account.conf Invalid key in stanza [JIRA] in /data/splunk/etc/apps/TA-jira-service-desk-simple-addon/local/ta_service_desk_simple_addon_account.conf, line 2: auth_type (value: basic). Invalid key in stanza [JIRA] in /data/splunk/etc/apps/TA-jira-service-desk-simple-addon/local/ta_service_desk_simple_addon_account.conf, line 3: jira_auth_mode (value: basic). Did you mean 'jira_ssl_certificate_path'? Did you mean 'jira_ssl_certificate_validation'? Did you mean 'jira_url'? Invalid key in stanza [JIRA] in /data/splunk/etc/apps/TA-jira-service-desk-simple-addon/local/ta_service_desk_simple_addon_account.conf, line 6: password (value: **). Invalid key in stanza [JIRA] in /data/splunk/etc/apps/TA-jira-service-desk-simple-addon/local/ta_service_desk_simple_addon_account.conf, line 7: username (value: xxxxxxxx).

jackchankl commented 2 years ago

Here is the config file which is configured automatically after configuration in the TA app:

[JIRA] auth_type = basic jira_auth_mode = basic jira_ssl_certificate_validation = 0 jira_url = x.x.x.x:x password = ** username = xxxxxxxx

guilhemmarchand commented 2 years ago

Hi @jackchankl

You issue means that the connectity to JIRA is not successful, which is Python is returning the message.

Please review: https://ta-jira-service-desk-simple-addon.readthedocs.io/en/latest/configuration.html#jira-account-configuration

If you are using the Cloud service: https://ta-jira-service-desk-simple-addon.readthedocs.io/en/latest/configuration.html#configuring-an-account-with-api-token-for-atlassian-cloud

If you are using an On premise JIRA: https://ta-jira-service-desk-simple-addon.readthedocs.io/en/latest/configuration.html#configuring-an-account-with-personal-access-token-for-jira-on-premise-pat

In both cases you test out the connectivity with a simple curl. Once you have properly configured the connectvity and if the connectivity is successful the issue will be fixed.

Regarding the btool messages, the Addon is build using the UCC librairies so I assume it's only because btool is not able to recognize the settings, however this is the proper way of building the Addons

jackchankl commented 2 years ago

Issue resolved, thank you

guilhemmarchand commented 2 years ago

Perfect, I am planning in a future version to have a builtin test of the connectivity at the setup time to avoid this.