Project

General

Profile

Feature #632

status mechanism for handlers

Added by Yazan Suleiman almost 8 years ago. Updated about 4 years ago.

Status:
New
Priority:
Normal
Assignee:
Target version:
-
Start date:
11/07/2014
Due date:
% Done:

0%

Estimated time:
Resolution:
Won't Fix

Description

There are 2 types of information a handler may have interest in showing:
public data : number of networks, station, channels, last update.
private data: database info (host, name ...)

This can be done if the WSS accepts input from the Handler Streamingoutput.

History

#1 Updated by Chad Trabant over 7 years ago

  • Subject changed from Handlers status to status mechanism for handlers

I would like to initially focus on making the private status information available, we can include the mentioned public data in the same summary.

White list IP ranges (IP and netmask) are an appropriate level of access for this kind of information. This white list control should be a function of the WSS as a standard feature.

A path should be determined, how about <interface>/status-handler ?

#2 Updated by Mike Stults about 4 years ago

  • Resolution set to Won't Fix

This feature can be implemented with the existing WSS functionality using the allowedIPs capability to distinguish between private and public.

For example, to add public and private database statuses, add two endpoints like this;

  1. for the public status endpoint
    db-status.endpointClassName=edu.iris.wss.endpoints.CmdProcessor
    db-status.handlerProgram=/wss_handlers/dbStatusHandler
    other properties, etc.
  1. for the private status endpoint, add allowedIPs property
    db-private-status.endpointClassName=edu.iris.wss.endpoints.CmdProcessor
    db-private-status.handlerProgram=/wss_handlers/dbStatusHandler # same handler or different
    aother properties, etc.
    db-private-status.allowedIPs=127.0.0.1/32,::1/128,172.17.0.0/24 # set IPs as needed

Also available in: Atom PDF