I have a MP A which contains 7 CIs, I want to copy this MP to create MP B. For MP B I only want to use 6 out of the 7 CIs as the last CI is unnecessary. I use the import configuration (great qol btw) and for the 7th CI I use same CI.
After the import configuration has been completed I delete the 7th CI from the MP. Inside the Report tab I still see that same CI appear which is not ideal. You'd think clicking the three dots besides it lets me Delete it from the page, but to my surprise that option is greyed out. How do I get rid of this CI from the Report page?
Best answer by ivan.kozlov
Hi JTH,
Could you please clarify which version of the product is this? There are quite a few improvements available in 15.2 in comparison with what is available in v14 which allows much more granular control over things you’re trying to import.
I think I've encountered the same issue as the one you’ve reported with “ghost CI’s appearing under the report tab. The solution was do delete those items manually using GraphQL queries.
First you need to run a query to identify the id of problematic CI aggregation and next query should delete it. Please test these queries on some development system before running anything in production!
Could you please clarify which version of the product is this? There are quite a few improvements available in 15.2 in comparison with what is available in v14 which allows much more granular control over things you’re trying to import.
I think I've encountered the same issue as the one you’ve reported with “ghost CI’s appearing under the report tab. The solution was do delete those items manually using GraphQL queries.
First you need to run a query to identify the id of problematic CI aggregation and next query should delete it. Please test these queries on some development system before running anything in production!
Hi @JTH please don’t hesitate to let us know if there is anything we can help you with further. I’m closing this thread for now, if you have any other questions please feel free to share them in the comments or create a new post 🙋♀️
@Marcel-Jan sorry, for such a lot time with reply. Just recently had to deal with cleanup of those Source aggregations for one of our customers and managed to find the right queries for that:
You can use this query to identify those blank source aggregations:
query q3a { monitoringProjects(filter:"configuration.aggregation.aggregations.any(aggregations.count() = 0)",versionSelector:{draftVersion:true}){ totalCount edges { node { gid draftVersion { name configuration {storedVersion { aggregation { type storedVersion { name aggregations(filter:"aggregations.count() = 0") {edges { node { type gid storedVersion { name dataSource { storedVersion { name }} }}}} }}}} }}} } }
And this mutation to remove them (gid in this case is the gid of the aggregation you can get from the previous query):
The delete mutation will put the project into draft state so you can review the change before publishing it.
Hi,
ONE Web > Monitoring Project
I have a MP A which contains 7 CIs, I want to copy this MP to create MP B. For MP B I only want to use 6 out of the 7 CIs as the last CI is unnecessary. I use the import configuration (great qol btw) and for the 7th CI I use same CI.
After the import configuration has been completed I delete the 7th CI from the MP. Inside the Report tab I still see that same CI appear which is not ideal. You'd think clicking the three dots besides it lets me Delete it from the page, but to my surprise that option is greyed out. How do I get rid of this CI from the Report page?
Page 1 / 1
Hi JTH,
Could you please clarify which version of the product is this? There are quite a few improvements available in 15.2 in comparison with what is available in v14 which allows much more granular control over things you’re trying to import.
I think I've encountered the same issue as the one you’ve reported with “ghost CI’s appearing under the report tab. The solution was do delete those items manually using GraphQL queries.
First you need to run a query to identify the id of problematic CI aggregation and next query should delete it. Please test these queries on some development system before running anything in production!
Currently on 13.9.4 and also I don't have access to the first link, however I'll look into this with the team 🙂 thank you for the respone
Hi @JTH please don’t hesitate to let us know if there is anything we can help you with further. I’m closing this thread for now, if you have any other questions please feel free to share them in the comments or create a new post 🙋♀️
I have tried this and it worked. The dataset is gone. The only weird thing is that the thing under which it was grouped (ISHS Sybase) remains.
The monitoring project ran successfully and did not profile the removed dataset though. So that's good.
Thanks for the feedback @Marcel-Jan, I’ve shared the issue with the team 🙌
@Marcel-Jan sorry, for such a lot time with reply. Just recently had to deal with cleanup of those Source aggregations for one of our customers and managed to find the right queries for that:
You can use this query to identify those blank source aggregations:
query q3a { monitoringProjects(filter:"configuration.aggregation.aggregations.any(aggregations.count() = 0)",versionSelector:{draftVersion:true}){ totalCount edges { node { gid draftVersion { name configuration {storedVersion { aggregation { type storedVersion { name aggregations(filter:"aggregations.count() = 0") {edges { node { type gid storedVersion { name dataSource { storedVersion { name }} }}}} }}}} }}} } }
And this mutation to remove them (gid in this case is the gid of the aggregation you can get from the previous query):
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.