Troubleshooting LiteLLM Integration

verifying the data in amberflo if your api call returned a success response, the final step is confirming that amberflo received and processed the meter event log in to amberflo navigate to the ai usage and cost dashboard within two minutes, you should see at least one new usage entry corresponding to the call you just made through the gateway you should expect to see the model you called the provider (for example, openai or azure openai) input and output token counts the team mapped to a business unit cost (if you have configured contracted or public rates) if you see the event in amberflo, your integration is confirmed if you do not see the event within two minutes, use the troubleshooting section below troubleshooting api call failures if the api call itself failed, the issue is almost always within the ai gateway configuration, not amberflo these are the common litellm failure modes and their likely causes authentication errors examples 401 unauthorized invalid api key missing or invalid virtual key causes wrong virtual key in the authorization bearer … header virtual key not associated with the team virtual key disabled or expired typo in the header or missing “bearer” fix reconfirm the virtual key via /v1/keys ensure it is tied to the correct team retry the call provider errors examples provider not found provider is not configured missing provider api key causes provider was never created provider exists but has no api key api key is incorrect or expired model references a provider that doesn’t exist fix check the provider list get /v1/providers re enter the provider’s api key recreate the provider if needed model errors examples model not found invalid model name unsupported model causes model was not created model name doesn’t match the provider’s naming model references the wrong provider provider does not support the specified model fix check models get /v1/models confirm the model name exactly matches what the provider expects recreate the model with correct provider linkage team or virtual key errors examples team not found key not associated with a team causes team not created virtual key created but not assigned to any team virtual key assigned to the wrong team fix check teams get /v1/teams check keys get /v1/keys reassign or recreate the key as needed outbound network errors examples the api call succeeds, but no meter events show in amberflo within two minutes logs show errors hitting the amberflo callback endpoint causes firewall blocking outbound https incorrect amberflo ingest url missing or incorrect litellm master key or salt key gateway cannot reach amberflo due to corporate proxy rules fix curl test the amberflo ingest endpoint from the host re confirm environment variables check logs for connection failures ensure outbound traffic to https is allowed if none of the above applies and you still do not see events in amberflo, the next place to check is the gateway logs litellm logs are usually explicit about configuration issues missing keys, misnamed models, or connection errors