transaction counts for bad urls

Not applicable

Hi Folks,

I have multiple conditional flow in my proxy endpoint each handling different HTTP verb and resource path. What I see in trace is that even if a transaction doesn't match any conditional flow (it matches base path though), it appears in trace would it mean that it would be counted towards a transaction for my organization in Apigee?

1. If so wouldn't it be bad for business as anybody can send bad requests with missing or bad resource path in url and that would cost my enterprise.

2. Does transaction rejected by spike arrest or quota policy also count towards actual transaction ?

0 1 128
1 REPLY 1

Hi @Mayank

You are correct, any request that Apigee does some processing on is considered as traffic and counted as part of your monthly/quarterly traffic allowance. There is one exception, any requests that are impacted by an Apigee failure, for example an Apigee outage, are not counted.

In the case of a client sending bad requests or requests rejected by spike arrest or quota, our product is doing its job and preventing these from reaching your configured targets.

If you need to protect against elevated unwanted traffic from bots or malicious developers, we recommend take a look at Apigee Sense.

If I have answered your question, please click the "answer" link below; alternatively let us know how we can further help.