Project

General

Profile

Bug #432

hostname in dataselect and station usage is an IP, not an hostname

Added by P Volcke over 8 years ago. Updated about 4 years ago.

Status:
New
Priority:
Low
Assignee:
Target version:
-
Start date:
01/15/2014
Due date:
% Done:

0%

Estimated time:
Resolution:
Won't Fix

Description

about the WSShell usage loggers (ie. dataselect_usage.log & station_usage.log) :

"Client Name" column seems to be the IP instead (but there's already another field with the IP).

~~~~~~~~~~

Log of email exchances with Bruce @ IRIS :

The code looks like this:

public static String getClientName(HttpServletRequest request) {
return request.getRemoteHost();
}

public static String getClientIp(HttpServletRequest request) {
String xfIp = getXForwardIp(request);
if (xfIp == null) {
return request.getRemoteAddr();
} else {
return xfIp;
}
}

In our case, they both appear to be returning an IP address. I am confused about this.

For example, in out logs I see this:
access_date=2014-01-06T18:31:04, application=fdsnws-dataselect_summary, client_ip=78.156.72.172, client_name=78.156.72.172, data_size=512, host=wslive4, http_status=200, process_time=454, user_agent=Swarm/2.3.2.5

I do not know why it behaves like that. Our non-was services (for example irisws-timeseries) do not behave this way.
The String xfIp = getXForwardIp(request); code is used to get the incoming ip address from the load balancer.

History

#1 Updated by Chad Trabant over 8 years ago

  • Assignee set to Mike Stults

#2 Updated by Chad Trabant about 7 years ago

  • Target version set to 1.1.10

Review for 1.1.10

Need to evaluate the performance impact of resolving hostnames.

Should probably be an option, controllable through the configuration file.

#3 Updated by P Volcke almost 7 years ago

Chad Trabant wrote:

Review for 1.1.10

Need to evaluate the performance impact of resolving hostnames.

Should probably be an option, controllable through the configuration file.

hi Chad,
do agree that resolving hostnames may have serious performance impact. FYI we perform post-analysis
of our WSS "dataselect_usage.log" files, using a caching tool for DNS hostname resolution. Thus, this reported
issue #432 is not critical to us.
best,
Pierre

#4 Updated by Mike Stults almost 7 years ago

  • Target version deleted (1.1.10)

#5 Updated by Mike Stults about 4 years ago

  • Resolution set to Won't Fix

Potentially large negative impact on performance and may also leave some addresses unresolved.

Also available in: Atom PDF