Skip to content

Diagnostic Information#

When reporting an issue, "it doesn't work" is rarely enough. The most useful reports include reproducible, specific information.

Collect this information first#

1. What you were doing#

For example:

  • Logging in
  • Adding a model
  • Running a threat intelligence lookup
  • Searching Splunk logs

2. The full error message#

Copy the complete error — do not truncate it.

3. Tool call card details#

If the issue involves a tool, expand the tool call card and record:

  • Tool name
  • Input parameters
  • The error message returned

4. Screenshots#

When taking screenshots, try to include:

  • The current page
  • The error dialog or error text
  • Relevant configuration fields (redact sensitive values)

Client logs#

For deeper investigation, you can provide the client log file.

macOS#

~/Library/Logs/AttackTrace/main.log

Windows#

%APPDATA%\AttackTrace\logs\main.log

Linux#

~/.config/AttackTrace/logs/main.log

Before submitting a report#

Confirm the following before filing:

  • Have you tested with a different model?
  • Have you narrowed the query scope?
  • Have you verified the API key or token has not expired?
  • Is only one specific tool affected, or are all tools failing?

Answering these questions first usually leads to faster resolution.