Provide Status page for nuget.org indexing

Folks, thank you for the awesome work you are doing for .NET community. You are the central hub for all our package needs in the entire .NET community. Keep it up!

There is a tiny issue, though.

I published a package today (https://www.nuget.org/packages/MessageVault.Client), version 2.1.0. Build server was unable to pull this version from the nuget.org, saying that the package is not found. After the investigation, it looks like that this url wan’t updated: https://www.nuget.org/api/v2/Packages(Id=‘MessageVault.Client’,Version=‘2.1.0’). It returns:

<m:error xmlns:m="http://schemas.microsoft.com/ado/2007/08/dataservices/metadata">
<m:code/>
<m:message xml:lang="en-US">Resource not found for the segment 'Packages'.</m:message>
</m:error>

Older versions of the same package return meaningful XML.

When I asked for advice on the twitter, I got this feedback: “@abdullin recently uploaded? NuGet.org has indexing issues today” and “@JakubKonecki @abdullin apparently the 6 hours ago on the packages page is an indicator.”

If indexing issues are indeed the root cause here, please provide some feedback on their status. It would be awesome to have them visible on status.nuget.org.

I’d love to have visibility instead of following another twitter advice regarding nuget.org downtime “Recommend patience…”.

[anangaur]

@jahmai Created an issue: https://github.com/NuGet/NuGetGallery/issues/4881

[csharpfritz]

Thank you for making my point for me: for all but a very limited number of packages, you can NuGet install them with no problems.

That’s what service degradation is.

On Mon, Jun 1, 2015 at 1:38 PM, Steffen Forkmann [e-mail] wrote:

If you can’t “nuget install” then it feels pretty broken for me. On Jun 1, 2015 19:34, “Jeffrey T. Fritz” [e-mail] wrote:

I would consider this behavior an outage, but rather a tolerable service degradation.

All read operations against the NuGet gallery contents that were present from before the point that the index process slowed down were serviced with no failures.

Jeff

On Mon, Jun 1, 2015 at 12:51 PM, Steffen Forkmann < [e-mail]> wrote:

of course the root course is something else. It’s that two API functions give different information. Reported years ago somewhere on codeplex and also here on github.

#2126 (comment) < https://github.com/NuGet/NuGetGallery/issues/2126#issuecomment-43786202

<- closed without solution

#2149 https://github.com/NuGet/NuGetGallery/issues/2149 <- nothing happens

— Reply to this email directly or view it on GitHub < https://github.com/NuGet/NuGetGallery/issues/2432#issuecomment-107634666

.

— Reply to this email directly or view it on GitHub < https://github.com/NuGet/NuGetGallery/issues/2432#issuecomment-107649076>

.

— Reply to this email directly or view it on GitHub https://github.com/NuGet/NuGetGallery/issues/2432#issuecomment-107650495 .