LogicMonitor Datamart Data

General
,
1

I followed the guidance that was posted under this post and have everything mostly working.
Alerts, audit logs, devices, etc are all populated. The time series data for Ping tho is not. I went back and checked the config and set StartDateTimeUtc to “2024-10-28”. This didn’t seem to kick off a sync of data either. When I check the health endpoint versions and assemblies are healthy, but System Memory reports unhealthy.

    "System Memory": {
        "status": "Unhealthy",
        "durationMs": 1.7453,
        "description": "Index was outside the bounds of the array.",
        "data": {}
    },
2

After doing some more digging, the system memory issue shows this in the logs

2024-10-30 12:04:07.636 +00:00 [Information] Microsoft.AspNetCore.Routing.EndpointMiddleware Executing endpoint '"Health checks"'
/bin/bash: line 1: free: command not found
2024-10-30 12:04:07.644 +00:00 [Error] Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService Health check "System Memory" threw an unhandled exception after 3.5637ms
System.IndexOutOfRangeException: Index was outside the bounds of the array.
   at AspNetCore.HealthChecks.SystemMemory.SystemMemoryHealthCheck.CheckHealthAsync(HealthCheckContext context, CancellationToken cancellationToken)
   at Microsoft.Extensions.Diagnostics.HealthChecks.DefaultHealthCheckService.RunCheckAsync(HealthCheckRegistration registration, CancellationToken cancellationToken)

And the issue for the datamart appears to be

gicMonitor.Datamart.LoopInterval Skipped writing aggregations because the end date time + minutes offset (from configuration) was greater than UTC now. Start date UTC: 10/01/2024 00:00:00 +00:00. End date UTC: 11/01/2024 00:00:00 +00:00. Minutes Offset: 0. End date UTC with offset: 11/01/2024 00:00:00 +00:00.

The start date I set as a few days ago, I don’t set an enddate as that is not in the example doc, but it appears to go to the 1st at midnight so it errors out stating that is in the future?

3

Hey @Joe_Williams …

Amusingly, the System Memory one is Microsoft code, not ours :smiley: Also, this is not a particularly important HealthCheck - we only included it because it came out of the box with ASP.NET code in the AspNetCore.HealthChecks.SystemMemory namespace. You can safely ignore it. If it becomes a problem for monitoring, we will remove it from the HealthChecks.

For the Time Series data, because aggregations are currently monthly and we’re not yet at the end of October 2024, you have two choices:

  1. Set the Start Date to 2024-09-01: this will ensure that you grab the September Time Series Data.
  2. Leave the Start Date as 2024-10-01 and wait for 2 days: this will collect the October Time Series Data once October is over.

Any further problems, let me know!