sentry-bundles

Loads the bundle list of a sentry.

Syntax

sentry-bundles [timeout=INT]
Parameter
timeout=INT
RPC timeout in seconds (default: 30 seconds)

Description

This query command sends asynchronous RPC request messages to 100 sentries at the same time and waits for responses.The RPC request message queue operates on a first-in, first-out (FIFO) basis. For example, if the Logpresso server needs to send RPC messages to 150 sentries, the server sends an RPC message to 100 sentries first and waits until RPC responses. If the waiting time exceeds the time specified in the timeout (default: 30 seconds), it is considered that an error has occurred on the sentry side. If 32 out of 100 sentries respond or timeout is exceeded, the Logpresso server sends an RPC message to the additional 32 sentries.

The query command outputs the results of RPC response messages in the order they are received. Depending on the load or network conditions of the host where Sentry is installed, the order of the responses may vary with each execution. Use the output data but do not rely on the order of the records.

Tip
Logpresso environment variable `logpresso.core.sentry_rpc_parallel` determines the length of the asynchronous RPC request message queue. The default value is `100` and you can adjust the length by modifying the value of this environment variable.
Input Field

This query command requires that the input record contains a guid field value.

FieldTypeDescription
guidStringUnique sentry identifier (Not relevant to GUID in JAVA)
Output Fields

This query command returns the fields below in addition to the fields from input record.

FieldTypeDescription
bundle_id64-bit IntegerBundle ID
symbolic_nameStringBundle symbolic name
versionStringBundle version
stateStringByndle status
last_modifiedDateLast modification
integrityStringIntegrity status

Possible bundle statuses in the state field are as follows:

StatusDescription
ACTIVEBundle is running.
INSTALLEDBundle is installed but bundle's dependencies have not been met.
RESOLVEDBundle dependencies are all resolved and bundle is ready to start.
STARTINGBundle is starting.
STOPPINGBundle is stopping.
UNINSTALLEDBundel has been removed.

Possible integrity statuses in the integrity field are as follows:

StatusDescription
no signatureDigitally signed hash value is not found.
hash errorSHA-512 hashing of the bundle failed (e.g. I/O error)
verifiedThe hash values match, the data has not been altered.
modifiedThe hash values do not match, the data has been modified.

If any error occurs, this query command returns an _error field in addition to the fields from input record. Possible errors are as follows:

Error MessageDescription
guid is nullguid field value from input record is null.
guid should be stringguid field value from input record is not a string.
guid should be non empty stringguid field value from input record is empty.
timeoutRPC request timeout exceeded
disconnectedDisconnected while processing RPC request
not connectedSentry is not connected.

Depending on the system where the sentry is installed, an RPC exception message other than the above can be issued.

Usage

  1. Load bundle lists of all sentries.

    sentry | fields guid | sentry-bundles