For have (hostname/host/ip) an useful data addition when visiting the /admin/reports/dblog page
Is there a way I can add this field without hacking the core dblog.module?

Comments

winguru’s picture

winguru CreditAttribution: winguru commented

I have exactly the same question and I came across this issue while searching for ways to extend Drupal. Unfortunately, I don't have much direction or experience extending core module functionality.

I intend to do some research and hopefully come up with a solution, but here are some of the reasons I am working on this issue:

  1. I like to see ip/reverse-dns information when looking at Drupal messages in a table form since "Anonymous" doesn't single out different users.
  2. I'm using Varnish as a front end for Drupal, so all of the log messages (in the details page) all show the address of the Varnish server and not the client.
  3. I'm using GeoIP and some custom hacks for including visitor information in the Apache environment variables I would like to log as part of the core hook_watchdog function (if possible)

I'll try to update my comments as I find more info on the "Drupal way" of doing this ;-)

--Geoff Thornton

Wolfflow’s picture

Wolfflow CreditAttribution: Wolfflow as a volunteer commented
Issue summary: View changes

Hi, fostering my issue I found this and even is a long time ago I want to thank winguru for his comment which resume some of the motivations of why this request could help Drupal Site Admins to easy their job especially Drupal Newbie Dev to enhance security task and further deeper programming of lists of ip that obviously treat a website in general.

Maybe that this issue was one of many that did not get lucky to be discovered sooner or maybe many developers have good reason to ignore, would be nice if some of the great Drupal Core developers could give us a short opinion, advice or hint, advising us where there may be "against of" or "in favor" of this special request, explanations.

Thanks

Status: Active » Closed (outdated)

Automatically closed because Drupal 6 is no longer supported. If the issue verifiably applies to later versions, please reopen with details and update the version.