Enhance server monitor functionality by adding serverMonitorResponse handling and improving hostname resolution

This commit is contained in:
Simon Larsen
2024-12-20 15:48:32 +00:00
parent 32ffdf9174
commit c8a966a2f7
3 changed files with 5 additions and 3 deletions

View File

@@ -418,6 +418,7 @@ export default class MonitorResourceUtil {
logger.debug(
`${dataToProcess.monitorId.toString()} - Processing monitor step...`,
);
response = await MonitorResourceUtil.processMonitorStep({
dataToProcess: dataToProcess,
monitorStep: monitorStep,

View File

@@ -41,7 +41,7 @@ for i in "${!BINARIES[@]}"; do
ARCH="${ARCHES[$i]}"
WXS_INPUT_FILE="./windows/app-$ARCH-template.wxs"
WXS_OUTPUT_FILE="./windows/app-$ARCH.wxs"
MSI_FILE="$OUTPUT_DIR/$APP_NAME-$APP_VERSION-$ARCH.msi"
MSI_FILE="$OUTPUT_DIR/$APP_NAME-$ARCH.msi"
# log binary and arch
echo "Building MSI for binary: $BINARY and arch: $ARCH"

View File

@@ -32,6 +32,7 @@ RunCron(
monitorSteps: true,
serverMonitorRequestReceivedAt: true,
createdAt: true,
serverMonitorResponse: true,
},
limit: LIMIT_MAX,
skip: 0,
@@ -53,8 +54,8 @@ RunCron(
monitorId: monitor.id!,
onlyCheckRequestReceivedAt: true,
requestReceivedAt:
monitor.serverMonitorRequestReceivedAt || monitor.createdAt!,
hostname: "",
monitor.serverMonitorRequestReceivedAt || monitor.serverMonitorResponse?.requestReceivedAt || monitor.createdAt!,
hostname: monitor.serverMonitorResponse?.hostname || "",
};
await MonitorResourceUtil.monitorResource(serverMonitorResponse);