Skip to main content
Mitratech Success Center
Client Support Center

Need help? Click a product group below to select your application and get access to knowledge articles, webinars, training content, and release notes or to contact our support team.

Authorized users - log in to create a ticket, view tickets status and check your success plan details.

 

TeamConnect Performance Monitor (TCE 8.0)

  1. Last updated
  2. Save as PDF
The TeamConnect Performance Monitor silently captures data in the background on all TeamConnect requests.

What changed in 8.0?

Starting with TeamConnect Enterprise (TCE) 8.0, the legacy TeamConnect Performance Monitor (jMonitor) is discontinued. For application performance monitoring and troubleshooting, use Glowroot (a lightweight, open‑source Java APM) with your TeamConnect application servers.

Why this matters: jMonitor (for example, accessing /jmonitor) was available in prior versions for request tracing and threshold-based logging. From 8.0 onward, you should transition to Glowroot to capture request traces, slow transactions, JVM metrics, and error details.

Required actions (Self‑hosted / On‑premises)

Glowroot is a third‑party, open‑source Java APM and is not bundled with TeamConnect; you install and manage it alongside your application server.

  1. Decide your Glowroot deployment mode Refer to the Glowroot installation docs linked below to choose the appropriate mode (external).

    • Embedded UI (simple, per‑node): suitable for single servers or quick diagnostics. By default, the UI binds to 127.0.0.1 on port 4000 (configurable in admin.json).

    • Central Collector (recommended for clusters): agents on each TCE node send data to a shared Glowroot Central, backed by Cassandra. Central UI defaults to port 4000; agents connect over HTTP/2 to port 8181 by default; Glowroot Central requires Cassandra 3.1+.

  2. Install the Glowroot agent on each TeamConnect application server

    • Download and place glowroot.jar, then add the JVM option: -javaagent:/path/to/glowroot.jar (see the Glowroot wiki for tips on where to set JVM arguments for your application server). For containerized deployments, ensure the glowroot/ directory is on persistent storage.

    • Restart the application server.

    • When running multiple agents on one host, set a unique agent id per JVM.

  3. Verify access

    • Embedded UI default: http://<server>:4000 (binds to 127.0.0.1 by default; bind address/port configurable in admin.json).

    • Central Collector: confirm agents are reporting to Glowroot Central and that dashboards show traffic. Agents report to the central collector at port 8181 by default (configurable).

Glowroot installation documentation (link out):

Security note: Restrict Glowroot UI access (e.g., bind address, reverse proxy, authentication/roles in the UI). Enable HTTPS for the UI by setting ui.https=true and providing ui-cert.pem and ui-key.pem. Review your organization’s security policies before exposing the UI beyond localhost.

Mitratech Cloud Services (Hosted) clients

If your TeamConnect 8.0 instance is hosted by Mitratech Cloud Services, please ask Support to submit a Change Control Form (CCF) to request Glowroot setup for your environment. When submitting, select the appropriate Hosting/Change Control request type in the Support case form (some organizations refer to this as the CCF process). In your request, include:

  • Client name and environment(s) (e.g., PROD, UAT)

  • Desired deployment mode (Embedded vs. Central Collector)

  • Any access restrictions or network details (e.g., required IP allow‑lists, desired port)

  • Proposed maintenance window

If you're a client admin and would like to setup Glowroot on your hosted instance, please open a general TeamConnect case and ask Support to route it to Hosting.

Support Portal: Contact Mitratech Support

Reminder: Do not expose Glowroot UI publicly. Work with Mitratech Support to configure appropriate access controls for hosted environments.

Notes for administrators

  • Remove any legacy procedures that reference jmonitor.properties or the /jmonitor endpoint in runbooks and dashboards.

  • Keep JVM Garbage Collection (GC) logging enabled per your standard practices; analyze GC logs alongside APM data when diagnosing performance.

  • For context on GC alongside monitoring, see the legacy Performance Monitor guidance on “Important information about Garbage Collection.”

Where to learn more

  1. Back to top
  • Was this article helpful?

Recommended articles

  1. Article type
    Topic
  2. Tags
    This page has no tags.