VCF Log Insight Health Check

Check the health, uptime, and node status of Aria Operations for Logs (Log Insight) in a VCF environment.

Security Scan

The skill's requests and runtime instructions align with its stated purpose (checking Log Insight health) and only require the expected CLI tools and an API token for the Log Insight host.

Purpose & Capability

Name, description, required binaries (curl, jq), and required environment variables (LOGINSIGHT_HOST, LOGINSIGHT_API_TOKEN) all match the stated purpose of querying Log Insight APIs. No unrelated credentials, binaries, or config paths are requested.

Instruction Scope

Instructions are narrowly scoped to two API calls (/api/v1/health and /api/v1/cluster/nodes) and summarizing results. A notable detail: curl is invoked with -k (insecure) which disables TLS certificate verification; this is sometimes necessary for appliances with self-signed certs but is a security risk (MITM exposure). The SKILL.md does not instruct reading other files or unrelated environment variables.

Install Mechanism

Instruction-only skill with no install spec and no code files — nothing is written to disk by an installer. This is the lowest-risk install model.

Credentials

Only LOGINSIGHT_HOST and LOGINSIGHT_API_TOKEN are required and the primary credential is the API token — these are appropriate and proportionate for querying the service. No unrelated secrets or broad credential access is requested.

Persistence & Privilege

Skill is not always-enabled and does not request persistent system privileges or modify other skills' configuration. It uses exec at runtime to call curl, which is expected for this purpose.

Assessment

This skill appears to do exactly what it says: run two Log Insight API calls and summarize results. Before installing: 1) Confirm the skill will run only in a trusted environment (it executes curl and will transmit your API token to LOGINSIGHT_HOST). 2) Avoid using a high-privilege API token; create a scoped token with minimum needed permissions and rotate/expire it. 3) If possible, avoid or justify the use of curl -k; prefer a valid TLS certificate on the Log Insight endpoint to prevent MITM risk. 4) Treat LOGINSIGHT_API_TOKEN as sensitive — do not paste it into chats or logs. 5) Verify the skill source (the GitHub homepage) if you need higher assurance about authorship. If you accept those caveats, the skill is coherent with its stated purpose.

When the user asks to check the health of the Log Insight or Aria Operations for Logs cluster, follow these steps:

1. Verify Credentials: Ensure LOGINSIGHT_HOST and LOGINSIGHT_API_TOKEN are available in the environment.
2. Fetch Cluster Health: Use the exec tool to run the following command to check the cluster status:

   curl -s -k -X GET "https://$LOGINSIGHT_HOST/api/v1/health" \
     -H "Authorization: Bearer $LOGINSIGHT_API_TOKEN" \
     -H "Accept: application/json" | jq '.'
   

3. Fetch Node Status: Use the exec tool to run the following command to check individual node uptime and status:

   curl -s -k -X GET "https://$LOGINSIGHT_HOST/api/v1/cluster/nodes" \
     -H "Authorization: Bearer $LOGINSIGHT_API_TOKEN" \
     -H "Accept: application/json" | jq '.nodes[] | {id, ip, status, uptime}'
   

4. Report to User: Summarize the JSON output into a clean, readable table detailing the overall health and the status of each node. Point out any errors or disconnected nodes explicitly.