feat:func to return Count of entities in registry table w/signoff

[Jougan-0]

Description

This PR fixes #

Notes for Reviewers
This function returns the total count of entities in the registries table

Signed commits

• Yes, I signed my commits.

[leecalcote]

@VihasMakwana would you like to offer review on this PR? That would be helpful.

[VihasMakwana]

Apart from changes, LGTM.

[leecalcote]

One of the more important use cases to facilitate with these logs is that of when a model or any of its entities is not successful in registering. It's important to be able to give contributors and Meshery administrators as much information as possible about what model and what entity failed to import and why.

Please provide examples of how these logs facilitate the administrator's resolution in the face of these import failures.

Include a link to troubleshooting Docs?

[leecalcote]

One of the more important use cases to facilitate with these logs is that of when a model or any of its entities is not successful in registering. It's important to be able to give contributors and Meshery administrators as much information as possible about what model and what entity failed to import and why.

Please provide examples of how these logs facilitate the administrator's resolution in the face of these import failures.

Include a link to troubleshooting Docs?

Be aware that both Meshery Server and its clients (Meshery UI and mesheryctl) stand to benefit from this logged information. When a user imports a model using either of these two clients, the clients should return similar information.

[Jougan-0]

meshery/meshery#9564

[leecalcote]

I looked again:

meshery git:(regLog) make server
cd server; cd cmd; go mod tidy; \
	BUILD="v0.7.2-rc-1" \
	PROVIDER_BASE_URLS="https://meshery.layer5.io" \
	PORT=9081 \
	DEBUG=true \
	ADAPTER_URLS="localhost:10000 localhost:10001 localhost:10012" \
	APP_PATH="./apps.json" \
	go run main.go error.go;
# command-line-arguments
./main.go:286:7: log.Infof undefined (type "github.com/layer5io/meshkit/logger".Handler has no field or method Infof)
./main.go:287:41: undefined: meshmodel.NonImportModel
./main.go:289:8: log.Errorf undefined (type "github.com/layer5io/meshkit/logger".Handler has no field or method Errorf)
./main.go:294:48: undefined: meshmodel.RegisterAttempts
make: *** [server] Error 1

Be sure that the PR is building before requesting your next review.

[Jougan-0]

One of the more important use cases to facilitate with these logs is that of when a model or any of its entities is not successful in registering. It's important to be able to give contributors and Meshery administrators as much information as possible about what model and what entity failed to import and why.

Please provide examples of how these logs facilitate the administrator's resolution in the face of these import failures.

Include a link to troubleshooting Docs?

We are using a logic of creating a file of registery_attempts.json that stores every entity that failed
file is present at
meshery/server/cmd/registery_attempts.json

[Jougan-0]

One of the more important use cases to facilitate with these logs is that of when a model or any of its entities is not successful in registering. It's important to be able to give contributors and Meshery administrators as much information as possible about what model and what entity failed to import and why.
Please provide examples of how these logs facilitate the administrator's resolution in the face of these import failures.
Include a link to troubleshooting Docs?

We are using a logic of creating a file of registery_attempts.json that stores every entity that failed file is present at meshery/server/cmd/registery_attempts.json

This could be used by the contributors and administrators to resolve the issue related to that entity

[leecalcote]

Ready for final review, @Jougan-0?

[Jougan-0]

@leecalcote final changes suggested by uzair are left will finish it today

[VihasMakwana]

@leecalcote PR looks good, can you take a final look?

[MUzairS15]

Can't we maintain the error and attempt count in the registration funcs itself?

[Jougan-0]

The registration is done as follows in the
https://github.com/meshery/meshery/blob/cfd822700dc4dcb7b4cafa9d3af593fee017cf31/server/meshmodel/helper.go#L163
so while it is being is registered if we have an error we pass the to the new function I created
I used this logic as the in components if the schema is empty it returned nil rather than error and for each component and relationship we register it's model so every time we register them if we found an error then we count with the error .
Hope this makes sense @MUzairS15

[Jougan-0]

meshery/meshery#9829

[leecalcote]

@Jougan-0 @MUzairS15 this directory will not be present in Meshery deployments. This log file needs to be stored under ~/.meshery/server/registry.log

[leecalcote]

The log file location needs to be available in Meshery deployments, not only in local builds. Our standard location for such files is ~/.meshery

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue is being automatically closed due to inactivity. However, you may choose to reopen this issue.