ErrorLog on Windows Azure tables produces wrong report title

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Use windows azure table as storage 
2. Successfully pull back errors and step out of custom azure code defined as 
public override int GetErrors(int pageIndex, int pageSize, 
System.Collections.IList errorEntryList)
3. Calling location of string hostName = 
Environment.TryGetMachineName(Context); found in file ErrorLogPages.cs should 
be using the Azure Deployment name (or maybe instance/deployment). In other 
words, this needs to also be part of the override class. Another option is to 
hardcode this in the web.config.

What is the expected output? What do you see instead?
Expected out, regardless of dev box or live release up on azure, is that I see 
some indication of where the call returned from on Azure.  

Please use labels and text to provide additional information.

Original issue reported on code.google.com by berry.d...@gmail.com on 11 Jul 2011 at 12:57

[GoogleCodeExporter]

Since ELMAH does not ship with a built-in error log implementation for Windows 
Azure Table Storage at this point, I'm assiming this issue is related to the 
implementation available over the WindowsAzure.ELMAH.Tables[1] NuGet package? 
If so, you may want to check with the author directly for support.

http://nuget.org/packages/WindowsAzure.ELMAH.Tables

Original comment by azizatif on 18 Dec 2011 at 6:51

• Changed title: ErrorLog on Windows Azure tables produces wrong report title
• Changed state: Invalid

[GoogleCodeExporter]

I'm re-opening this issue as I misread your issue. I see now it's not related 
to the ErrorLog implementation but that ErrorLogPage is fixed on the machine 
name and you would have something more meaningful in the Azure environment like 
the deployment/instance name/Id?

Original comment by azizatif on 18 Dec 2011 at 7:03

• Changed state: New
• Added labels: Component-UI, Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

This issue has been migrated to:
https://github.com/elmah/Elmah/issues/236
The conversation continues there.
DO NOT post any further comments to the issue tracker on Google Code as it is 
shutting down.
You can also just subscribe to the issue on GitHub to receive notifications of 
any further development.

Original comment by azizatif on 25 Aug 2015 at 8:20