| 2021-03-28 23:18:39 |
Edin S |
bug |
|
|
added bug |
| 2021-03-28 23:28:26 |
Edin S |
description |
Apologies if this isn't the right project to file the bug against. If this is the case, please close this bug and direct me to a more appropriate project.
We've found a few cases where monitoring the the wellness of the systemd service "nova-api-metadata" to be inadequate in determining if the metadata service is working; the systemd service might be reported as active/running, but it may be failing to receive and respond to connections/requests.
I'd like to request a check for monitoring a metadata agent's health via the HTTP layer (e.g. make a request to http://169.254.169.254/ and potentially check for good values). I understand that there are complexities that arise from network namespaces, and scaling this solution to hundreds (or thousands) of networks -- but perhaps there's a middle ground that can be found. |
Apologies if this isn't the right project to file the bug against. If this is the case, please close this bug and direct me to a more appropriate project.
We've found a few cases (e.g. LP#1907686) where monitoring the the wellness of the systemd service "nova-api-metadata" to be inadequate in determining if the metadata service is working; the systemd service might be reported as active/running, but it may be failing to receive and respond to connections/requests.
I'd like to request a check for monitoring a metadata agent's health via the HTTP layer (e.g. make a request to http://169.254.169.254/ and potentially check for good values). I understand that there are complexities that arise from network namespaces, and scaling this solution to hundreds (or thousands) of networks -- but perhaps there's a middle ground that can be found. |
|
| 2021-03-31 22:29:20 |
Edin S |
description |
Apologies if this isn't the right project to file the bug against. If this is the case, please close this bug and direct me to a more appropriate project.
We've found a few cases (e.g. LP#1907686) where monitoring the the wellness of the systemd service "nova-api-metadata" to be inadequate in determining if the metadata service is working; the systemd service might be reported as active/running, but it may be failing to receive and respond to connections/requests.
I'd like to request a check for monitoring a metadata agent's health via the HTTP layer (e.g. make a request to http://169.254.169.254/ and potentially check for good values). I understand that there are complexities that arise from network namespaces, and scaling this solution to hundreds (or thousands) of networks -- but perhaps there's a middle ground that can be found. |
We've found a few cases (e.g. LP#1907686) where monitoring the the wellness of the systemd service "nova-api-metadata" to be inadequate in determining if the metadata service is working; the systemd service might be reported as active/running, but it may be failing to receive and respond to connections/requests.
I'd like to request a check for monitoring a metadata agent's health via the HTTP layer (e.g. make a request to http://169.254.169.254/ and potentially check for good values). I understand that there are complexities that arise from network namespaces, and scaling this solution to hundreds (or thousands) of networks -- but perhaps there's a middle ground that can be found. |
|
| 2021-03-31 22:30:45 |
Edin S |
bug |
|
|
added subscriber Canonical IS CREs |
| 2021-04-01 00:48:48 |
Edin S |
bug task added |
|
charm-neutron-openvswitch |
|
| 2021-04-01 09:53:54 |
Dorina Timbur |
bug |
|
|
added subscriber Dorina Timbur |
