You can check identity server deployment guide.
You probably forgot to add index testapi-log-2022.01. ElasticSearch, Prometheus and such are 3rd party applications and as much as we try to help configuring, their configuration is unrelated to abp. Hence, it is better to search for google or ask in stackoverflow about specific 3rd party questions which can return results faster.
Yes, it may be related with template generation. If you think there is a problem with template generation, please provide what you have entered in suit and what is generated wrong in which files.
Thank you.
In your TestSample.ManagedEntityService.Blazor project;
Check ManagedEntityServiceMenuContributor
, you are passing /ManagedEntities as url for your Menus.ManagedEntityServiceMenus.ManagedEntities but your ManagedEntities.Razor
has @page "/managed-entities"
Either change /ManagedEntities in your menu contributor to /managed-entities or vice versa.
I will check it, please don't share your commercial applications with public link.
Thank you.
Can you give more details about your problem?
Do you develop ui inside of your microservice (like product service)? Does your Web application has reference of your new microservice .Web
layer and DependsOn configuration?
You need to divide base MigrationEventHandler
and MigrationsChecker
. You can check eShopOnAbp sample to see how.
These kind of errors are logged because of security reasons. Furthermore, you need to set Microsoft.IdentityModel.Logging.IdentityModelEventSource.ShowPII=true
even to see some of the details in logs. These are done for security reasons.
If you want to ignore it and share the error details, probably you need to override some identityserver core functionality. Since we are using that library, it is better to ask in identityserver 4 github issues if it is possible and what to override.
Hi @Toby,
Our recommended way would be the pragmatic way which suits your development team the best. Your sample makes sense.