Overview
Dashboards
Flopsar Environment Health
The Flopsar Environment Health dashboard offers a comprehensive overview of the Flopsar infrastructure’s health. It displays critical data regarding the status of various Flopsar components, such as servers and application instances. The dashboard uses visualizations like heatmaps and alert lists to help administrators quickly assess system health and identify any potential issues.

Flopsar Application Details
The Flopsar Application Details dashboard provides an in-depth view of Flopsar applications and their performance. It allows administrators to examine key metrics, such as invocation counts and duration, exception rates, for specific applications. The dashboard also offers detailed insights into resource usage, relationships, and associated alerts, helping users monitor application health, identify issues, and assess resource utilization within the environment.

Flopsar Server Details
The Flopsar Server Details dashboard offers comprehensive monitoring of Flopsar servers, providing insights into their health, performance, and resource usage. It includes a detailed list of servers, their relationships within the environment, and real-time active alerts for different issues. Additionally, the dashboard presents server capacity metrics and visualizes CPU and memory usage.

Collected objects
Relationships
In the 'Application Observability with Flopsar' management pack, the relationships between objects are essential for structuring and managing application and server monitoring data within Aria Operations. These relationships define how Flopsar components and virtual machine infrastructure are interconnected, allowing for a comprehensive view of system performance and health.
The relationship diagram illustrates a hierarchy that begins with the 'Flopsar Adapter Instance', which serves as the core component responsible for integrating data from the Flopsar system. The hierarchy then follows this structure:
- The 'Flopsar Adapter Instance' connects to the 'Flopsar Server', representing the servers being monitored within the Flopsar environment.
- From the 'Flopsar Server', the relationship branches into two key areas: 'Flopsar OTLP Application' and 'Flopsar Application', showing the applications and services managed by the Flopsar system.
- The 'Flopsar Application' then connects to the 'Flopsar Application Instance', representing individual application instances being monitored.
In addition to this, a separate set of relationships illustrates how the 'Virtual Machine' object from the vCenter Management Pack connects to the Flopsar components, specifically the 'Flopsar Server' and 'Flopsar Application Instance', emphasizing the role of virtual machines in the Flopsar monitoring environment.
Flopsar Server
Represents a Flopsar server within the monitored environment.
Data Name | Type | Description |
---|---|---|
Version | Property | The version of the Flopsar server. |
Hostname | Property | The hostname of the Flopsar server. |
Operating System | Property | The operating system running on the Flopsar server. |
Agent Server Socket Address | Property | The socket address of the Flopsar server agent. |
CPU Info | Property | Information about the CPU of the Flopsar server. |
CPU Frequency | Property | The frequency of the CPU in the Flopsar server. |
CPU Cores | Property | The number of CPU cores in the Flopsar server. |
Total Memory | Property | The total amount of memory in the Flopsar server. |
Statistics -> CPU usage | Metric | The CPU usage statistics for the Flopsar server. |
Statistics -> Memory usage | Metric | The memory usage statistics for the Flopsar server. |
Statistics -> Available space | Metric | The available disk space on the Flopsar server. |
Statistics -> Database size | Metric | The size of the database in the Flopsar server. |
Statistics -> Online agents | Metric | The number of online agents connected to the Flopsar server. |
Statistics -> Incomplete stacks | Metric | The number of incomplete stacks in the Flopsar server. |
Flopsar Application
Represents an application being observed by the Flopsar server.
Data Name | Type | Description |
---|---|---|
Exceptions -> Total | Metric | Total number of exceptions observed for the Flopsar application. |
Exceptions -> Percentage of invocations that resulted in exception | Metric | The percentage of invocations that resulted in an exception. |
Invocation count -> Total | Metric | Total number of invocations for the Flopsar application. |
Invocation count -> 5th percentile | Metric | Invocation count at the 5th percentile for the Flopsar application. |
Invocation count -> 10th percentile | Metric | Invocation count at the 10th percentile for the Flopsar application. |
Invocation count -> 25th percentile | Metric | Invocation count at the 25th percentile for the Flopsar application. |
Invocation count -> 50th percentile | Metric | Invocation count at the 50th percentile for the Flopsar application. |
Invocation count -> 75th percentile | Metric | Invocation count at the 75th percentile for the Flopsar application. |
Invocation count -> 90th percentile | Metric | Invocation count at the 90th percentile for the Flopsar application. |
Invocation count -> 95th percentile | Metric | Invocation count at the 95th percentile for the Flopsar application. |
Invocation count -> 96th percentile | Metric | Invocation count at the 96th percentile for the Flopsar application. |
Invocation count -> 97th percentile | Metric | Invocation count at the 97th percentile for the Flopsar application. |
Invocation count -> 98th percentile | Metric | Invocation count at the 98th percentile for the Flopsar application. |
Invocation count -> 99th percentile | Metric | Invocation count at the 99th percentile for the Flopsar application. |
Invocation count -> 100th percentile | Metric | Invocation count at the 100th percentile for the Flopsar application. |
Invocation duration -> 5th percentile | Metric | Invocation duration at the 5th percentile for the Flopsar application. |
Invocation duration -> 10th percentile | Metric | Invocation duration at the 10th percentile for the Flopsar application. |
Invocation duration -> 25th percentile | Metric | Invocation duration at the 25th percentile for the Flopsar application. |
Invocation duration -> 50th percentile | Metric | Invocation duration at the 50th percentile for the Flopsar application. |
Invocation duration -> 75th percentile | Metric | Invocation duration at the 75th percentile for the Flopsar application. |
Invocation duration -> 90th percentile | Metric | Invocation duration at the 90th percentile for the Flopsar application. |
Invocation duration -> 95th percentile | Metric | Invocation duration at the 95th percentile for the Flopsar application. |
Invocation duration -> 96th percentile | Metric | Invocation duration at the 96th percentile for the Flopsar application. |
Invocation duration -> 97th percentile | Metric | Invocation duration at the 97th percentile for the Flopsar application. |
Invocation duration -> 98th percentile | Metric | Invocation duration at the 98th percentile for the Flopsar application. |
Invocation duration -> 99th percentile | Metric | Invocation duration at the 99th percentile for the Flopsar application. |
Invocation duration -> 100th percentile | Metric | Invocation duration at the 100th percentile for the Flopsar application. |
Flopsar OpenTelemetry Application
Represents an OTLP (OpenTelemetry Protocol) application within the infrastructure.
Data Name | Type | Description |
---|---|---|
Exceptions -> Total | Metric | Total number of exceptions observed for the Flopsar OpenTelemetry application. |
Exceptions -> Percentage of invocations that resulted in exception | Metric | The percentage of invocations that resulted in an exception for the Flopsar OpenTelemetry application. |
Invocation count -> Total | Metric | Total number of invocations for the Flopsar OpenTelemetry application. |
Invocation count -> 5th percentile | Metric | Invocation count at the 5th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 10th percentile | Metric | Invocation count at the 10th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 25th percentile | Metric | Invocation count at the 25th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 50th percentile | Metric | Invocation count at the 50th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 75th percentile | Metric | Invocation count at the 75th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 90th percentile | Metric | Invocation count at the 90th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 95th percentile | Metric | Invocation count at the 95th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 96th percentile | Metric | Invocation count at the 96th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 97th percentile | Metric | Invocation count at the 97th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 98th percentile | Metric | Invocation count at the 98th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 99th percentile | Metric | Invocation count at the 99th percentile for the Flopsar OpenTelemetry application. |
Invocation count -> 100th percentile | Metric | Invocation count at the 100th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 5th percentile | Metric | Invocation duration at the 5th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 10th percentile | Metric | Invocation duration at the 10th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 25th percentile | Metric | Invocation duration at the 25th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 50th percentile | Metric | Invocation duration at the 50th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 75th percentile | Metric | Invocation duration at the 75th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 90th percentile | Metric | Invocation duration at the 90th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 95th percentile | Metric | Invocation duration at the 95th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 96th percentile | Metric | Invocation duration at the 96th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 97th percentile | Metric | Invocation duration at the 97th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 98th percentile | Metric | Invocation duration at the 98th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 99th percentile | Metric | Invocation duration at the 99th percentile for the Flopsar OpenTelemetry application. |
Invocation duration -> 100th percentile | Metric | Invocation duration at the 100th percentile for the Flopsar OpenTelemetry application. |
Flopsar Application Instance
Represents an individual instance (agent) of the application observed by the Flopsar server.
Data Name | Type | Description |
---|---|---|
PID | Property | The Process ID (PID) of the Flopsar application instance. |
Hostname | Property | The hostname of the Flopsar application instance. |
ID | Property | The unique identifier for the Flopsar application instance. |
Connection time | Property | The time when the Flopsar application instance connected. |
Startup time | Property | The time when the Flopsar application instance started. |
Agent version | Property | The version of the Flopsar agent running in the application instance. |
Loaded Extensions | Property | The list of extensions loaded into the Flopsar application instance. |
CPU cores | Property | The number of CPU cores allocated to the Flopsar application instance. |
CPU | Property | The CPU model and specifications used by the Flopsar application instance. |
Memory installed | Property | The amount of memory installed in the Flopsar application instance. |
JVM -> Name | Property | The name of the Java Virtual Machine (JVM) used by the application instance. |
JVM -> Version | Property | The version of the Java Virtual Machine (JVM) used by the application instance. |
JVM -> Vendor | Property | The vendor of the Java Virtual Machine (JVM) used by the application instance. |
Features -> CPUTime | Property | The CPU time feature of the Flopsar application instance. |
Features -> Heap | Property | The heap feature of the Flopsar application instance. |
Features -> Threads | Property | The thread count feature of the Flopsar application instance. |
Instrumented methods | Metric | The number of instrumented methods for the Flopsar application instance. |
Errors | Metric | The number of errors observed in the Flopsar application instance. |
CPU usage | Metric | The CPU usage statistics for the Flopsar application instance. |
System memory usage | Metric | The system memory usage statistics for the Flopsar application instance. |
JVM heap memory usage | Metric | The JVM heap memory usage for the Flopsar application instance. |
JVM threads | Metric | The number of threads in the JVM used by the Flopsar application instance. |
Total data sent | Metric | The total amount of data sent by the Flopsar application instance. |
Dropped invocations | Metric | The number of dropped invocations in the Flopsar application instance. |
Alerts
The alerts of the 'Application Observability with Flopsar' management pack help monitor key system parameters by providing notifications when specific thresholds are exceeded. These alerts track essential metrics such as storage space, database size, exceptions, CPU usage, and more, enabling administrators to quickly identify and address potential issues.
Flopsar Server Available Space is Low
- Flopsar Server Available Space is Low 5%: If Available space (GiB) ≤ 10, trigger Critical.
- Flopsar Server Available Space is Low 10%: If Available space (GiB) ≤ 20, trigger Warning.
Flopsar Server Database Size Increase
- Flopsar Server Database Size Increase: If Database size (GiB) above threshold, trigger Critical.
Flopsar Application More Than 0 Exceptions
- Flopsar Application More Than 0 Exceptions: If Total Exceptions > 0, trigger.
Flopsar Server CPU Usage is High
- Flopsar Server CPU Usage 90%: If CPU usage (%) > 90, trigger Critical.
- Flopsar Server CPU Usage 85%: If CPU usage (%) > 85, trigger Warning.
Flopsar Application Invocation Count and Invocation Duration on 95th Percentile is High
- Flopsar Application Invocation Duration on 95th Percentile is High (ms): If Invocation duration 95th percentile (ms) > 5, trigger Critical.
- Flopsar Application Invocation Count on 95th Percentile is High: If Invocation count 95th percentile (ms) > 5000, trigger Critical.