Home
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
Troubleshooting services and diagnostic tools
Teracloud® Streams provides log and trace services and troubleshooting tools that can help you resolve the issues that you encounter when you work with the product.
Managing log and trace data
Teracloud® Streams generates log and trace data that can help you to identify, diagnose, and resolve problems with the Teracloud Streams product and applications.
Customizing logging and tracing
Teracloud® Streams provides domain and instance properties that you can use to customize logging and tracing.
Log and trace properties
Teracloud® Streams provides log and trace properties for domains and instances that apply to all or specific Teracloud Streams services.
Trace properties for services
These trace properties apply to specific services in an Teracloud® Streams domain or instance. Updates to these properties are dynamic. You do not need to restart the domain or instance for the changes to take effect.

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.
Administering
Administer the product by using the Teracloud® Streams graphical user interface, APIs, or the streamtool command-line interface.
Developing
Develop stream applications with the Streams Processing Language (SPL), Java, and Python.
Troubleshooting
Resolve problems with Teracloud® Streams using the troubleshooting tools provided with the product as well as the resources offered by Teracloud Support.
- Before contacting Teracloud® Support
  Review this information before you contact Teracloud® Support. These resources might help you to find possible solutions for your issue, or make your support experience more efficient if you need to contact Teracloud Support.
- Troubleshooting techniques
  Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as you expect it to work, and then decide how to resolve the problem.
- Known problems and solutions
  Use the solutions that are provided to resolve known problems that you might encounter when you work with different components of the product.
- Troubleshooting services and diagnostic tools
  Teracloud® Streams provides log and trace services and troubleshooting tools that can help you resolve the issues that you encounter when you work with the product.
  - Log and trace services
    The default log and trace service for Teracloud® Streams logs events and messages in rolling log files on each resource. Because the logs are distributed across the cluster, use the streamtool getlog command to collect the logs from each resource for easy examination.
  - Managing log and trace data
    Teracloud® Streams generates log and trace data that can help you to identify, diagnose, and resolve problems with the Teracloud Streams product and applications.
    - Log and trace files
      By default, Teracloud® Streams generates log and trace files for the domain and instance services and applications. Administrators, instance owners, application developers, and Teracloud Support can use this data to correct problems with Teracloud Streams.
    - Customizing logging and tracing
      Teracloud® Streams provides domain and instance properties that you can use to customize logging and tracing.
      - Log and trace properties
        Teracloud® Streams provides log and trace properties for domains and instances that apply to all or specific Teracloud Streams services.
        Global log and trace properties
        Global log and trace properties apply to all Teracloud® Streams services. The domainLog.level property also applies to stream applications.
        Trace properties for services
        These trace properties apply to specific services in an Teracloud® Streams domain or instance. Updates to these properties are dynamic. You do not need to restart the domain or instance for the changes to take effect.
      - Modifying log and trace properties
        You can use the streamtool command-line interface or the Teracloud® Streams graphical user interfaces to modify settings for Teracloud Streams log and trace properties.
      - Changing the default location of log and trace files
        The default root directory for the log and trace files that are generated by Teracloud® Streams is the /tmp directory. To configure a different root directory, update the domainLog.path domain property by using the streamtool setdomainproperty command.
      - Logging events and messages in the Linux™ system log
        By default, Teracloud® Streams logs events and messages in rolling log files on each resource. You can use this procedure to configure Teracloud Streams to log events and messages in the Linux™ system log.
  - Diagnostic tools
    Teracloud® Streams provides a set of diagnostic tools that can help you troubleshoot problems.
- Teracloud® Streams messages
  The Teracloud® Streams messages describe the errors and solutions, warnings of potentially problematic conditions, and helpful information that you can use to troubleshoot the problems that can occur when you work with the product. These messages are displayed in the user interfaces and log files.
Reference
Find details on the SPL language, toolkits, APIs, commands, and more.
Glossary
Use this glossary to find terms and definitions for Teracloud® Streams.

Trace properties for Teracloud® Streams domain and instance services

These trace properties apply to specific services in an Teracloud® Streams domain or instance. Updates to these properties are dynamic. You do not need to restart the domain or instance for the changes to take effect.

You can modify trace properties by using the streamtool command-line interface or the Streams Console.

By default, the trace properties for services default to the trace properties for the domain or instance. For example, the default value for the controller.traceLevel domain property is the domainTrace.defaultLevel property value, which is error.

Other possible runtime service trace level values are:

trace
debug
info
warn
error
off

These options are in order, highest to lowest level, with a setting of trace generating the largest amount of data.

The following table lists the trace properties for domain and instance services. For more information about these properties, use the following commands:

streamtool man domainproperties for information about domain properties
streamtool man properties for information about instance properties

Table 1. Domain and instance service trace properties for Teracloud® Streams
This table lists the domain and instance property name and description.
Property name	Description
auditlog.traceLevel domain property	Tracing level for the logging service.
data.traceLevel domain property	Tracing level for the data service.
controller.traceLevel domain property	Tracing level for the domain controller service.
jmx.traceLevel domain property	Tracing level for the JMX management API service.
rest.traceLevel domain property	Tracing level for the REST management API service.
sws.traceLevel domain property	Tracing level for the web management service.
app.traceLevel instance property	Tracing level for the application deployment service.
hc.traceLevel instance property	Tracing level for the domain controller service.
hc.pecTraceLevel instance property	Tracing level for the processing element container service.
sam.traceLevel instance property	Tracing level for the application manager service.
srm.traceLevel instance property	Tracing level for the application metrics service.
view.traceLevel instance property	Tracing level for the view service.