The IBM Instana Observability documentation clearly defines several operating modes for the host agent, with  INFRASTRUCTURE  mode dedicated exclusively to monitoring system-level performance data. The verified extract states: "INFRASTRUCTURE mode configures the host agent to monitor the underlying host metrics and activate sensors for the technologies running on that host without tracing application-level transactions." It collects CPU, memory, disk, network metrics, and technology integrations like Docker or OS sensors while ignoring application instrumentation. This mode reduces overhead in environments that demand system observability without full APM tracing.  APM  mode, conversely, extends to application traces and requests. Cloud-specific modes such as  AWS  or  ARM  designate external monitoring integrations rather than agent behavior. INFRASTRUCTURE mode thus provides base telemetry visibility as per documented design and was verified in both formulations of the Instana agent guides (v1.0.277, v1.0.307).

According to IBM Instana Observability (v1.0.307 and earlier), stanctl cluster backup is a built-in utility and command-line tool to back up system state and operational data from an Instana cluster. The verified procedure reads: "stanctl cluster backup saves configuration, operational state, and selected monitoring data into an archive file located in the current working directory." This archive is designed for disaster recovery and migration, containing all crucial files needed for restoring Instana to a consistent state. Disk snapshots (A) are separate and handled by storage appliances. Option B describes pre-backup preparation rather than the actual result. Remote backup (C) operations require remote execution configuration and are not part of the default cluster backup. Thus, D is correct as per documentation, which emphasizes bringing together all cluster backup data in a portable .tar or .zip archive for safe storage or transfer.

As outlined in the Instana agent deployment documentation, the default log level for gathering Log4j syslog information is Info . The documentation reads: "The default log level for syslog collection in Instana agents with Log4j integration is Info, enabling monitoring of operational and sensor activity without excessive diagnostic output." Info level is chosen as a best-practice default to log key events like agent startup, sensor activations, and health check results. Debug, Warning, and Error thresholds are for troubleshooting or failure analyses and may be set manually for deep inspection but are not preselected at install. Optimal Info-level logging ensures administrators receive actionable messages without burdening disk or log forwarding pipelines. Configuration files can be adjusted for verbose output; however, initial deployments and automated frameworks always rely on Info as the default value.

BeeInstana is identified in Instana’s documentation as the core Kubernetes operator driving distributed installation and management of Instana components. The documentation defines: "BeeInstana is a Kubernetes operator that requires robust, high-performing distributed data stores and manages Instana deployment complexity, resource allocation, and scaling within large clusters." By leveraging Kubernetes-native constructs, BeeInstana orchestrates Instana backend, UI, sensors, and streaming components—ensuring reliable, scalable deployments for enterprise settings. The operator orchestrates failover, recovery, and persistent storage management, supporting self-hosted and hybrid installations. While it is associated with metric data handling, its main role is orchestration and operational management based on distributed database infrastructures. Simple operator installation (A, D) does not capture its full role, and describing BeeInstana as only a metric database (B) misrepresents its architectural function in Instana’s platform lifecycle.

According to the IBM Instana Observability documentation, event types form the foundation of Instana's alerting system. When configuring new alerts, users can select event categories such as  Incidents ,  Offline , or  Changes . The documentation specifies: "Instana alerts are triggered by event conditions derived from incidents (performance degradations), offline detections (component unavailability), and changes (deployment or configuration actions)." Incidents indicate performance or reliability degradation impacting users, Offline events represent disconnected sensors or hosts, while Changes capture deployments or configuration modifications influencing performance. Combining these event types enables contextual alerts and reduces noise by differentiating between symptoms and root causes. Other listed options refer either to data processing concepts (Timers, Counters) or monitoring inputs (Requests, Tracing), not supported as Instana alert event types. These verified categories are consistent across versions 1.0.277 through 1.0.307.

IBM Instana leverages the open-source and widely recognized GeoLite2 database for mapping user IP addresses to their approximate physical locations in synthetic and real user monitoring scenarios. The documentation details: "Instana provides geographical and location metadata based on the GeoLite2 database, which is regularly updated for improved accuracy and privacy compliance." GeoLite2 is a MaxMind-developed database providing country, city, region, and sometimes ISP-level information from IP addresses. Using an on-premise and regularly-curated geo database ensures no end-user data is ever transmitted to external or third-party web mapping services (such as Google Maps), maintaining strong data privacy and compliance for enterprise customers. Other listed tools are not native to Instana’s geo lookup implementation.

According to the IBM Instana Observability documentation, an air-gapped installation is required when your environment is disconnected from the internet or has no access to external networks. The documentation states: "Air-gapped and restricted environments require deploying Instana without any connection to public repositories or backend services, assuring full isolation for compliance and regulatory requirements." The air-gapped setup ensures sensitive data or system configurations are never exposed outside the organization's internal trusted boundaries, making it mandatory for government, defense, or tightly regulated industries. Standard installation processes, including auto-update features and remote license verification, are replaced in air-gapped deployments with manual artifact and key management, as file transfers and package updates must be handled strictly within the controlled environment. The option described in B (high-speed internet) or D (unrestricted internal transfer) does not trigger air-gapping, while option A may require proxy or firewall configuration but is not entirely air-gapped unless full external access is blocked.

IBM Instana Observability documentation makes it clear that, when integrating many IBM APM v8 agents with a single Instana Agent host, it is highly recommended to increase the JVM memory allocation of the Instana host agent. The official guidance is: "If integrating several hundred APM v8 agents with a single Instana host agent, make sure to increase the Java Virtual Machine (JVM) heap size on the Instana host agent, as the default settings may not suffice for the heightened metric ingestion and processing load." Without this adjustment, the host agent could experience memory pressure, leading to dropped metrics, agent restarts, or degraded ingestion. This step is essential for scaling and ensuring metric reliability in high-volume environments, as detailed in the agent performance tuning and scalability section of IBM’s documentation. Other options (A, B, D) do not address the resource requirements driven by metric collection at scale.

IBM Instana integrates natively with Prometheus to unify metric ingestion without disrupting existing telemetry setups. The configuration parameter remote_write enables this linkage. The official documentation states: "The remote_write configuration enables Prometheus to send data to Instana, where those metrics are displayed either as Prometheus entities or merged into process custom metrics." Instead of storing them only within Prometheus, Instana pulls remote_write relay feeds to create comprehensive, unified metrics views in its dashboard. This approach avoids duplicate monitoring systems and allows alerting across both Prometheus and Instana data seamlessly. The parameter does not configure outbound writing by Instana back into Prometheus—data always flows from Prometheus to Instana in this architecture. This integration respects Prometheus scraping principles yet centralizes analysis within Instana, achieving correlation between imported numerical time-series values and native metrics at the application or process layer.

IBM Instana documentation describes automated event management for Synthetic Points of Presence (PoP). When a Synthetic PoP is uninstalled or goes offline, Instana's event model will automatically trigger the "Synthetic pop status" event. The verified statement found in the latest docs: "The ‘Synthetic pop status’ built-in event automatically triggers when a Synthetic PoP is uninstalled or taken offline, notifying administrators for actionable response." No manual intervention or custom rule creation is needed (A, B), and default event logic already covers all offline or removal states so configuration changes (D) aren't necessary. This ensures real-time visibility for operational teams to maintain synthetic coverage, immediately alerting when synthetic endpoint monitoring is compromised or reconfigured. Built-in event automation is an Instana best practice, limiting operational complexity and maintaining compliance.