u/Ok_Hunter6411

Hi everyone,

I’m learning ASP.NET MVC and I want to create a new practice project where I can experiment with DevExpress controls.

I already have an existing solution where I have created a Web API project. Now I’m thinking of adding a new ASP.NET MVC project with DevExpress in order to practice the UI part.

My question is:

Would it be better to add this new MVC + DevExpress project inside the same solution, or should I create a completely separate solution for it?

My concern is mainly about debugging and running multiple projects at the same time. For example, if both projects are in the same solution, can I run/debug them separately or together without issues, using different ports?

I’m still learning, so I’d like to hear what is considered good practice in real-world development.

Thanks in advance!.

Hi everyone,

I’m a junior .NET developer and I’m currently designing a small internal application called LogHub.

The goal of LogHub is to collect and monitor logs from different internal applications/services. For now, I’m starting with the database design and then I plan to build the application in Visual Studio using .NET Core. The first version may also use DevExpress, but later I might move it to a more minimal/simple UI.

So far, I have designed these main tables:

- Users

- Applications

- Logs

- Alerts

- AlertNotifications

- Aggregations

The basic idea is:

- Applications store the systems/services that send logs.

- Logs store the raw log entries.

- Alerts are created when a log or group of logs needs attention.

- Logs have an optional AlertId FK, so a log can be connected to an alert.

- AlertNotifications store where/how an alert was sent.

- Aggregations will store summary/statistics data for dashboard usage.

This is meant to be an internal monitoring/logging tool, not a public product.

My questions are:

1. Does this database design make sense for a first version?

2. Would you change anything in the table structure?

3. Is .NET Core a good choice for this type of internal tool?

4. Would you recommend starting with DevExpress UI, or keeping the first version minimal?

5. Any advice on how to structure the Visual Studio solution for this kind of project?

I’m mainly trying to learn good architecture and database design while building something useful.

Thanks in advance!

​

I'm trying to understand how software teams monitor applications in production and investigate issues when they occur.

In our case, notifications can be sent to Microsoft Teams, but I'm curious how other teams approach this problem as applications and log volume grow.

Where do your logs go?

How do you investigate errors reported by users?

How do you monitor application health?

How do you receive alerts?

Do you rely mainly on Teams/Slack notifications, or do you use something else as your primary solution?

At what point do chat-based notifications become difficult to manage?

If you moved away from Teams/Slack-centric monitoring, what did you replace it with and why?

I'd love to hear about real-world setups, lessons learned, and tools that have worked well in production environments.