[The Anomaly Sub Download
Jamar Lizarraga
Server Event time Event Occurrence Anomaly type
CSNAME
2022-11-13 00:56:27 Backup job [1346233] completed. Client [CLIENT], Agent Type [SQL Server], Subclient [default], Backup Level [Transaction Log], Objects [1], Failed [0], Duration [00:01:14], Total Size [9.38 MB], Media or Mount Path Used [[MA001] /ds3/CVLT03, [MA001] /ds1/CVLT01]. 93 Occurrence
CSNAME
2022-11-12 23:59:56 Backup job [1345979] completed. Client [CLIENT2], Agent Type [Virtual Server], Subclient [default], Backup Level [Incremental], Objects [3801], Failed [0], Duration [00:59:48], Total Size [3.69 GB], Media or Mount Path Used [[MA001] /ds2/CVLT02, [MA001] /ds1/CVLT01]. 177 Occurrence
Anomaly in DDB Pruning: The number of deduplication database prunable blocks or CommServe job records that should be deleted does not drop for a considerable period of time, which indicates an unusual performance drop in for the deduplication database that reported the issue. The email alert sent for this anomaly contains a link to the DDB Pruning Performance Anomaly Report.
Anomaly in events: The frequency or occurrence of the events does not match the system threshold. The software verifies anomaly in events on an hourly basis, and sends an email alert for any anomaly. The email alert sent for this anomaly contains a link to the Anomaly Dashboard Report.
Anomaly in number of failed jobs: The number of failed jobs is more than the system threshold. The email alert sent for this anomaly contains a link to the Unusual Number of Failed Jobs Report.
Anomaly in number of pending jobs: The number of pending and waiting jobs is more than the system threshold. The email alert sent for this anomaly contains a link to the Unusual Number of Pending Jobs Report.
Anomaly in number of succeeded jobs: The number of succeeded jobs is less than the system threshold. The email alert sent for this anomaly contains a link to the Unusual Number of Succeeded Jobs Report.
Job activity anomaly: The number of created, deleted, or modified files in a backup job changes abruptly from the normal behavior or the total backed up root size increases or decreases short. The email alert sent for this anomaly contains a link to the Unusual Backup Job Activity Report.
Note: A backup job runs for longer duration a few times for various reasons such as the backup of the deduplication database associated with the storage policy happens simultaneously, a user suspends a job for a duration, the operation window interrupts a job, or the subclient content that is being backed up increased unusually.
When you associate a client computer in the alert configuration, the alert notifies any anomalous backup jobs for the client computer. When you associate a storage policy in the alert configuration, the alert notifies any anomalous auxiliary copy jobs for the storage policy.
Notify when the anomalous job count is more than: This option is applicable only when you select Repeat notification every criteria. Specify the anomalous job count exceeding which the alert can be sent. This condition is applicable both for the first and the repeat notifications.
2022-11-11 00:59:43 Backup job [1341137] completed. Client [CLIENT], Agent Type [Virtual Server], Subclient [default], Backup Level [Incremental], Objects [613], Failed [0], Duration [01:59:31], Total Size [589.97 MB], Media or Mount Path Used [[MA] /ds2/CVLT02, [MA] /ds1/CVLT01]. 126 Occurrence
2022-11-10 00:54:33 Backup job [1338682] completed. Client [CLIENT], Agent Type [SQL Server], Subclient [default], Backup Level [Transaction Log], Objects [3], Failed [0], Duration [00:02:01], Total Size [42.96 GB], Media or Mount Path Used [[MA] /ds1/CVLT01]. 121 Occurrence
2022-11-09 04:59:46 Backup job [1336175] completed. Client [CLIENT], Agent Type [Virtual Server], Subclient [default], Backup Level [Incremental], Objects [4428], Failed [0], Duration [05:59:39], Total Size [4.30 GB], Media or Mount Path Used [[MA] /ds3/CVLT03, [MA1] /ds2/CVLT02]. 109 Occurrence
2022-11-09 02:56:37 Backup job [1336524] completed. Client [CLIENT], Agent Type [SQL Server], Subclient [default], Backup Level [Transaction Log], Objects [3], Failed [0], Duration [00:00:56], Total Size [13.06 MB], Media or Mount Path Used [[MA] /ds2/CVLT02, [MA] /ds3/CVLT03]. 136 Occurrence
2022-11-08 00:59:56 Backup job [1334105] completed. Client [CLIENT], Agent Type [Virtual Server], Subclient [default], Backup Level [Incremental], Objects [9934], Failed [0], Duration [01:59:49], Total Size [9.68 GB], Media or Mount Path Used [[MA] /ds2/CVLT02, [MA] /ds3/CVLT03]. 183 Occurrence
Server Event time Event Occurrence Anomaly type
CS001
2022-12-06 00:59:09 Backup job [1398329] completed. Client [CLIENT], Agent Type [Oracle RAC], Subclient [(command line)], Backup Level [Full], Objects [14], Failed [0], Duration [01:23:26], Total Size [39.47 GB], Media or Mount Path Used [[MA001] /ds2/CVLT02, [MA002] /ds3/CVLT03]. 156 Occurrence
Please click here for more details.
Server Event time Event Occurrence Anomaly type
ens21cvc001
2022-12-05 00:59:39 Backup job [1394241] completed. Client [CLIENT2], Agent Type [MySQL], Subclient [default], Backup Level [Full], Objects [374], Failed [0], Duration [12:59:28], Total Size [9.86 TB], Media or Mount Path Used [[MA003] /ds2/CVLT02]. 149 Occurrence
Hi Robert,
Which FR you are using. Are you also getting more event-based anomalies than desired? We are working on reducing the noise and will port it to your FR. Above, setting is for long running job and is hidden. We are unhiding it and adding some settings. Will add a doc link here once update is out.
I continue to get these Aux Copy anomaly alerts, in addition to the original ones that I had mentioned where it says that X jobs completed and comes from Event anomaly. Even after setting anomaly sensitivity to low, this is continuing to happen.
Hey Mizső,
What the blog post details is how Dynatrace now considers Kubernetes metrics and events in root cause analysis. Towards the bottom it has a "What's next" which talks about Kubernetes anomaly detection. This also shows a screenshot of some problems which it would be able to pick up. I would say it's likely that once Kubernetes anomaly detection rolls around there will be UI pages similar to the AWS one, its just not here yet so we don't know what it looks like.
New Kubernetes observability features is coming soon in Dynatrace. I am so exited, I can't wait for them :-). You can watch demos about them with Henik and Andy. These new features will be really cool and amazing.
I just wanted to inform you that the App Anomaly Detection feature in the BD Mobile Security App was found disabled on not just my phone but also my mother's for no reason after the latest update (roughly within the last one or two days).
This was perceived as a rather unpleasant surprise by the both of us since we do heavily rely on our Apps to work as intended without any additional effort. I would be very grateful if such worrying behaviour could be mitigated to some extent in the future.
Quick update on the situation: the developers could reproduce the behavior during testing and they are now investigating in depth. It's not clear at this stage what is the reason behind the function's random deactivation, but they will soon find out and come up with a fix via an automated update.
I just wanted to note that I experience the same behaviour as @Gjoksi on my side after a phone restart/reboot; the App Anomaly Detection is then switched off again. The same goes for my mother's device, too.
I've uninstalled and reinstalled the bitdefender mobile app on my device from the google play store and now I have an older version running on it: version 3.3.224.2368. This version doesn't have the app anomaly detection issue.
The app version was probably rolled back on play store until the issue is resolved. In order to update an app, the version code of the update must be higher than the current one, that's why only after uninstalling did the old version appear.
I, too, finally received the latest version of BD Mobile Security (3.3.227.2376). It fixed App Anomaly Detection so it does not turn itself off anymore after each and every individual phone restart/reboot.
Launching the BD Mobile Security App then though, the "Autopilot Recommendations" feature on the Dashboard still suggests to turn on App Anomaly Detection. When navigating to the Malware Scanner tab to verify whether the aforementioned feature is working correctly, then switching back to the Dashboard, the notice on the Dashboard curiously disappears (and does not return). I managed to replicate that erroneous behaviour on two different phones.
Thanks for sharing your feedback. May I kindly ask you to inform the Support teams about this? There could be a workaround I'm unaware of, or maybe they should look deeper into this, and check if the issue resurfaced. Based on my findings, it should work fine now.
I am pretty sure many/the majority of BD Mobile Security App users are currently affected by what I described in my comment (January 30). It is not a serious problem in my opinion since App Anomaly Detection seemingly works and remains in its enabled state even after a phone restart/reboot. It could potentially be perceived as a little bit distracting for the average user though when they are presented with said notice on their Dashboard indicating a malfunction so it should be addressed rather sooner than later I suppose :)
It only does the above when switching to the Malware Scanner tab (step 2). When I instead (after step 1) go to any of the other tabs (Web Protection, Scam Alert, More) and return to the Dashboard, the notice is still there! It really only disappears forever once I visited the Malware Scanner tab.
I have forwarded your feedback to the Mobile Security teams and they are looking into it. The patch addressed the initial problem and I think this is a rather isolated behavior unrelated to the previous one, that will be fixed soon as well. I'm saying this because according to the engineers, we did find another occurence, so it's something the developers have their eyes on right now.
795a8134c1