I have a customer in Las Vegas who's interested in using dT to scrape all log messages, not just ones that exist within a purepath.
The obvious solution to this is to simply enable Start-PurePath on the logging sensor. However this is not possible out of the box, but easily do-able in DEBUG mode.
Does anyone see any issues with this approach?
Yes I'm sure several replys will point out the concerns related to having a non-standard configuration, and upgrades are problematic, however this has already been discussed with the customer.
Thanks for the thoughts.
Answer by Christian S. ·
hi Joe,
actually i'm wondering what you mean with 'easily do-able'?
i'm very sure that it's impossible to start a PurePath on sensor nodes like logging, exception or memory (single-event nodes) for these reasons:
so for these reasons it's simply not possible.
it would also not be a good idea in terms of the amount of PurePaths.
i'd say with dynatrace this usecase is not really managable right now.
best,
Christian
Answer by Rob V. ·
That sounded like fun so I had to try it, but easyTravel is pretty boring, logging-wise.
The only things I can think of include the potential explosion of data if you have a lot of non-PP logging going on, and the fact that it will impact your "Default" application (since these won't be web request-based PPs and will therefore land in Default).
Rob
One item I forgot to mention, is that they intend to setup filters on the logging sensor to pick up only important stuff. They liked the filtering capability and thought that was sufficient for their needs.
Hopefully this will keep the data explosion issue under control.
I wonder if they could use AOP to get this done (a) without having to hack our sensors, and (b) to add a little context info to the otherwise log-only PPs, to give some clue about where they're coming from. I guess if the messages are designed with discipline that could help manage it too.
DECEMBER 12, 10:00 AM GMT / 2:00 PM ET
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here
Learn how Dynatrace Real User Monitoring automatically detects errors that impact your end users caused by erroneous 3rd party or CDNs.
December 10, 4:00 pm CET / 10:00 am ET
Register here