Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create support bundle for scans so we analysis issues #1011

Open
chris-rock opened this issue Dec 21, 2023 · 3 comments
Open

Create support bundle for scans so we analysis issues #1011

chris-rock opened this issue Dec 21, 2023 · 3 comments

Comments

@chris-rock
Copy link
Member

Issues we see right now with the current approach is that we need to always specify what we want to collect. It would be easier to have a flag that collects all the required data so that users can provide those to us for analysis.

This could be eg. cnspec scan --collect-support-bundle or similar. Other things we identified:

  • timestamps for debug logs
@jaym
Copy link
Contributor

jaym commented Jan 8, 2024

The things we have that I currently make use of are all spit out by DEBUG=1:

  • The asset bundle
  • inventory (resolved and unresolved)
  • the report
  • the resolved policy json
  • the resolved policy dot file as seen by the graph executor

Sometimes, its useful to be able to have a different profiles of the execution:

  • The heap profile
  • The cpu profile (its useful to be able to do this by wall clock time and real time)

@chris-rock
Copy link
Member Author

We should also include the version and the installed plugins

@chris-rock
Copy link
Member Author

chris-rock commented Feb 7, 2024

Would also be nice to include cnspec status details and to ensure the support bundle does not include any secrets in inventories.

@chris-rock chris-rock reopened this Feb 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants