The returned measurements shall be ordered from oldest to newest.
Initial implementation
com.fanitas.evelyn.core.impl.ref.EvelynImpl shall initially return hardcoded sample data. Real index calculation and persistence are outside this issue.
The sample data shall contain enough measurement points to make all six graph lines visible.
Chart behavior
The X-axis represents time.
The Y-axis represents index values.
The Y-axis range is dynamic.
Zero must always be visible.
The Y-axis should be symmetric around zero.
The chart displays one series for each of the six indices.
Data is loaded when the Overview view is created.
Out of scope
Real index calculation
Persisting historical measurements
Periodic or live refresh
Editing data
Automated tests
Additional Overview widgets
## Background
Evelyn Mission Control currently has no useful content in its Overview tab.
Evelyn exposes a textual status report through:
```java
com.fanitas.evelyn.core.Evelyn.getStatusReport()
```
The textual report is not suitable for presenting historical system-health indices in a graph.
## Goal
Display a time-series chart in the Evelyn Mission Control Overview tab.
The chart shall contain six lines:
1. Evelyn Price Index
2. EVE_SYRUP Pool Depth Index
3. EVE_SYRUP Pool Balance Index
4. AAZDKK_USDT Pool Balance Index
5. AAZDKK_USDT Pool Price Index
6. AAZDKK_USDT Pool Depth Index
For all indices, zero represents the desired state. Values farther from zero represent a worse state.
## API
Replace the textual status-report API with a typed historical status-index API.
Introduce a value type representing one measurement point with:
* Timestamp
* Evelyn Price Index
* EVE_SYRUP Pool Depth Index
* EVE_SYRUP Pool Balance Index
* AAZDKK_USDT Pool Balance Index
* AAZDKK_USDT Pool Price Index
* AAZDKK_USDT Pool Depth Index
Expose the history through:
```java
List<EvelynStatusIndexPoint> getStatusIndexHistory()
```
The returned measurements shall be ordered from oldest to newest.
## Initial implementation
`com.fanitas.evelyn.core.impl.ref.EvelynImpl` shall initially return hardcoded sample data. Real index calculation and persistence are outside this issue.
The sample data shall contain enough measurement points to make all six graph lines visible.
## Chart behavior
* The X-axis represents time.
* The Y-axis represents index values.
* The Y-axis range is dynamic.
* Zero must always be visible.
* The Y-axis should be symmetric around zero.
* The chart displays one series for each of the six indices.
* Data is loaded when the Overview view is created.
## Out of scope
* Real index calculation
* Persisting historical measurements
* Periodic or live refresh
* Editing data
* Automated tests
* Additional Overview widgets
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Background
Evelyn Mission Control currently has no useful content in its Overview tab.
Evelyn exposes a textual status report through:
The textual report is not suitable for presenting historical system-health indices in a graph.
Goal
Display a time-series chart in the Evelyn Mission Control Overview tab.
The chart shall contain six lines:
For all indices, zero represents the desired state. Values farther from zero represent a worse state.
API
Replace the textual status-report API with a typed historical status-index API.
Introduce a value type representing one measurement point with:
Expose the history through:
The returned measurements shall be ordered from oldest to newest.
Initial implementation
com.fanitas.evelyn.core.impl.ref.EvelynImplshall initially return hardcoded sample data. Real index calculation and persistence are outside this issue.The sample data shall contain enough measurement points to make all six graph lines visible.
Chart behavior
Out of scope