Skip to content
Ivan Senic's fork of the inspectIT core repository
Branch: master
Clone or download
Pull request Compare This branch is 14 commits behind inspectIT:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.settings
gradle/wrapper
inspectit.agent.java.sdk
inspectit.agent.java
inspectit.server.diagnosis
inspectit.server
inspectit.shared.all
inspectit.shared.cs
inspectit.ui.rcp
license
resources
.gitignore
.project
README.md
build.gradle
dependencies.gradle
gradlew
gradlew.bat
inspectit.root.gradle
platform.gradle
properties.gradle
settings.gradle

README.md

Website Twitter Account Gitter LinkedIn Group YouTube Build Status License

Overview

inspectIT is the leading Open Source APM (application performance management) tool for monitoring and analyzing your Java(EE) software applications.

Various sensors capture end-to-end information for every request from the end user, to the business tier all the way to the backends. inspectIT is based on an application-centric, business-focused approach, where each technical request is mapped to an application and to a business use-case. With inspectIT you always know about the health of your software and can easily analyze any problems that arise.

For Web applications the tool integrates the End user monitoring using automatic JavaScript agent injection. This allows easy monitoring of the performance that real users are facing in the browser. In addition, the inspectIT can correlate all user actions in the browser to the backend traces, thus providing a complete picture on the user experience.

We hope that together we can build an alternative to the (great!) commercial tools available so that it is up the end user to choose his tooling. Let's make inspectIT even more awesome!

Features

See all requests Trace-based analysis Remote traces Details (SQL)
Details (Exceptions) Sensor configuration Business context Alerting
Monitoring dashboards EUM Summary EUM Single Page EUM 3rd Party Content
  • Browser end user monitoring: automatic injection of a JavaScript agent into your application HTML code.
  • Detailed trace representation (invocation sequence) for every request containing all interactions with the systems.
  • Support for inter-JVM communication based on HTTP and JMS: each trace shows interaction with all correlated JVMs.
  • Automatic enrichment of every trace with HTTP information, SQL queries, exceptions, parameters and many more.
  • Detailed exception capturing allows to analyze functional problems.
  • Drill down into one invocation sequence to find and analyze problematic requests.
  • Drill up from an problem within an invocation sequence and find business-related information like the URL the request was sent to.
  • Aggregated views for every captured metric, e.g. aggregated SQL overview shows metrics aggregated by SQL query.
  • Talk in invocation sequences! Store, import and export detailed traces with all information instead of noting down which clicks lead to a problem.
  • Monitor your hardware metrics like cpu, memory or threads.
  • Monitor metrics exposed via JMX beans.
  • Dynamic instrumentation - change measurement points on the monitored JVM without a need for a restart.
  • Have a view on your applications and business transactions by using flexible business context definition.
  • Integration with influxDB and Grafana for easy monitoring with pre-defined dashboards.
  • Simple e-mail alerting is possible on all long-term monitoring data.
  • No more config files! We have graphical configuration interfaces for everything.
  • Provides SDK that implements opentracing.io API. All user spans are combined with inspectIT measurements in a trace.
  • Easy and transparent integration of the inspectIT agents in the application.
  • Reproducing problems is a thing of the past! You already have a trace representation that you can analyze.
  • Optimized for low overhead.
  • Production-proof: Used for >8 years at our customers and during performance firefights.
  • One server is enough for most environments supporting a big number of agents.
  • RESTful API for automation and integration with other tools.
  • Fully adaptable user interface.
  • Extensible system: Missing something? Write your own extensions.

End user monitoring

⚠️ Experimental

The inspectIT 1.8 line comes with a new feature: Browser End User Experience Monitoring (EUM). This feature allows you to measure the performance at the browser side of the end user, giving more detailed insights than the back-end instrumentation alone. This is done by automatically injecting a JavaScript agent into your applications HTML code, which in turn captures relevant metrics at the client-side and sends them back to inspectIT using AJAX Requests. Check the official feature documentation to help you started.

Out-of-the-box profiles

