Class OpsviewProvider

java.lang.Object

ecmwf.common.monitor.module.OpsviewProvider

All Implemented Interfaces:

MonitorInterface

public final class OpsviewProvider
extends Object
implements MonitorInterface

The Class OpsviewProvider.

Constructor Summary

Constructors

Constructor	Description
OpsviewProvider()

Method Summary

Modifier and Type	Method	Description
void	addNotes(String destination, int type, String metadata)	Adds/replaces the notes attached to a destination/host.
void	sendMessage(String hostname, String service, int status, String message)	Sends the message.

Methods inherited from class Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Details

OpsviewProvider

public OpsviewProvider()

Method Details

sendMessage

public void sendMessage(String hostname,
 String service,
 int status,
 String message)
                 throws MonitorException

Sends the message. Send message.

Specified by:

sendMessage in interface MonitorInterface

Parameters:

hostname - the name

service - the service

status - the status

message - the message

Throws:

MonitorException

addNotes

public void addNotes(String destination,
 int type,
 String metadata)
              throws MonitorException

Adds/replaces the notes attached to a destination/host. A default method (rather than a second abstract one) so that MonitorInterface.sendMessage(String, String, int, String) remains this interface's only abstract method - existing providers set up as a lambda (a single-method functional interface, e.g. a DataMover relaying sendMessage calls to the MasterServer over its REST proxy) keep compiling unchanged, and simply don't support notes: the default throws UnsupportedOperationException, which MonitorManager.addNotes(String, int, String) turns into a MonitorException for the caller. Adds/replaces the notes attached to a destination/host. Unlike sendMessage(String, String, int, String), errors are propagated (wrapped in a MonitorException) rather than swallowed: this is invoked from a direct, user-initiated action (the "Export Notes" button on the Destination Metadata page), so the caller needs to know whether it actually succeeded.

Specified by:

addNotes in interface MonitorInterface

Parameters:

destination - the destination

type - the destination's type (ecmwf.ecpds.master.transfer.DestinationOption), used by providers that group destinations by type (e.g. Opsview's Acquisition/Dissemination/Other filters)

metadata - the metadata

Throws:

MonitorException