ikvrivis/docsportal_forked
1
0
Fork 0
forked from docs/docsportal
Code Pull Requests Activity

fixing the figure

Browse Source
This commit is contained in:
Hasko, Vladimir 2023-05-11 12:35:23 +00:00
parent 74469ae5da
commit 621fa7392b
1 changed files with 21 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
doc/source/internal/apimon_training/introduction.rst
View File

@ -26,6 +26,7 @@ The ApiMon a.k.a API-Monitoring project:
.. figure:: https://stackmon.github.io/assets/images/solution-diagram.svg
:figwidth: image
ApiMon Architecture Summary
---------------------------
@ -74,10 +75,24 @@ ApiMon comes with the following features:
What ApiMon is NOT:
The following items are out of scope (while some of them are technically possible):
The following items are out of scope (while some of them are technically
possible):
- No performance monitoring: The API-Monitoring does not measure degradations of performance per se. So measuring the access times or data transfer rates of an SSD disk is out of scope. However, if the performance of a resource drops under some threshold that is considered as equivalent to non-available, this is reported.
- No application monitoring: The service availability of applications that run on top of IaaS or PaaS of the cloud is out of scope.
- No view from inside: The API-Monitoring has no internal backplane insights and only uses public APIs of the monitored cloud. It requires thus no administrative permissions on the backend. It can be, however, deployed additionally in the backplane to monitor additionally internal APIs.
- No synthetic workloads: The service is not simulating any workloads (for example a benchmark suite) on the provisioned resources. Instead it measures and reports only if APIs are available and return expected results with an expected behaviour.
- No every single API monitoring .The API-Monitoring focuses on basic API functionality of selected components. It doesn't cover every single API call available in OTC API product portfolio.
- No performance monitoring: The API-Monitoring does not measure degradations of
performance per se. So measuring the access times or data transfer rates of an
SSD disk is out of scope. However, if the performance of a resource drops
under some threshold that is considered as equivalent to non-available, this
is reported.
- No application monitoring: The service availability of applications that run
on top of IaaS or PaaS of the cloud is out of scope.
- No view from inside: The API-Monitoring has no internal backplane insights and
only uses public APIs of the monitored cloud. It requires thus no
administrative permissions on the backend. It can be, however, deployed
additionally in the backplane to monitor additionally internal APIs.
- No synthetic workloads: The service is not simulating any workloads (for
example a benchmark suite) on the provisioned resources. Instead it measures
and reports only if APIs are available and return expected results with an
expected behaviour.
- No every single API monitoring .The API-Monitoring focuses on basic API
functionality of selected components. It doesn't cover every single API call
available in OTC API product portfolio.