om sec push resinfo

Push the local service instance resources and application launchers info key/value pairs the collector.

--color=<string>

Colorize output. Possible values are:

• auto: guess based on tty presence
• always|yes: always colorize
• never|no: never colorize

--cron

If set, the action is actually executed only if the schedulingconstraints are satisfied.

--daemon

A flag inhibiting the command daemonization. Set by the daemonization routine.

--debug

Increase stream and file log verbosity up to the debug level.

--env

Export the uppercased variable in the os environment.

With the create action only, set a env section parameter in the service configuration file. Multiple --env <key>=<val> can be specified. For all other actions.

--local

Execute the service action on the local service instances only, ignoring cluster-wide considerations.

--namespace=<string>

The namespace to switch to for the action. Namespaces are cluster partitions. A default namespace can be set for the session setting the OSVC_NAMESPACE environment variable.

--node=<string>

The node to send a request to. If not specified the local node is targeted.

--status=<string>

Operate only on service with a local instance in the specified availability status (up, down, warn, ...).

--sync

Use synchronous collector communication. For example, push resinfo --sync before a compliance run makes sure the pushed data has hit the collector database before the rulesets are contextualized.

--waitlock=<string>

A duration expression like 5s. The maximum wait time when acquiring the service action lock.

-h, --help

Show this help message and exit.

-p, --parallel

Start actions on specified services in parallel. max_parallel in node.conf limits the number of parallel running subprocesses.

-s, VAL, --service=<string>

A service selector expression [!]<expr>[<sep>[!]<expr>] where:

• ! is the expression negation operator
• <sep> can be:
  • , OR expressions
  • + AND expressions
• <expr> can be:
  • a shell glob on service names
  • <param><op><value> where:
    • <param> can be:
      • <rid>:
      • <group>:
      • <rid>.<key>
      • <group>.<key>
      • <single value jsonpath expression on the $.monitor.services.<path> dictionary extended under the 'nodes' key by each instance 'status' and 'config' data>
    • <op> can be:
      • < > <= >= =
      • ~ with regexp value

Examples:

• *dns,ha*+app.timeout>1
• ip:+task:
• !*excluded
• $.avail=warn
• $.nodes.*.status.avail=warn

Note:

• ! usage requires single quoting the expression to prevent shell history expansion