Home
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
Configuring audit logging
Teracloud® Streams supports comprehensive, multiple-level auditing of product and user operations. By default, audit logging is not enabled.
Audit log examples
Audit log entries contain information about Teracloud® Streams domains, instances, users, operations, and operation objects. Detailed messages can provide additional information.

Welcome
Learn about the core capabilities of Teracloud® Streams, its architecture, and key concepts.
Installing
Use this information to install, upgrade, and uninstall the Teracloud® Streams product.
Configuring
Create a basic or an enterprise domain which is a single point for configuring and managing common resources, security, and instances.
- Setting up a basic domain on a single resource
  A basic domain has a single Teracloud® Streams resource and user. This type of domain is typically used for test or development environments.
- Setting up an enterprise domain on multiple resources
  An enterprise domain can have multiple resources and users. This type of domain is typically used for production environments. You can configure high availability to ensure that Teracloud® Streams can continue to run even if resources fail or are not available.
- Configuring security
  Each Teracloud® Streams domain and instance maintains its own security configuration.
- Configuring audit logging
  Teracloud® Streams supports comprehensive, multiple-level auditing of product and user operations. By default, audit logging is not enabled.
  - Enabling audit logging
    To enable audit logging for Teracloud® Streams, use this procedure to create a log4j configuration file and update the required domain properties.
  - Customizing audit logging
    The sample log4j configuration file that is installed with Teracloud® Streams includes an appender example that shows you how to filter out audit event entries and messages based on certain conditions.
  - Audit log examples
    Audit log entries contain information about Teracloud® Streams domains, instances, users, operations, and operation objects. Detailed messages can provide additional information.
- Configuring transport mechanisms
  Teracloud® Streams supports several high-performance and configurable transport mechanisms for communicating across processing elements (PEs). You can configure the transport mechanism by updating Teracloud Streams properties.
- Configuring a checkpoint data store
  Use this procedure to configure a checkpoint data store for Teracloud® Streams domains and instances.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Developing
Learn about different Teracloud Streams tools and features to write, compile, run, and test streams applications.
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Teracloud® Streams audit log examples

Audit log entries contain information about Teracloud® Streams domains, instances, users, operations, and operation objects. Detailed messages can provide additional information.

Audit log format:

Timestamp* D[domain] I[instance] H[host] U[user] SUCCESS/FAILURE/NA 
SRC[operation-source] OBJ[operation-object] OP[operation-and-parameters] 
message

Timestamp* is the time that the Teracloud® Streams component performs operations and auditing. It is not the time that the logging service and log4j write the message to the appender. This format is the same as the Teracloud® Streams logging timestamp format, which is yyyy-MM-dd'T'HH:mm:ss.SSSZ.

The following examples are streamtool startinstance command operations. The first example contains a message that provides additional information.

2015-01-16T13:30:53.869-0500 D[StreamsDomain] I[StreamsInstance] 
H[host1.teracloud.com(192.0.2.0)] U[streamsadmin, streamsadmin] SUCCESS 
SRC[api] OBJ[com.teracloud.streams.admin.internal.api.StreamsInstance] OP[start, 
authUser=streamsadmin@StreamsDomain listener=com.teracloud.streams.cli.StartInstance@6b0cd689]
CDISA3004W The StreamsInstance instance started with warnings for the following domain: 
StreamsDomain. The instance is operational.

2015-01-16T13:30:53.932-0500 D[StreamsDomain] I[StreamsInstance] 
H[host2.teracloud.com(198.51.100.0)] U[streamsadmin, streamsadmin] SUCCESS(0) 
SRC[streamtool] OBJ[com.teracloud.streams.cli.StartInstance] OP[startinstance, d=StreamsDomain
zkconnect=host3:2181,host4:2181,host5:2181 i=StreamsInstance]