In Apache Flume we need to specify configuration details of Source, channel and Sink.
For each we must specify type and other properties depending on type.
Is there a reference page which enlists all types of Source, channel and Sink each. And then corresponding other properties based on type.
And when to use which type.
Can someone please point me to correct documentation ?
There is excellent documentation of all components on the official website: https://flume.apache.org/FlumeUserGuide.html
Related
Is there a standard way to update the SMBIOS table, to add new variables?
For example, if I would like to change a variable such as 'mainboard name', or more generically, add a new entry in the table to define custom struct and value, what would be the standard way to implement this, so that I can query this value with dmidecode, /sys/class/dmi, or libsmbios?
Obviously, the board manufacturers have tools to change such values in the SMBIOS table, and which can be accessed from operating system in a standard way.
The /sys/firmware/dmi/tables interface seems to be read-only. Can one write to the respective area under /dev/mem (using smbios_entry_point) to add new entries?
Is there an alternative standard and modern way to save such (custom) hardware information, to avoid having to query the hardware component directly? from UEFI?
There is such an option for COM Express® module. The PICMG specification depict an EEPROM on the Carrier Board that can hold SMBIOS data. Take a look at following specification:
https://www.picmg.org/wp-content/uploads/PICMG_EeeP_R1_0.pdf
There is a source code for updating the EEPROM at: https://sourceforge.net/projects/eapidk/
But in COM Express® Carrier Design Guide https://www.picmg.org/wp-content/uploads/PICMG_COMDG_2.0-RELEASED-2013-12-06.pdf there is following statement
The EEPROM stores configuration information for the system of the Carrier Board. The data
structure used is defined in the PICMG EEEP Specification. The Specification recommends but
does not require the use of this system configuration EEPROM. The Module BIOS may check
the Carrier Board configuration EEPROM but is not required to do so by the Specification.
Which allow BIOS/Firmware vendor to skip this EEPROM.
The descriptions of the property modifiedProperty do not contain a list of (or a link to) its possible values, which makes it difficult to utilize APIs that return this resource type.
Document Details
Content: modifiedProperty resource type - Microsoft Graph v1.0
Content Source: api-reference/v1.0/resources/modifiedproperty.md
Product: microsoft-identity-platform
Technology: microsoft-graph
Link : https://github.com/microsoftgraph/microsoft-graph-docs/blob/master/api-reference/v1.0/resources/modifiedproperty.md
It would be helpful if the list of possible values could be provided.
I highly doubt you're going to be able to find such a list. The values of the modifiedProperty property are going to vary based on which type of Azure resource you're looking at and which property on that resource was modified. The only thing you can be certain of is that the modifiedProperty will be empty or it will contain a property name, the old value, and the new value, according to the documentation you linked.
If you are trying to code for a particular type of Azure resource or a particular type of property, you should look into the documentation for that resource or property instead of the documentation for getting that information.
I want to configure IIB 10 and MQ 8 so that the published monitoring-event messages are persisted in a persistent MQ queue.
The manual at : https://www.ibm.com/support/knowledgecenter/SSMKHH_10.0.0/com.ibm.etools.mft.doc/ac37850_.htm
has a Note to say:
Publications resolve to be nonpersistent by default, but you can change a publication to be persistent by configuring named topics in WebSphere® MQ. For more information, see the Subscriptions and message persistence topic in the WebSphere MQ Version 7.5 product documentation online.
Unfortunately, this weird ref to an old version of MQ leads nowhere.
I went through the MQ manual that defines the fields in the Topic definition in Explorer and that doesn't help, since the 'Default persistence' requires the publisher to use MQPER_PERSISTENCE_AS_Q_DEF. As IIB's default is 'not persistent', I have to assume it doesn't use this.
I'd be really grateful if someone could tell me how to override this and have persisitent messages written to a persistent queue.
FWIW
I originally assumed that defining the queue to receive the event messages as persistent would do the trick - it doesn't.
Next, I tried defining a topic XXX with topic string $SYS/Broker/int-sver/monitoring/+/+ with 'Default persistence' set to 'Persistent' - that doesn't work, either.
You mentioned the docs state "Publications resolve to be nonpersistent by default", this does not mean that they use MQPER_NOT_PERSISTENT, likely they use MQPER_PERSISTENCE_AS_Q_DEF or specify nothing at all in which case it defaults to the same as if MQPER_PERSISTENCE_AS_Q_DEF was specified.
The problem is with your topic string. A TOPIC object is a anchor to a leaf in the tree. It applies to anything below that leaf unless a more specific TOPIC object applies. So in your case the string should be $SYS/Broker/int-sver/monitoring with out the /+/+ at the end.
+ is a wildcard and wildcards only come into play on subscriptions not on topics.
You can find more information in the IBM MQ v8.0 Knowledge Center page IBM MQ>Technical overview>IBM MQ objects>Object types>Topic objects:
A topic object is an IBM® MQ object that allows you to assign
specific, non-default attributes to topics.
A topic is defined by an application publishing or subscribing to a
particular topic string. A topic string can specify a hierarchy of
topics by separating them with a forward slash character (/). This can
be visualized by a topic tree. For example, if an application
publishes to the topic strings /Sport/American Football and
/Sport/Soccer, a topic tree will be created that has a parent node
Sport with two children, American Football, and Soccer.
Topics inherit their attributes from the first parent administrative
node found in their topic tree. If there are no administrative topic
nodes in a particular topic tree, then all topics will inherit their
attributes from the base topic object, SYSTEM.BASE.TOPIC.
You can create a topic object at any node in a topic tree by
specifying that node's topic string in the TOPICSTR attribute of the
topic object. You can also define other attributes for the
administrative topic node. For more information about these
attributes, see the The MQSC
commands,
or the Automating administration
tasks.
Each topic object will, by default, inherit its attributes from its
closest parent administrative topic node.
topic objects can also be used to hide the full topic tree from
application developers. If a topic object named FOOTBALL.US is created
for the topic /Sport/American Football, an application can publish or
subscribe to the object named FOOTBALL.US instead of the string
/Sport/American Football with the same result.
If you enter a #, +, /, or * character within a topic string on a
topic object, the character is treated as a normal character within
the string, and is considered to be part of the topic string
associated with a topic object.
For more information about topic objects, see Publish/subscribe
messaging.
The closest page I could find to the link in the IIB KC on MQ v8.0 is the IBM MQ Knowledge Center page IBM MQ>Developing applications>Developing MQI applications with IBM MQ>Writing a procedural application for queuing>Writing publish/subscribe applications>Subscription options:
Message persistence
--
Queue managers maintain the persistence of the publications they
forward to subscribers as set by the publisher. The publisher sets the
persistence to be one of the following options:
0
Nonpersistent
1
Persistent
2
Persistence as queue/topic definition
For publish/subscribe, the publisher resolves the topic object and
topicString to a resolved topic object. If the publisher specifies
Persistence as queue/topic definition, then the default persistence
from the resolved topic object is set for the publication.
This article explains how to generate and subscribe to broker generated event messages.
It is not in the text, but I think the generates messages are persistent.
https://www.ibm.com/developerworks/websphere/library/techarticles/0911_fan/0911_fan.html
At the subscription queue one could also set DEFPSIST(YES)
I have created jmx agent which generates custom data as attribute and returned as composite data type when viewed in jconsole.
The original datatype is ArrayList. How would I construct the jmx item key in zabbix.
jmx[com.example:Type=Hello,fruits.apple.weight]
How would I do if I need to access an array of objects.
Any ideas or suggestions is appreciated.
Unfortunately, accessing array or lists is currently not supported in Zabbix, but there is a feature request for that: ZBXNEXT-1570.
How to get the key of a especific directory in the registry of windows XP?
I'm using Delphi
HKEY_CURRENT_USER\Software\Microsoft\Windows\ShellNoRoam\Bags
There are no directories in the registry. The registry contains keys and values. The values have names and data. The keys are like directories, though.
If you want to inspect the contents of a key, you can use the TRegistry class. Set its RootKey property to HKey_Current_User, and use its OpenKeyReadOnly method to open the subkey. Then you can use the various Read methods to read the data of any value.
If you're not sure what the type is of a data entry, you can use the GetDataType orGetDataInfo` methods.
To read a list of all the data entries' names, you can use GetValueNames.
All of those are documented in the help, and now that you know their names, it should be easier for you to find many examples.