retrieving all rules inserted into drools session which are being printed in KieSession using drools query

I am having a number of rules which are inserted in the drools session and I've got them printed using event listener provided by KieSession. Here is the code:

  kSession.addEventListener(new RuleRuntimeEventListener() {
        @Override
        public void objectInserted(ObjectInsertedEvent event) {
            System.out.println("==> " + event.getObject() + " inserted");
        }

        @Override
        public void objectUpdated(ObjectUpdatedEvent event) {
            System.out.println("==> " + event.getObject() + " updated");

        }

        @Override
        public void objectDeleted(ObjectDeletedEvent event) {
            System.out.println("==> " + event.getOldObject() + " deleted");
        }
    });

I want to get all the rules printed in objectInserted and are not triggered by objectDeleted method using drools query. I am not finding a way to do that. I don't want to it using Java but Drools. I am new to drools and did not find much regarding this over the internet. Any help would be really appreciated. Thanks

What I am trying to do
I am trying to write a query that returns me all the values which are present in a drool session using drools query.
something like this:

query "Query all attack categories"
AttackCategory($category : value)
end

this is a query i am already using in my system. I want this query to be generified and fetch all the objects(of different classes ) with only a single query.

My KieBaseModel

     KieBaseModel kbaseModel = kmoduleModel
            .newKieBaseModel(DEFAULT_KIE_BASE_NAME)
            .setDefault(true)
            .setEqualsBehavior(EqualityBehaviorOption.EQUALITY)
            .setEventProcessingMode(EventProcessingOption.CLOUD);

Update to the requirements
I can get the Objects from the drolls but is there any way I can get a tree structure as defined in the image. I want to get a link between the questions as well. Like, if question 1 was answered, which question was asked after it, and if the level 1 q1 was asked, then which question was asked after that. Some of the questions will be deleted from the tree as well. I need the connected tree-like described in the image. Is there any way to get such a tree from drools? Thanks

In your DRL file(s) you have access to a variable called drools. This is an instance of the KnowledgeHelper class, which gives you access to a bunch of information about the rules, environment, working memory, etc. The link is to the source code for KnowledgeHelper, since the documentation only discusses the most commonly used methods (usually for getting stuff like the rule name.)

From the drools variable, you can access the WorkingMemory object (link to source), which gives you access to all the objects in working memory. You should be able to use iterateObjects or iterateFactHandles to walk the data in working memory as needed.

Obviously I'm not familiar with your specific use case, so you'll need to update any code to match your use case. But let's say I want to get all AttackCategory instances remaining in WorkingMemory, I might do something like this:

drools.getWorkingMemory()
      .iterateObjects(new ObjectFilter() {
          @Override
          public boolean accept(Object object) {
            return object instanceOf AttackCategory;
          }
       ) // now you have an instance of Iterator<? extends AttackCategory>

You could also substitute iterateFactHandles for iterateObjects if you wish to iterate over the fact handles instead.

Note that these iterators are not threadsafe.

You could alternatively do this in Java and call such a utility method from the DRL, but you indicated you'd prefer to do this in Drools itself. Unfortunately while drools does give you access to working memory and the general environment, the listeners are outside of this. Drools is only aware of facts in its working memory, but not how they got there. The way listeners work is that they hook into the insert and delete handlers themselves and trigger when those methods do; the objects, once inserted, are just like any other object in working memory (which is to say, you can't differentiate between how they got there.)