[BUG] Importing a large amount of monitoring config occur poor experience and may trigger a long database transaction

[MasamiYui]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

I imported 500 monitoring configuration files, it took 8 minutes.

Expected Behavior

During this time, I didn’t see any data increase on the monitoring center list page, which made me suspect if the process was stuck.

Steps To Reproduce

1.Enter 'monitors' from left menu
2.Select 'Import Monitor'
3.Import a large monitor config file
4.Waiting long time,no data increase

Environment

HertzBeat version(s):1.6.1

Debug logs

No response

Anything else?

I found that MonitorServiceImpl.java used @transactional at the class level,
@Transactional(rollbackFor = Exception.class) public class MonitorServiceImpl implements MonitorService

This occur a poor experience and was unnecessary.

If each configuration import was treated as a separate transaction, I would have seen the data being imported continuously, making me feel that the process was working.

The same issue might also at AlertDefineServiceImpl.java.

[yunfan24]

Hello, I have a question. If each configuration is imported as a separate transaction, how can we ensure the integrity of the imported data? In other words, if one configuration import fails, how should it be handled?

[MasamiYui]

Hello, I have a question. If each configuration is imported as a separate transaction, how can we ensure the integrity of the imported data? In other words, if one configuration import fails, how should it be handled?

I think failure can be ignored may be more reasonable ;or adding a progress bar or a place to check the progress will be much better for batch import.