- Mark as New
- Subscribe to RSS Feed
- Permalink
‎17 Feb 2022 03:00 PM
Hi All,
I'd like to know if there is a way to "un-monitor" specific services (e.g. "Welcome to Tomcat"); I can't find a way to remove them, and muting the requests leaves the service "alive".
Thanks,
Edoardo
Solved! Go to Solution.
- Labels:
-
oneagent
-
services classic
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎17 Feb 2022 08:21 PM - edited ‎17 Feb 2022 08:22 PM
Hello EdoardoB (great name),
You could use a custom process monitoring rule with "Do not monitor" to stop monitoring the processes creating the service. The issue will be making sure you can identify just that process.
Best,
Edward Buckler
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 07:37 AM
Hi Edward,
thank you for your suggestion; problem is that the process "hosting" this service is not "hosting" only useless services but also some useful ones, so I would loose those (I think).
Thanks,
Edoardo
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 08:36 AM
Only way to disable service data is (at this time) muting all of it's requests (there is a new "Muted requests" menu in since 1.234). Better way should be to disable such default services on host level. If there is no purpose to use them, why are they available to use ?
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 08:53 AM
Hi Ratislav,
you are obviously right, the sad part is that not always developers behave in the proper way ahaha; I tried muting the (only) request on a Welcome to Tomcat service but the service looks still active (even if it is showing no metrics in the service list view).
Thanks,
Edoardo
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 09:05 AM
Yes it'll be "active" but there will be no mess with your Dynatrace environment. We have several customers, where "Welcome to Tomcat" is used for various production requests .
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 03:17 PM
Hi Edoardo
You can exclude processes from beeing monitored and you also can exclude incoming web request urls. Maybe you can use 'excluding web request urls'? See Settings->Server-side service monitoring->Deep monitoring
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 05:05 PM
Hi Matthis,
the problem is that in this way I will remove every request with a specifica path, right? And in my case I can't confirm that all requests "/" are actually useless...
Thanks,
Edoardo
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎18 Feb 2022 05:16 PM
Yes, you can exclude requests to specific URLs. In my case e.g. we exclude on an apache webserver all requests that begin with '/server-status' as they come from our monitoring with icinga and are of no interest in Dynatrace now.
When you want to exclude only some requests but they all use the same URL, then you cann't use this configuration.
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎20 Feb 2022 10:11 PM
Hi Edoardo,
There is no proper way to accomplish what you want, this is something that could be done previously in AppMon. As work around, we merge those services into the primary monitored service, not pretty, but gets it off your screen, you will then have the web requests show up under the main service, which you can mute.
I've raised a product enhancement for this specific feature. If you add your support to it, it might get some more focus.
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎21 Feb 2022 08:00 AM
Thank you, voted!
Edoardo
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎21 Feb 2022 08:12 AM
Hi @EdoardoB ,
I'd recommend to do this:
- define proper request naming rules to group relevant from non-relevant requests. (e.g. you might have some periodic health checks on the Default service maybe that you want to keep, but not any other "accidental" requests)
- One you have proper groups of requests on that service, "mute" the ones that are not relevant for any error or anomaly detection
This might be a little effort but since we now have API access to define both key- and muted requests this can be done through the API for large scales.
E.g.: I'm excluding "irrelevant" /healtz check requests from all the microservice mesh health checks by muting them on every service.
- Mark as New
- Subscribe to RSS Feed
- Permalink
‎22 Feb 2022 08:41 AM
Thank you, that's what I did at the moment, since it's not possible to mute a service for now...
Edoardo
