Marsh's dashboard

A comment on the question "Why no path or query parts in the API target URL configuration?" in Apigee:

Hi Jochem,

This was part of our last sprint, which just wrapped up. Unfortunately we couldn't get to it in time.

But personally, this is a feature near and dear to my heart, so I promise we'll keep at it! Hope to have some updates for everyone soon (as a general rule we don't promise dates). – Marsh, on March 05, 2010 15:03

Marsh replied on February 25, 2010 01:47 to the question "Can we control API rate-limit on an IP basis or end-user basis?" in Apigee:

Edward, great question. Rate-limiting by IP address is a feature we're tracking in our product backlog, though I can't promise when we'll have this.

We're also considering another solution that you might prefer—the ability to have the client request a unique identifier for your proxy via the Apigee API. The resulting metrics could then pivot around that data, which would be a better way to visualize usage by users of your app.

If you have any further thoughts about this, we'd love to hear them.

~ Marsh

A comment on the question "Apigee Server IPs" in Apigee:

Re subnet: Apigee is a highly available service, so we worry about and plan for failure at the data center (and above). The only way to mitigate that kind of problem is to distribute our servers, which means that a single subnet isn't possible.

But you make some good points (and it's always a pleasure to hear your perspective, Matthias), and you've raised an important provider use-case (firewall configuration) that we'll keep considering how to address as we continue to grow. In the meantime, the two IPs listed above are what you need.

Cheers, Marsh – Marsh, on February 19, 2010 14:04

Marsh replied on February 18, 2010 18:28 to the question "Apigee Server IPs" in Apigee:

Matthias, the current Apigee IPs are 174.129.236.240 and 75.101.150.28.

Do you think you would ever use an Apigee API method to auto-update your rules? Would pushing the IP change notices to Twitter be of any use to you?

Marsh replied on February 17, 2010 19:40 to the question "Apigee Server IPs" in Apigee:

Matthias, that's a fantastic question. We'll get you a list of IP's as soon as we confirm them.

But your post got me thinking, as new IPs come online from time to time, and old IPs could be deprecated. At the very least it needs to be documented (FAQ perhaps). We're even considering how we might use Apigee's API to indicate current IP ranges, as well as to list what IPs are marked for deprecation or coming online. We could also set up a mailing list.

If you have any input about what you'd like, by all means let us know.

Marsh replied on February 13, 2010 19:48 to the problem "Please go back to step 1 and enter valid API name error" in Apigee:

It sounds like a browser issue... FWIW, I'm using Chrome 4.0.249.89 Beta on Windows 7 with no trouble. We'll test this again on OSX with Chrome.

Thanks again for all the info and hope it's smooth sailing from here.

Marsh

Marsh replied on February 13, 2010 19:27 to the problem "Please go back to step 1 and enter valid API name error" in Apigee:

Abraham,

Thanks for the step-by-step screenshot walkthrough—that was very helpful. Using my own account, I followed your instructions exactly (though I had to choose a different subdomain), and I had no trouble. Then as administrator, I added the proxy to your account, which also seems to have worked. You should be able to use that proxy now.

So the good news is that your proxy should now be working properly. The bad news is that I have no idea why you had trouble, as I cannot reproduce the error. What browser (and version) are you using and under what OS?

Thanks,

Marsh

Marsh replied on February 13, 2010 18:04 to the problem "Please go back to step 1 and enter valid API name error" in Apigee:

What are the settings you're using to have this situation? That will help us recreate what you're seeing. If there's any chance you could include a screenshot, that would be helpful too.

Sorry you're having trouble!

Marsh

Marsh replied on February 08, 2010 16:16 to the question "Where can I find the ApiGee token for my API?" in Apigee:

Visit this URL in a browser:
https://api.apigee.com/authtoken

When you provide your username and password, you should get your token as a response.

The Apigee API is currently in pre-beta. We'll improve token discovery as we get closer to launching it.

A comment on the question "API endpoint doesn't support paths?" in Apigee:

Hi Udi, under the current proxy setup, in step 2 you would supply www.threadsy.com as the API Hostname, and choose an Apigee subdomain for your proxy, something like api.threadsy.apigee.com.

In step 3 you'd supply an API method like "gateway/version.json" to test.

Once you finished the proxy setup process, you could call http://api.threadsy.apigee.com/gatewa... and get a response from threadsy.com through the proxy.

At that point you can optionally set up a CNAME record to map a subdomain, such as api.threadsy.com, to that Apigee proxy. See these docs for more info: http://apigee.com/docs/setting_up_dns

We've redesigned the proxy setup screens, and we're working on building them into Apigee in this current development sprint.

We're also planning how to add optional support for paths in the API endpoint, so that you could define "gateway" as part of the path and just use http://api.threadsy.apigee.com/versio... to make the request (or http://api.threadsy.com/version.json in the CNAME example). Is this something you'd like to see?

Let me know if you have any further questions. – Marsh, on February 02, 2010 21:45

A comment on the question "How real-time are the charts?" in Apigee:

Here's a workaround in the short term. On the Overview, choose 3 Days as the timeframe. Then visit the Requests view, and you'll see data. When you go back to the Overview, you can now choose the "Day" period and see the same numbers as you do with the /apis list.

This is most certainly a problem with fetching and displaying the stats—I can assure you the data is still there and no requests are being dropped. As soon as I know more, I'll get back to you (FYI, today is a holiday in the US, so it might be a little slower than usual!).

And thanks for the bug report! – Marsh, on January 18, 2010 16:21

A comment on the question "How real-time are the charts?" in Apigee:

Thanks, now I have enough information to reproduce what you're seeing. Let me get this info to engineering so we can figure out what's going on. – Marsh, on January 18, 2010 16:08

Marsh replied on January 12, 2010 22:17 to the problem "Errors on Step 3 of API setup are not clearly documented" in Apigee:

Good point. We're reworking the API setup pages, which should address this.

A comment on the question "How real-time are the charts?" in Apigee:

Hi Matthias,

We don't lose requests, so I'm not sure what you're seeing. There does appear to be a bug with the way the left-most part of the graph drops to 0, but we're working on that.

Basically, data should be available within 5 minutes, with 10 minutes being the worst case. If you're seeing something other than that, a screenshot might help me understand.

Let us know what more we can do,

Marsh – Marsh, on January 12, 2010 21:20

Marsh marked one of Manoj Chakraboty's replies in Apigee as useful. Manoj Chakraboty replied to the problem "504 Gateway Timeout on long API requests".

A comment on the question "How real-time are the charts?" in Apigee:

Matthias, can you explain more about what you're seeing? I'd be happy to investigate it further. – Marsh, on January 08, 2010 16:53

Marsh replied on January 08, 2010 14:13 to the idea "Where do our users come from" in Apigee:

Great idea—I'll make sure it's in the product backlog.

Thanks, Matthias, and keep the ideas coming!

Marsh started following the idea "Where do our users come from" in Apigee.

Marsh replied on January 06, 2010 19:32 to the question "Why no path or query parts in the API target URL configuration?" in Apigee:

To recap, there are two issues in this thread:

1) Whether paths can be specified as part of the proxy endpoint, rather than just the domain, which would help with the Twitter versioning situation.

2) Support for APIs like Tumblr's which don't exactly conform to REST (e.g. the username is part of the domain rather than a parameter to a constant API endpoint).

#1 is likely to be implemented earlier. As for the specific case in #2, Tumblr announced support for the Twitter API, which might be serve as a stop-gap solution in the interim. I promise that we are tracking both of these issues in our product backlog and hope to get to them as soon as possible.

Marsh replied on January 05, 2010 02:21 to the problem "504 Gateway Timeout on long API requests" in Apigee:

We'll look into this and get back to you.

Thanks for the feedback—I don't think we ever considered a 10 min response. Out of curiosity, why does it take so long?