Error In Logs: Unable to record samples: sql_stats.ee4c8acddba503005666f1431d9619e4

[mcthornton5]

Hi All,

After we updated to Jakarta, I started seeing this error message occur every minute in the System Logs:

Unable to record samples: sql_stats.ee4c8acddba503005666f1431d9619e4: org.jrobin.core.RrdException: Bad sample timestamp 1506760766. Last update time was 1506760766, at least one second step is required: org.jrobin.core.RrdDb.store(RrdDb.java:704)

org.jrobin.core.Sample.update(Sample.java:221)

com.glide.velocious.jrobin.backend.JRobinDB.recordSamples(JRobinDB.java:60)

com.glide.velocious.jrobin.da.JRobinWriter.recordSamples(JRobinWriter.java:56)

com.glide.monitor.db.MysqlStatsMonitor.flush(MysqlStatsMonitor.java:115)

com.glide.ui.monitor.InternalMonitor.flushSingletons(InternalMonitor.java:225)

com.glide.ui.monitor.InternalMonitor.run(InternalMonitor.java:195)

Does anyone know what this means? I'm not too sure what sql_stats is, but what follows appears to be a sys_id, and it's the same one every time. Is there anywhere else I can investigate to see what the issue seems to be?

My biggest concern is that it is marked as an error and is logged every minute, and that it appears to be a repeat sys_id.

Thanks so much!

[Deepak Kumar5]

Might be something related to sql performance graph/stats.

sergiu.panaite can help you on this in better way.

[sergiu_panaite]

Hi Michael,

The ServiceNow Performance dashboard stores the data into a table called jrobin_database. That table contains data for different definitions (we can think about categories), in our case for SQL, see below screenshot from my own instance:

If your instance is hosted on our cloud, I would suggest you open an incident with ServiceNow support, as we will need to look further into this.

If your instance is on premise, let me know and I will think what kind of information I would need further to debug this.

[mcthornton5]

Thanks so much for the detailed response. I've got a ticket opened with support, and I've asked them if we can take a detailed look into the issue. Initially I was told that this the error could be ignored, but it just doesn't seem right that we get these errors every minute or so.

Again, I really appreciate the help.

[sergiu_panaite]

You get them every minute because of their collection time, see below screen shot of the SQL Stats definition: