Skip to main content
Solved

Delete dataset from report (Monitoring Project)


JTH
Data Pioneer
Forum|alt.badge.img+2
  • Data Pioneer
  • 16 replies

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?

​​​

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!

You can access GraphQL API here https://customer.envrionment.ataccama.online/playground/
https://docs.ataccama.com/one/latest/one-apis/one-api.html#work-with-graphql

query {
  monitoringProject(gid: "PUT_PROJECT_ID_HERE") {
    draftVersion {
      configuration {
        storedVersion {
          aggregation {
            storedVersion {
              aggregations {
                edges {
                  node {
                    storedVersion {
                      aggregations {
                        edges {
                          node {
                            gid
                            type
                            storedVersion {
                              catalogItem {
                                storedVersion {
                                  _displayName
                                }
                              }
                            }
                          }
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

You’ll need to use ID’s from the output of the first query in the 2nd one:

mutation { 
  catalogItemAggregationDelete(gid: "PUT_CI_AGGREGATION_ID_HERE") { 
    success 
  } 

  # catalogItemAggregationPublish(gid: "PUT_CI_AGGREGATION_ID_HERE") { 
  # success 
  # } 
}

I hope this helps.

Ivan

View original
Did this topic help you find an answer to your question?

5 replies

ivan.kozlov
Ataccamer
Forum|alt.badge.img+3
  • Ataccamer
  • 26 replies
  • Answer
  • July 25, 2024

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!

You can access GraphQL API here https://customer.envrionment.ataccama.online/playground/
https://docs.ataccama.com/one/latest/one-apis/one-api.html#work-with-graphql

query {
  monitoringProject(gid: "PUT_PROJECT_ID_HERE") {
    draftVersion {
      configuration {
        storedVersion {
          aggregation {
            storedVersion {
              aggregations {
                edges {
                  node {
                    storedVersion {
                      aggregations {
                        edges {
                          node {
                            gid
                            type
                            storedVersion {
                              catalogItem {
                                storedVersion {
                                  _displayName
                                }
                              }
                            }
                          }
                        }
                      }
                    }
                  }
                }
              }
            }
          }
        }
      }
    }
  }
}

You’ll need to use ID’s from the output of the first query in the 2nd one:

mutation { 
  catalogItemAggregationDelete(gid: "PUT_CI_AGGREGATION_ID_HERE") { 
    success 
  } 

  # catalogItemAggregationPublish(gid: "PUT_CI_AGGREGATION_ID_HERE") { 
  # success 
  # } 
}

I hope this helps.

Ivan


JTH
Data Pioneer
Forum|alt.badge.img+2
  • Author
  • Data Pioneer
  • 16 replies
  • July 25, 2024

Hi @ivan.kozlov,

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


Cansu
Community Manager
Forum|alt.badge.img+3
  • Community Manager
  • 625 replies
  • July 30, 2024

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
Star Blazer L2
Forum|alt.badge.img+1
  • Star Blazer L2
  • 21 replies
  • August 1, 2024

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.

 


Cansu
Community Manager
Forum|alt.badge.img+3
  • Community Manager
  • 625 replies
  • August 2, 2024

Thanks for the feedback @Marcel-Jan, I’ve shared the issue with the team 🙌


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings