Improve ArmorCode integration observability by enhancing monitoring and status messaging so users can clearly distinguish between transient retry scenarios (such as API rate limiting) and actual ingestion failures, and confirm when ingestion has successfully completed.
S
Shamrock Nightingale
The ArmorCode integration currently retries ingestion jobs when API rate limits are encountered. During these retries, the integration monitoring UI surfaces “unknown error” states and alternating red/green job statuses, which makes it difficult for users to determine whether ingestion ultimately succeeded or failed.
As a result, users cannot easily confirm whether data was fully ingested, partially ingested, or missed entirely. This lack of observability creates uncertainty around the completeness and reliability of the security insights data and requires manual verification.
Log In