Skip to content

Support

How to get help and support

First Aid

Quick troubleshooting when the Edge isn't working properly.

⚠️ Emergency Fix - Disable Interception:

If you suspect that the Edge is not working properly but don't have time to investigate, you should first disable all interception rules by adding a skip rule for all namespaces.

Add this rule:
rules:
  - name: "emergency-skip-all"
    action: skip
    scope:
      namespace: all

🚨 Complete Removal:

If disabling interception is not enough, you can remove Edge completely. It's still recommended to disable all interceptions first before removal.

Uninstall Edge:
helm uninstall auditty-edge -n auditty

✅ What Happens After Changes:

  • Disabling interception stops all log processing immediately
  • Logs will continue to flow normally without any Auditty modifications
  • Complete removal will delete all Auditty pods from the cluster
  • You can safely reinstall/reconfigure at any time

Contact Us

How to reach the Auditty support team for assistance.

📧 Email Support:

support@auditty.ai

We will respond as soon as possible.

💡 When Contacting Support:

  • Include your cluster information and Auditty version
  • Describe the issue and steps to reproduce
  • Include relevant pod logs if available
  • Mention if this is a POC or production environment

Common Issues

Pods Not Starting

Check the pod status and logs:

kubectl get pods -n auditty
kubectl logs -n auditty -l app.kubernetes.io/name=auditty-edge

Common causes: insufficient resources, RBAC issues, image pull errors

Logs Not Being Intercepted

Verify your rules are configured correctly:

kubectl get configmap auditty-config -n auditty -o yaml

Ensure intercept rules match your workload namespaces and names

High Resource Usage

Check resource consumption:

kubectl top pods -n auditty

If resource usage is high, consider reducing scope of intercept rules or increasing resource limits

Metrics Not Showing in Auditty

DaemonSet pods send metrics to Edge API, which batches and forwards them to Auditty (default flush interval: 5 minutes). Check the Edge API logs for delivery errors:

kubectl logs -n auditty -l app.kubernetes.io/name=auditty-edge-api | grep -i "hivemind\|error"

Check that hivemind_api_key is correct and network policies allow egress. If you run with edgeApi.enabled: false, check the DaemonSet pods (app.kubernetes.io/name=auditty-edge) instead — they send metrics directly.

License Expired

If the dashboard shows zero infrastructure or a license expiry banner, your Edge license has expired. Edge has a 3-day grace period after expiration — during this window it continues processing logs normally. After the grace period ends, Edge stops intercepting.

Contact support@auditty.ai to renew your license. After renewal, update the license in your ConfigMap/secret and restart Edge — the license monitor stops interceptors on expiry and does not automatically resume them:

kubectl rollout restart -n auditty daemonset/auditty-edge

Debugging Tips

View Edge Logs

kubectl logs -n auditty -l app.kubernetes.io/name=auditty-edge --tail=100 -f

Check Configuration

kubectl get configmap auditty-config -n auditty -o yaml

Verify RBAC

kubectl auth can-i get pods --as=system:serviceaccount:auditty:auditty-edge-api -n auditty

K8s API RBAC (pods, deployments, etc.) is granted to the Edge API service account, not the DaemonSet — the DaemonSet itself has no ClusterRole.

Check DaemonSet Status

kubectl get daemonset -n auditty
kubectl describe daemonset auditty-edge -n auditty

Frequently Asked Questions

Does Auditty Edge affect my application performance?

No. Edge processes logs asynchronously and does not add latency to your application. It operates at the node level, intercepting logs after they leave your containers.

Can I temporarily disable Auditty without uninstalling?

Yes. Add a skip rule for all namespaces (see Emergency Fix above). This stops all interception while keeping Edge running.

What happens if Edge crashes?

Your logs continue to flow normally. Edge is designed to fail safely - if it's not running, logs pass through unchanged to log files.

Can I customize resource limits?

Yes. Adjust the daemonSet.resources section in your values.yaml file during installation or upgrade.

How do I upgrade to a new version?

Use helm upgrade with the new version tag. Your configuration will be preserved.

helm upgrade auditty-edge oci://ghcr.io/auditty/helm-charts/auditty-edge --version <new-tag> -n auditty --values values.yaml

What happens when my license expires?

Edge has a 3-day grace period after license expiration. During this period, Edge continues processing logs normally. The dashboard will show a warning banner. After the grace period ends, Edge stops intercepting logs and your logs flow through unchanged. Contact support@auditty.ai to renew, then update the license in your ConfigMap/secret and restart Edge (kubectl rollout restart) — interception does not resume automatically.