Is your database connector keeping up?

Once your database connector is running, this is where you check that it is keeping up. It's on plans that include the connector, and only your account admins see it. The figures cover the period at the top right. Here, the last 24 hours. Start with the save rate: of the rows Routy handed to your database, the share it accepted. A row count alone can look fine either way. The rate is what tells you whether rows are going missing. This rate is a little under 100%, and most of the gap is duplicates. Routy delivers every row at least once, so sometimes a row arrives that your database already has. It is skipped, and nothing is lost. Duplicates are highest right after a catch-up, when a window of data is sent again. Dropped is different. These are rows Routy could not write at all. Above zero means data is missing from your database, and the gap won't close on its own.

The first chart shows what was saved each hour, with the save rate as the dashed line. Hover an hour to see what was attempted, saved, skipped and dropped in it.

The second chart separates the bad news. Dropped rows in red, failed operations in amber, and how long writes took. Here the writes got slow first, and an hour later rows were dropped. A climbing duration is often the first sign your database is under load.

When rows are dropped, note the hours, and check them against your own database logs. Test Connection checks that Routy can still reach your database. If rows are still missing, contact support with those hours. Every figure on this screen is explained in the help panel, one click away.