Interface DataSink
- All Superinterfaces:
- HistoryStorer
- All Known Subinterfaces:
- DataStore,- StoreAndForwardEngine
- All Known Implementing Classes:
- AbstractDatasourceSink,- AbstractSink,- AggregateSink
A data sink accepts history. It's just a bit heavier weight than a plain old HistoryStorer, from which it extends. It
 supports startup and shutdown, along with the idea that it may not always be able to or want to accept data, which is
 indicated by the "isAccepting" property.
- 
Field SummaryFieldsModifier and TypeFieldDescriptionstatic final StringThe template for loggers under the store and forward system.
- 
Method SummaryModifier and TypeMethodDescriptiongetInfo()Gets the information for this sink, as well as any below it.default StringHow this element will be represented in the log system.Returns the name of the store and forward pipeline that this sink belongs to.Returns the quarantine interface for the sink.booleanReturns whether the data store is accepting data.voidshutdown()voidstartup()Methods inherited from interface com.inductiveautomation.ignition.gateway.history.HistoryStoreracceptsData, isLicensedFor, storeData
- 
Field Details- 
LOG_NAME_TEMPLATEThe template for loggers under the store and forward system. Includes a string format parameter- should be ObjectName- See Also:
 
 
- 
- 
Method Details- 
getPipelineNameString getPipelineName()Returns the name of the store and forward pipeline that this sink belongs to.
- 
startupvoid startup()
- 
shutdownvoid shutdown()
- 
isAcceptingboolean isAccepting()Returns whether the data store is accepting data.
- 
getInfoList<DataSinkInformation> getInfo()Gets the information for this sink, as well as any below it.
- 
getQuarantineManagerReturns the quarantine interface for the sink. If the sink doesn't support quarantined data, can return null.
- 
getLogNameHow this element will be represented in the log system. The full name of the logger will be "StoreAndForward.{ThisValue}" It should be surrounded with a MDC key of the pipeline name
 
-