inspectIT already ships with out-of-the-box instrumentations for commonly used Java technologies. If your technology is missing, you can easily instrument it manually (or request a new profile). We currently support:

  • JavaEE
    • Enterprise Java Beans (EJB)
    • Java Server Faces (JSF)
    • Java Transaction API (JTA)
    • Servlets API
    • WebServices
    • WebSockets
  • Java Persistence
    • JDBC
    • JPA
    • Hibernate
  • Remote communication
    • HTTP
    • JMS
  • Other
    • Apache Struts
    • Apache MyFaces Trinidad

Supported application platforms

  • IBM WebSphere
  • Oracle Weblogic
  • JBoss / Wildfly
  • Tomcat
  • Jetty
  • Glassfish
  • Resin
  • ..
  • and any plain java application

Project structure

Project Description
inspectit.agent.java Agent for instrumenting and monitoring Java 6+ applications.
inspectit.agent.java.sdk Java SDK that implements opentracing.io API.
inspectit.server Server component know as Central Measurement Repository (CMR).
inspectit.server.diagnosis Component for automatic performance problems diagnosis (see diagnoseIT project).
inspectit.shared.all Classes shared between all projects.
inspectit.shared.cs Classes shared between server and UI projects.
inspectit.ui.rcp inspectIT user interface based on Eclipse RCP.

Related projects

  • Experimental features and supporting components of inspectIT are located at inspectIT Labs
  • Our Docker integration projects are located at inspectIT Docker

Integration

The integration of inspectIT in your application is completely transparent, you do not have to change a single line of code. The only thing you have to do is to place our agent with your application and integrate it into your startup script.

The integration is as simple as adding the following to the startup of your application.

-javaagent:[INSPECTIT_AGENT_HOME]/inspectit-agent.jar -Dinspectit.repository=[REPOSITORY_IP]:[REPOSITORY_PORT] -Dinspectit.agent.name=[AGENT_DISPLAY_NAME]

The end user documentation provides in-depth documentation on the installation of inspectIT for all supported platforms. If you have further questions please get in touch with us.

Getting started

Download

Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls Docker Pulls

You can get inspectIT in three ways:

Try it out with a demo application

You can easily test the inspectIT features by starting out the demo based on the Spring Petclinic application. The repository inspectit-labs/spring-petclinic-microservices contains start-up and docker scripts that integrate the inspectIT into the famous Spring demo app. Also check the inspectit-labs/workshop for the in-detail step-by-step workshop that will walk you through using inspectIT with the demo application.

Get in touch

Twitter Account Gitter LinkedIn Group

We are interested in your feedback. Come chat with us and other users on Gitter. Visit the forum or simply drop us a line. You also might want to follow us at Twitter @inspectIT_apm or join discussions in our LinkedIn group.

Documentation

We are running an Atlassian Confluence for all sorts of documentation (thanks to Atlassian for the free license): From end user documentation to the road-map.

Contribute

You do not have to be a programmer to contribute to inspectIT, but if you are you are certainly welcome. Here is a short list of how you can contribute. Please see our Contribution Documentation

Developers

If you want to fix Bugs or implement Features on your own, you're very welcome to do so! For the easiest start, you just need to follow our Development Environment Documentation for installing Eclipse with all projects and settings already pre-configured via the new official Oomph installer.

Ticketing

We primarily use Atlassian JIRA for ticketing. But if you are in a hurry, please feel free to open a GitHub issue.

Licensing

inspectIT is licensed under Apache License version 2.0. Please see our licensing documentation for more details. (Note that releases up to 1.6.7 were licensed using AGPLv3)

Commercial support

If you need the commercial support for the inspectIT please check the transparent package offering by NovaTec Consulting GmbH and feel free to contact us if you are interested.

Sponsoring

inspectIT is mainly driven by NovaTec Consulting GmbH, a German consultancy firm that specializes in software performance. Sponsoring a feature in inspectIT is always possible and welcome. Just get in touch with us through Sponsor a feature.

Research / Further readings

inspectIT is the base for the research project diagnoseIT, sponsored by German federal ministry of education and research with more than 500.000€.

You can’t perform that action at this time.