You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In some environments, someone may want to check what CPU architecture the system is running on so as to be able to perform preflight checks before deployments e.g an application that's not built for ARM may have a preflight failure for arm64 architecture
Extend the analyser to allow checking machineArch values like so
hostAnalyzers:
- cpu:
checkName: "Check machine architecture"outcomes:
- fail:
when: "machineArch != x86_64"message: This server is not x86_64
- fail:
when: "machineArch == amd64"message: This server is amd64
Add Info.MachineArch template to allow crafting outcome messages such as {{ Info.MachineArch }} machine architecture is not supported
Describe alternatives you've considered
One can use a combination of run collector and regex analyser like so to achieve the same result. The message template bit would be missing though
Describe the rationale for the suggested feature.
In some environments, someone may want to check what CPU architecture the system is running on so as to be able to perform preflight checks before deployments e.g an application that's not built for ARM may have a preflight failure for
arm64
architectureDescribe the feature
Extent https://troubleshoot.sh/docs/host-collect-analyze/cpu/ host collector/analyser
KernelArch
value from https://pkg.go.dev/github.com/shirou/gopsutil/[email protected]/host#InfoStat and store in a newmachineArch
field. This value will be the output ofuname -m
machineArch
values like soInfo.MachineArch
template to allow crafting outcome messages such as{{ Info.MachineArch }} machine architecture is not supported
Describe alternatives you've considered
One can use a combination of run collector and regex analyser like so to achieve the same result. The message template bit would be missing though
The text was updated successfully, but these errors were encountered: