Troubleshooting snmpv3 in sc4snmp

[LarsFromMars]

Hi could i have some pointers in troubleshooting snmpv3
I have configured switches with v3 - I can snmpwalk, snmpget etc successfully using the net-snmp cmds from the sc4snmp host - so my credentials and connectivity are good we are using AuthPriv
When i add those same credentials to a secretname as per : https://splunk.github.io/splunk-connect-for-snmp/main/configuration/snmpv3-configuration/ nothing seems to happen.
I also don't know where to look to troubleshoot - so far i have:

• checked the inventory is updated
  microk8s kubectl logs -f snmp-splunk-connect-for-snmp-inventory-XXXX -n sc4snmp
• looked at all the worker poller logs in splunk but i cannot find anything interesting pertaining to anything successfully or not successfully polled
• tried variations of configurations with the secrets in "" and '' (no special characters used in the secrets)
• confirmed the engine id is correct by polling the engine id oid (tried with and without)

Any other pointers? is there a kubectrl command that shows what the secretname looks like? or any logs showing whether the worker-pollers are trying to poll the device?

[omrozowicz-splunk]

The thread here was led mainly on slack, but in order to not leave this question without response here I'll copy paste here how to check if there are correct data in k8s secret.

1. Check if you have secret in microk8s kubectl get secret -n sc4snmp
2. Describe it: microk8s kubectl describe secret/my-test-secret -n sc4snmp
3. Decode it according to instruction: https://stackoverflow.com/questions/56909180/decoding-kubernetes-secret

We'll plan the task to update the docs with a whole procedure of traps v3 troubleshooting.