Overview

Flowdock Log uses the Flowdock API module to place all of your Drupal log messages in a Flowdock Team Inbox. This is very useful to track production and non-production environments of your Drupal installations. Each Drupal multisite, environment, and installation can have its own Flow to keep logging logically separated. This can be advantageous to developers who are already using Flowdock to communicate or an enhancement to you current Drupal development team's information tracking.

Advantages

  • Get group notifications to developers all Drupal log messages including errors right where they are already communicating
  • Comment on messages or create message flows to help troubleshoot issues and fix them faster if there is a regression
  • Use tagging to filter messages by IP, module name, and severity

This module uses Drupal 7's core queue system to only send data to Flowdock in the background. Queues are run during cron execution so if you would like message sent more or less often to Flowdock you will need to adjust how often your cron jobs are run.

Flowdock Log is implemented using hook_watchdog and can be installed along side any other logging module.

Flowdock API

You will need to download the Flowdock API module to use this module.

Link To Projects

Git Flowdock Log

git clone --branch 7.x-1.x http://git.drupal.org/sandbox/1point21/2202669.git flowdock_log

Git Flowdock Api

git clone --branch 7.x-1.x http://git.drupal.org/sandbox/1point21/2202667.git flowdock_api

Parveview

http://pareview.sh/pareview/httpgitdrupalorgsandbox1point212202669git-7x-1x

Flowdock

Flowdock is a team collaboration app for desktop, mobile & web. Work on things that matter, be transparent and solve problems across tools, teams & time zones. Try it for free for 30 days or free for ever with up to 5 users.

http://www.flowdock.com

Reviews of other projects

  1. https://drupal.org/comment/8521289#comment-8521289

Comments

1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
PA robot’s picture

PA robot CreditAttribution: PA robot commented
Multiple Applications
It appears that there have been multiple project applications opened under your username:

Project 1: https://drupal.org/node/2203593

Project 2: https://drupal.org/node/2203589

As successful completion of the project application process results in the applicant being granted the 'Create Full Projects' permission, there is no need to take multiple applications through the process. Once the first application has been successfully approved, then the applicant can promote other projects without review. Because of this, posting multiple applications is not necessary, and results in additional workload for reviewers ... which in turn results in longer wait times for everyone in the queue. With this in mind, your secondary applications have been marked as 'closed(duplicate)', with only one application left open (chosen at random).

If you prefer that we proceed through this review process with a different application than the one which was left open, then feel free to close the 'open' application as a duplicate, and re-open one of the project applications which had been closed.

I'm a robot and this is an automated message from Project Applications Scraper.

PA robot’s picture

PA robot CreditAttribution: PA robot commented
Status: Needs review » Needs work

There are some errors reported by automated review tools, did you already check them? See http://pareview.sh/pareview/httpgitdrupalorgsandbox1point212202669git

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

Fernly’s picture

Fernly CreditAttribution: Fernly commented

Please add a git clone link. Thanks!

1point21’s picture

1point21 CreditAttribution: 1point21 commented

Here is the git clone link for the master branch from the project page.

git clone --branch master 1point21@git.drupal.org:sandbox/1point21/2202667.git flowdock_api
cd flowdock_api
1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
1point21’s picture

1point21 CreditAttribution: 1point21 commented

Based on the Drupal recommendations I have moved over to using a 7.x-1.x branch and deleted the master branch. Here is the new git clone.

git clone --branch 7.x-1.x 1point21@git.drupal.org:sandbox/1point21/2202669.git flowdock_log
cd flowdock_log

This code is tested working with the required Flowdock API module. All of the coding standard issues have been resolved according to pareview.

http://pareview.sh/pareview/httpgitdrupalorgsandbox1point212202669git-7x-1x

1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
1point21’s picture

1point21 CreditAttribution: 1point21 commented
Status: Needs work » Needs review
1point21’s picture

1point21 CreditAttribution: 1point21 commented
Issue summary: View changes
heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn commented
Issue summary: View changes
heddn’s picture

heddn
Primary language English
Location Nicaragua
CreditAttribution: heddn commented
Status: Needs review » Needs work

function flowdock_log_get_watchdog_map()
Why doesn't this wrap the values in t()?

variable_del('flowdock_log*');
This doesn't work. Either write a db_delete query or list each of the variables you want to delete.

1point21’s picture

1point21 CreditAttribution: 1point21 commented

The values in flowdock_log_get_watchdog_map() have been wrapped in the t(), I like the suggestion. The variable delete function has been updated to delete each variable individually.

1point21’s picture

1point21 CreditAttribution: 1point21 commented
Status: Needs work » Needs review
alvar0hurtad0’s picture

alvar0hurtad0
he/him
Primary language Spanish
Location Cáceres
CreditAttribution: alvar0hurtad0 commented
Status: Needs review » Needs work

Automatic Review

I'll be great if you include a link to pareview:
http://pareview.sh/pareview/httpgitdrupalorgsandbox1point212202669git

you've some authomated revision errors

Manual Review

Individual user account

Yes: Follows the guidelines for individual user accounts.

No duplication

NOIMHO it causes fragmentation, I think it's much better join the two projects Flowdock Log and Flowdock API into a single project.

Master Branch

YES: :D

Licensing

Yes: It follows the licensing requirements

3rd party code

Yes: I didn't found any 3rd party code so it's ok.

README.txt

No: The readme is very short and not clear. The project page is much more clear.

Code long/complex enough for review

Yes: a bunch of lines and functions.

Secure code

Yes. : I checked al SQL querys and all of then use de database API. Didn't found any cross site, scripting possibility.

PA robot’s picture

PA robot CreditAttribution: PA robot commented
Status: Needs work » Closed (won't fix)

Closing due to lack of activity. If you are still working on this application, you should fix all known problems and then set the status to "Needs review". (See also the project application workflow).

I'm a robot and this is an automated message from Project Applications Scraper.