JpBIT
-
Posts
2 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by JpBIT
-
-
I am creating a C# program to fetch the "Last Boot Uptime" for all devices under a particular group with /v3/assets
But the time format is inconsistent for some devices. Some are in 24hr format others in 12hr format, some has the weekday on it etc..
Eg:
15 February 2024 21:58
22 February 2024 08:57
12 March 2024 08:24
18 March 2024 01:33
17 February 2024 02:11
15 February 2024 21:50
11 March 2024 15:08
17 February 2024 02:44
29 February 2024 00:36
16 March 2024 00:33
16 March 2024 01:29
06 February 2024 15:24
13 March 2024 08:46
Saturday, 2 March 2024 10:12 a.m.
Thursday, 14 March 2024 1:36 AM
Saturday, February 24, 2024 20:02
Thursday, 14 March 2024 11:08 pmMost of the result are in dd MMMM yyyy HH:mm format.
Except once pc all others are windows. I checked the datetime format in windows for two PC's that had different boot up time format in REST API result but both windows time formats were same.
How to get a unified time format as the API result ?
Notification Bridge
in Windows Client API
Posted · Edited by JpBIT
My windows monitoring service written in C# was sending alerts properly until this morning where two sites had the same error.
I tried sending a test command using command line and it is working. The time in below log is NZST.
Was it due to an outage?
03/04/2024 03:09:57 ERROR: Pulseway notification failed. Response: This request operation sent to net.pipe://localhost/NotificationBridge did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
03/04/2024 03:17:01 ERROR: Pulseway notification failed. Response: This request operation sent to net.pipe://localhost/NotificationBridge did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.