search

Dim0N22 / elmah

Automatically exported from code.google.com/p/elmah
Apache License 2.0
0 stars 0 forks source link

2 websites on 2 machines with same IIS-applicationname causes Elmah to display errors from both websites #346

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Set up 1 sqlELMAH db
2.Set up 2 websites each on it's own machine, and each having a unique 
hostname. 
3. Set up each website so that they have the SAME IIS application-name. (The 
name which is logged in the dbfield called Application)
4.Install ELMAH to each website and make them use the same elmahDB
5. Produce an error on websiteA
6. Produce an error on WebsiteB
7. View errorlog on WebsiteA

Go to websiteA's errorlog. The expected result would be to see only websiteA's 
error. 
Elmah should take into consideration the HOSTNAME on which it is running and 
only show errormessages from this hostname

Instead, because elmah does not care about the hostname, and the websites have 
the same Application-name, errors from both websites is displayed on each of 
the websites.

Elmah version: 1.2 (Latest)
DB: Mssql 2005

Please provide any additional information below.

Original issue reported on code.google.com by christia...@gmail.com on 29 Oct 2013 at 1:23

Attachments:

GoogleCodeExporter commented 9 years ago 
Here is a screenshot of both GUI and database to illustrate the problem

Original comment by christia...@gmail.com on 29 Oct 2013 at 1:35

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry, but this is not a valid issue.

Please raise this as a discussion here: 
https://groups.google.com/forum/#!forum/elmah, and we'll be able to help you 
there.

Cheers,

James

Original comment by jamesdriscoll71 on 29 Oct 2013 at 1:45

GoogleCodeExporter commented 9 years ago 
@jamesdriscoll71 I think this is a valid report as long as @christian.holm 
believes this to be a genuine bug. :)

@christian.holm This is by-design. The only filter is the application name. The 
idea is that an application can be deployed on 2 (or more) servers but you may 
be viewing the log through yet another server. It enables centralization and 
viewing errors "across" the app if needed through any server.

Original comment by azizatif on 29 Oct 2013 at 3:32