Report Builder: very old metric can’t be found

However, no matter where we look, we cannot find this metric - it's not in metrics manager, it's not on his or anyone else's accounts.

And now, when I try and edit the report builder, it removes the metric, so I cannot make any edits without breaking the file!

Under All Admin > Logs, there is a tab for “Usage & Access Logs”

You can check in here for changes made to Calculated Metrics, you can even further reduce this list by adding the name, or even a partial name of the metric that is missing.

Once you find it, you can grab the ID of the metric. Now, open ANY calculated metric in your inventory, and replace the ID in the URL..

Deletions are really "soft" deletions... basically the item is removed from the components list, but it should still exist..

Looking at our logs, it seems they don't go back far enough (we have "only" 3 years of logs by the look of it), and I estimate this was set up / potentially deleted more like 4-5 years ago (but somehow report builder can still use the metric)

once we have the search terms, I need to know whether it is typed or pased in the search field. How can we achieve this?

If you use the last interaction, that's easier... but may not provide the detail you need... but if you try to track a combined usage you can see how complex this might get...

All of this would require custom JS to detect Key Presses (which wouldn't work for assistive technologies, and storing / updating at each use, to then read/pull when the search is submitted....

While I am not going to presume to know why this is important to you / your business... it might be worth having a discussion about whether this particular use case is worth the complexities (which still may not be able to capture all scenarios with 100% accuracy any way)

That one is tricky... what if they paste AND type? I assume you don't want to inflate your server calls by sending tracking on each keystroke or paste action (which may not even result in an actual search).

If you use the last interaction, that's easier... but may not provide the detail you need...  but if you try to track a combined usage you can see how complex this might get...

Personally I don't use the flow diagrams much... While I appreciate the ability to see the pathing through multiple channels like you are trying to do... Since the numbers don't align it causes confusion...

I almost suspect there is an issue with these diagrams (but it's hard to prove).. but in my case, our "orders" are subscriptions... users can only purchase a single subscription at a time... so there should be no way to have multiple orders in a visit that could cause calculation issues with a flow diagram, and yet, the orders are way off for us... leaving me even more convinced there's a bug in that visualization.....

If extensions are blocking then please try to open the page in another browser (Mozilla, Safari) or you can also check in incognito mode.

Yes it is OOTB dependencies depends on the version of cloud ,If cloud server uses the old version then map the same old version to your main pom and also try to change the analyser version 1.1.2

If you anyway need custom code to capture this new category, maybe a line of code would solve the issue rather than introducing a whole new extension?

Yes, it is possible to set traffic filter rules, including rate limits, in AEM as a Cloud OOTB Fastly CDN. Some of the advanced WAF-based rules require an additional WAF or advanced security license, but the basic filter rules can be used OOTB.

Check the cards list initialization: In your CardDustReviews class, you have a @ChildResource annotation on the cards list. Make sure that the cards list is properly initialized and populated with data. You can try debugging the code to see if the cards list is empty or if there's an issue with the data retrieval.

1. Check the Exporter configuration: Ensure that the Exporter configuration is correct and that the CardDustReviews class is properly registered as an exporter. You can try checking the Sling logs to see if there are any errors or warnings related to the exporter configuration.

1. Verify the Angular mapping: Double-check that the Angular mapping is correct and that the CardDustReviews component is properly mapped to the JSON output. Make sure that the Angular code is correctly referencing the cards list and that there are no typos or incorrect property names.

1. Check the cards list initialization: In your CardDustReviews class, you have a @ChildResource annotation on the cards list. Make sure that the cards list is properly initialized and populated with data. You can try debugging the code to see if the cards list is empty or if there's an issue with the data retrieval.

Restarting AEM from the OSGi Console and from a remote server access SSH tool like Putty or Gitbash are two different approaches with distinct implications. Let's dive into the details:

When you restart AEM from the OSGi Console, you are essentially restarting the AEM instance itself. This restart is specific to the AEM application and only affects the AEM process.

When you restart AEM using a remote server access SSH tool like Putty or Gitbash, you are restarting the underlying HTTP server process (e.g., Apache HTTP Server) that hosts the AEM instance.