A lightweight tool for searching Hadoop jobs, visualizing performance, and viewing cluster utilization.
Inviso is a lightweight monitoring tool for Hadoop clusters that provides search capabilities for job histories, performance visualization, and cluster utilization tracking. It helps administrators and developers understand cluster behavior, debug performance issues, and optimize resource allocation.
Hadoop cluster administrators and data engineers who need to monitor job performance, troubleshoot issues, and analyze cluster resource usage in Hadoop 2 environments.
Developers choose Inviso for its lightweight design, easy deployment, and integrated search and visualization features that simplify Hadoop cluster observability without requiring complex monitoring systems.
Inviso is a lightweight monitoring and visualization tool designed for Hadoop clusters. It enables administrators and developers to search through job histories, analyze performance metrics, and monitor cluster resource utilization through an intuitive web interface.
Inviso prioritizes simplicity and lightweight deployment, providing essential Hadoop cluster observability without heavy infrastructure overhead.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
The QuickStart guide outlines a straightforward setup process, and a Docker image is available for even easier deployment, minimizing infrastructure overhead.
ElasticSearch integration enables efficient querying and correlation of Hadoop job histories, specifically tailored for Pig and Hive scripts as noted in the README.
When Hadoop log aggregation is enabled, Inviso provides direct links to task logs for in-depth debugging, enhancing troubleshooting capabilities.
Python scripts support pub/sub models for distributed event handling, allowing integration with queuing services like SQS to scale indexing workloads.
Requires specific versions of JDK, Tomcat, ElasticSearch, and Hadoop 2 with log aggregation, making setup heavy and prone to compatibility issues, especially with older components like ElasticSearch 1.3.2.
Primarily designed for Hadoop 2, with Hadoop 1 requiring more configuration and no mention of support for other big data frameworks like Spark or Flink.
Indexing scripts must be run in loops or cron jobs, as shown in the QuickStart, requiring ongoing manual intervention to keep data up-to-date and lacking automated scheduling.