Matomo configured with wrong site id

[rosiel]

On TAG=1.0.10, ENVIRONMENT=starter_dev, Matomo is getting configured with site id = 2, but Drupal thinks site id = 1.

When I load Matomo's UI, it displays a "no data has been recorded yet, set up below" page. It specifies that the site ID expected is 2. However Drupal's Matomo configuration has it at 1.

I'm currently spinning up make local to see if this happens there too.

[jefferya]

I can reproduce on non isle-dc site using isle-buildkit TAG 1.0.7.

Is the proper value 2 or 1? I suspect the 2 in Matomo is from isle-buildkit during the matomo database creation, more specifically,

https://github.com/Islandora-Devops/isle-buildkit/blob/main/matomo/rootfs/etc/matomo/create-matomo-database.sql#L878

) ENGINE=InnoDB AUTO_INCREMENT=2 DEFAULT CHARSET=utf8;

I've not found the time to dig deeper and test but the reasoning behind AUTO_INCREMENT=2 instead of 1 is not clear to me.

[rosiel]

Confirmed, it's happening on ISLE-DC with the local configuration as well.

[noahwsmith]

@nigelgbanks do you recall if that AUTO_INCREMENT=2 was intentional? Seems maybe like a bug/typo to me...

[nigelgbanks]

I can't remember, looks like @dannylamb added it here: Islandora-Devops/isle-buildkit@544b045#r93147610. Do you recall @dannylamb?

[dannylamb]

For the life of me I can't remember why it was bumped from 1 to 2. I think it was just not working and for whatever reason, bumping it to two made it work. But now the shoe appears to be on the foot so I dunno 😅

[rosiel]

OK, so. In the Tech call today Seth also mentioned doing something about this - like needing to set autoincrement=2. We'll broaden this issue out to:

Install Profile: Use site_id = 2 in configs.
Starter Site: same.
Playbook: Get Matomo set up with autoincrement 2.

[nigelgbanks]

I should mention in upgrading Matomo for the 2.z release I've changed the way it installs such that we no longer need to create tables in this way, so hopefully the issue will not be present in the 2.X release.