This helps in identifying already recognized errors during testing. Known Issues: Familiarize yourself with previously reported issues in the Known Issues section.Filebeat Errors: If you encounter errors with Filebeat during testing, refer to this Slack discussion for insights and resolutions.Package Verification: Use the pre-release package that matches the current TAG you're testing.Multi-node Testing: For multi-node wazuh-manager tests, ensure agents are connected to both workers and the master node.Alerts: Every test should generate a minimum of one end-to-end alert, from the agent to the dashboard, irrespective of test type.External Accounts: If tests require third-party accounts (e.g., GitHub, Azure, AWS, GCP), request the necessary access through the CICD team here.For AWS access, coordinate with the CICD team through this link. Deployment Options: While deployments can be local (using VMs, Vagrant, or Docker) or on the aws-dev account, opt for local deployments when feasible.Test Requirements: Ensure your test comprehensively includes a full stack and agent/s deployment as per the Deployment requirements, detailing the machine OS, installed version, and revision.Be careful because some of the description steps might refer to a current version in production, always navigate using the current development documention for the stage under test. Documentation: Always consult the development documentation for the current stage tag at this link.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |