Configure Monitoring for TIBCO

⚙️ Configuring Monitoring and Alerts for TIBCO with GermainUX

Configure GermainUX to collect and analyze JMX metrics and TIBCO Spotfire logs.

🔧 Configure TIBCO JMX Monitoring

📂 1. Open the JVM Wizard

Go to:

Germain Workspace -> Left Menu -> Settings --> Wizards -> JVM

Use the JVM Wizard to deploy the JMX monitoring component.

💻 2. Select the Node and Engine

Select the GermainUX node and Engine that will execute the monitor.

Choose an Engine that:

🎯 3. Select the Target

Select the:

Make sure the selected application and environment correctly identify the monitored TIBCO instance.

🔗 4. Configure the JMX Connection

Specify the JMX target URL.

When the connection is secured, configure the required credentials.

Verify:

🔬 5. Configure Java Profiling — Optional

If GermainUX Java Profiler will also be used, configure the applicable profiling thresholds.

Profiling should be enabled only when the additional Java execution detail is required.

✅ 6. Review and Submit

Review the JMX monitoring configuration.

Confirm:

Submit the configuration.

📃 Configure TIBCO Spotfire Log Monitoring

TIBCO Spotfire monitoring uses dedicated log parsers and a directory monitor.

Configure the parsers required for the Spotfire logs available in your environment.

📜 Spotfire Action Log

Deploy the:

Spotfire Action Log Parser

Select:

Review and submit the configuration.

🚤 Spotfire Performance Log

Deploy the:

Spotfire Performance Log Parser

Select:

Review and submit the configuration.

🖥️ Spotfire Server Log

Deploy the:

Spotfire Server Log Parser

Select:

Review and submit the configuration.

📁 Configure the Spotfire Log Directory Monitor

After configuring the required parsers, deploy the:

TIBCO Spotfire Log Directory Monitor

Configure:

Review and submit the configuration.

The Engine monitors the configured directory and processes supported Spotfire log files using the applicable parsers.

📊 Configure KPIs

Configure the KPIs required for your TIBCO monitoring use cases.

Depending on the monitoring source and TIBCO component, these can include KPIs for:

Use the KPIs available for the selected GermainUX monitoring component.

⏰ Configure SLAs

Configure SLA thresholds for conditions requiring attention.

Examples include:

🚫 Availability

TIBCO Component = Unavailable

🔌 JMX

JMX Connection = Unavailable

⚡ Performance

Response Time -> Expected Threshold

💾 JVM Memory

Memory Usage -> Expected Threshold

Errors

Error Count -> Expected Threshold

📈 Transactions

Transaction Failure Rate -> Expected Threshold

Use thresholds appropriate for each application and environment.

🧠 Configure Rules

Use GermainUX Rules for more advanced conditions.

Examples include:

Rules can correlate TIBCO telemetry with other monitoring data available in GermainUX.

🔔 Configure Alerts and Watches

Configure notifications for conditions requiring attention.

Examples:

GermainUX can trigger alerts, Watches, reports, diagnostics, or approved automation.

📊 Configure Dashboards

Create dashboards according to the monitored TIBCO environment.

⚙️ TIBCO Operations

Monitor:

🏭 JVM

Monitor:

📉 TIBCO Spotfire

Monitor:

🔗 Infrastructure

Correlate TIBCO telemetry with:

✅ Validate JMX Monitoring

After configuration, verify:

1. JMX monitor executes.

2. Connection succeeds.

3. Authentication succeeds.

4. JMX metrics are collected.

5. KPIs appear in GermainUX.

6. Expected values are populated.

7. SLA status is evaluated.

🔍 Validate Spotfire Log Monitoring

Generate or locate known Spotfire activity.

Verify:

1. Log files are generated.

2. Directory Monitor detects the files.

3. Correct parser processes each log type.

4. Events are generated in GermainUX.

5. Application and environment are correct.

6. Expected fields are populated.

7. Errors can be searched and analyzed.

🛠️ Troubleshooting

❓ No JMX Data

Verify:

❌ JMX Connection Fails

Verify:

⛔ Spotfire Logs Are Not Collected

Verify:

✨ Some Spotfire Events Are Missing

Verify that the appropriate parser is deployed for the relevant log type:

Review the source log to confirm that the expected event was actually written.

ℹ️ Get More Information

GermainUX can help determine which monitoring, analytics and automation capabilities are appropriate for your Tibco environment.

Contact GermainUX Support.