You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm using a plugin, and while there are no issues with the metrics collected through it,
I've noticed that issue with measurements over time. Normally, only "job" and "stage" should be present.
But Problem is that : It seems that the plugin is continuously sending Jenkins logs to the database as measurements.
This issue is occurring both in Docker and Kubernetes environments.
This bug seems quite serious indeed. Since it's affecting data backup and restoration processes, it could potentially lead to data integrity issues. It's crucial to address this bug promptly to ensure the stability and reliability of the system.
If you have any additional details or insights that could help in resolving this issue, please feel free to share them.
The text was updated successfully, but these errors were encountered:
I’m not sure of the current development status of the plugin but looking at master branch it doesn’t appear to have been released in three years as of this writing.
It doesn’t appear to be up for adoption. It might make sense to adopt it if the current owner is okay with that or co-own it.
Hello,
I'm using a plugin, and while there are no issues with the metrics collected through it,
I've noticed that issue with measurements over time. Normally, only "job" and "stage" should be present.
But Problem is that :
It seems that the plugin is continuously sending Jenkins logs to the database as measurements.
This issue is occurring both in Docker and Kubernetes environments.
This bug seems quite serious indeed. Since it's affecting data backup and restoration processes, it could potentially lead to data integrity issues. It's crucial to address this bug promptly to ensure the stability and reliability of the system.
If you have any additional details or insights that could help in resolving this issue, please feel free to share them.
The text was updated successfully, but these errors were encountered: