Monitoring infrastructure

Instana ensures that at any time the infrastructure is monitored and represented as it is. All issues and changes that are detected on the infrastructure are constantly related to any occurring issues and incidents on the application and end user level. In this way, you can have a comprehensive understanding of all parts that deliver the application.

Infrastructure - physical, virtual, cloud, hybrid, containerized - is the underlying layer to provide the relevant resources and services for applications. There are several challenges when monitoring infrastructure:

Monitoring software installation needs to scale and be low maintenance:

  • Discover all relevant components with their configuration, and ensure that the data is current;
  • Track changes;
  • Relate infrastructure issues to application impact, and vice versa.

Especially in modern architectures the infrastructure is constantly changing and leverages concepts like clustering and autoscaling to ensure reliability, scaling, and flexibility.

To know more about how to monitor infrastructure with Instana, see the following topics:

Limitations

  • Negative metric values are not displayed.
  • Instana now supports ingestion of more than 3000 metrics per entity, with some restrictions:
    • The BeeInstana component must be active. BeeInstana is active for all Instana SaaS deployments, but is not active by default in all self-hosted installs.
    • Tagged metrics that exceed the former 3000 limit can be viewed in Analyze Infrastructure, or in custom dashboards. A tagged metric is defined as a metric that uses one or more key-value pairs to further identify the origin of the metric.
    • Curated dashboards might not display all metrics for entities. Entity metric ingestion of nontagged metrics is limited to 3000 metrics per time interval for performance reasons.