Giter Site home page Giter Site logo

oarevalo / bugloghq Goto Github PK

View Code? Open in Web Editor NEW
155.0 155.0 67.0 1.82 MB

BugLogHQ is a tool to centralize the handling of automated bug reports from multiple applications. BugLogHQ provides a unified view of error messages sent from any number of applications, allowing the developer to search, graph, forward, and explore the bug reports submitted by the applications.

Home Page: http://www.bugloghq.com

ColdFusion 91.98% PHP 0.35% JavaScript 5.37% Python 0.46% CSS 1.27% HTML 0.57%

bugloghq's People

Contributors

akiandy avatar aliaspooryorik avatar awayken avatar bcswartz avatar cfchris avatar coldwell avatar coryasilva avatar developerjoe avatar dfgrumpy avatar jbez avatar jimpriest avatar krunchmuffin avatar michael-zock avatar oarevalo avatar sebduggan avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

bugloghq's Issues

Add a dashboard for a global view of the current status

This would replace the initial view when logging into buglog (or maybe could be an option so users can select between the dashboard view or the current summary view)

The idea here is to provide "at-a-glance" information of what's going on, with a focus on actionable information.

Ideas for what could be on the dashboard:

  • List of X most recent reports received
  • List of top X reports ordered by count in descending order
  • List of recent rule firings (which rule has just been fired, with a link to the triggering report and a short description of what each rule means)
  • Historical chart of bug reports received (should allow to select different time units: hours, days,months,etc)
  • List of "followed" or "flagged" bug reports

Dashboard should have a similar filtering toolbar as the summary view. The filtering would affect all dashboard content.

Logging in with IE9 takes u to just a chart

For whatever reason, in IE9 only, it takes me just to a chart with nothing else on the screen. Though the URL still shows /buglog/hq/index.cfm?event=& and view source just has the tag.

Purge Scheduler Bug

We kept enabling the Purge option and it would never purge and could not figure out why. Ends up if you have purge enabled, but digest NOT enabled there's a typo in the "configureDigest" function (in BugLogListener.cfc).

If digest is not enabled, it actually removes the purge CRON job, we updated this line within the "configureDigest" function - line #444 in our copy:

<cfset scheduler.removeTask("bugLogPurgeHistory") />

TO:

<cfset scheduler.removeTask("bugLogSendDigest") />

So if digest is NOT enabled, it removes the digest CRON job - not the purge one.

Figured you would want to know-

Verbose dump data can cause a loss of queued data in the service listeners

Hi

I just encountered a problem where data can be lost because the listener can't write extremely long queue data to the database and restarting the listener will mean the loss of the currently queued reports.

In my case the method processQueue() in the bugLogListenerAsync.cfc went into the catch block, because the _insert() in the dbDataProvider.cfc was unable to insert record due to the extra data.In this case, some HTML from a remote service, whose 55,399 "slightly" exceeded the 5000 character limit in your schema (I'm dealing with a MS SQL Server, where the system wouldn't allow more than 8,000 characters anyway). ;)

Stopping and restarting the listener would mean losing the queued data, which is not exactly desirable.
Wouldn't it be better to do a "left(trim( foo ), 5000)" on the content beforehand to salvage at least some of the reported error report rather than losing all of it and a ton of other stuff caught in the same queue?

Allow users to "follow" or "flag" a bug report

On flagged reports:

  • show in dashboard if any new ocurrences of this bug happen again (same host or different host)
  • optionally receive an email whenever it happens
  • maybe allow to add notes or comments

I want to be able to tell BugLogHQ to process bugs immediately.

We have a multi-tenant application where many domains point at one codebase. We have multiple IIS servers and each has a few CF servers to spread the load. All of that is load balanced with sticky session. So... when the scheduled tasks get called, there is no guarantee what instance is being hit. And bugs are staying in the queue for a long time.

I propose (and will write) an update to "notifyService" that allows you to force queue processing immediately. I will default this to "false" for backwards compatibility.

How do you access the RSS feed?

I went to: bugLog/hq/index.cfm?event=rss and I'm prompted for a username and password. I tried my BLHQ username/password, even the admin username/password, but it never succeeds.

I love this web app...

Oscar,

Doing a quick search on google reveals that your app is one of a kind...
It makes no sense to me why there are so many so called "bug tracker" applications that ALWAYS require you to manually enter bugs that are found... when we all know most bugs are hard to find and even if they are found, they are hard to report in some form somewhere on the web.

I'm STILL interested in converting this to a SAAS offering with you.

Error when sending an issue to Jira

Clicking the "Send to Jira" link on an issue returns the following error:

Invalid element in com.atlassian.jira.rpc.soap.beans.RemoteProject - id

We have BugLogHQ 1.8.1 installed and are using Jira v5.2.11#854-sha1:ef00d61

Allow user to choose specific date range

For example, I may want to go back and look at January in detail now in May. It's currently only possible by selecting a view that allows you to go far enough back. 60 days doesn't include January, and 120 days rolls everything up to month-size blocks. I'd like to be able to look at it grouped by day, or by week, etc -- but for my chosen start and end dates.

[Enh] Dashboard: Add chart for number of bugs by application

Would it be possible to add a second chart (maybe a pie chart) below the first one that shows the number of bugs in the selected time range, grouped by application name?

We're currently integrating BugLogHQ into our internal applications and since different people are responsible for different applications (often with responsibilities shifting depending on vacation schedules), this would allow for an even quicker overview than using the summary filter or the mail summary.

Unfortunately, I'm still not familiar enough with the structure of the your main application or I'd provide a pull request myself.

Add BugLogID / link into email

When I get an email from BugLog it would be nice if it included a link back to bugLog.

This could also be cut-pasted into a ticket system, etc.

Add "checkpoint" reporting to buglog client

The idea is that the client object will have a variable persistent across the same request that the caller application can use to report checkpoints on milestones as the request gets executed. Then, if a bug report needs to be sent to buglog, an array/struct/something with all the checkpoints will be sent too. This will be helpful when trying to pinpoint the source of the errors (i.e. "how much of request was completed before the error happened?")

Example:

buglogclient.checkpoint("account created");

or can also be used to track begin/end timestamps:

buglogclient.checkpoint("expensive process","start");
.....
buglogclient.checkpoint("expensive process","end");

Also the caller application could just get the checkpoint data and output it at the end of the request as a debugging tool.

writedump(buglogclient.getCheckpoints());

Add explicit tracking of execution stack when reporting bugs

The listener should accept an array of structs consisting on:

  • template path
  • line number

This could help to quickly identify where an error is happening. So there could be a view listing template paths, line numbers and the errors that each line triggers.

Example:

\path\to\app\template\file.cfm [line 33]
   * syntax error  (23 times)
\path\to\app\template\file.cfm [line 121]
   * undefined variable (4 times)
...

Use JQuery for javascript stuff

Currently all javascript snippets are embedded on each view template; they should be refactored to a separate .js file and leverage something like jquery

Modify mailRelay to allow selecting of hosts

Hi,

We've been using BugLog for a month or two now and really like the application.

Our initial setup has been to just forward all our bugs via email to the technical team. We anticipate that we'll do this for a while still.

We have a problem though where we are getting all emails from our live hosts and development/testing hosts. We really only want emails from our live hosts. Unfortunately the mailRelay option does not allow you to select just a single host.

We did try add discard rules for our development/testing environments which didn't seem to discard the bugs. In any case, we do want a record of the bugs from our development environments, we just don't want them emailed.

Would it be possible to add a host parameter (and maybe even application) to the mailRelay rules?

Thanks for all your hard work on this project, we love it and can't wait for version 2 :)

Matt

Strip auto-generated JS from client service's CFDump

Right now the composeFullMessage() in the client component uses plain tags to output the catch and extra details. This results in the tag's generated Javascript showing up in the error results unnecessarily, because the corresponding script tags get nuked.

Due to the greedy regular expression pattern this is only a workaround, because it doesn't differentiate between JS generated by the dump tags and JS inside one of those two arguments, but the following example would solve at least part of the problem:

<cffunction name="sanitizeDump" access="private" returntype="string" hint="Performs a sanitized dump, where JavaScript has been removed to minimize XSS risks">
    <cfargument name="dumpData" type="any" required="true">

    <cfsavecontent variable="LOCAL.result"><cfoutput><cfdump var="#ARGUMENTS.dumpData#"></cfoutput></cfsavecontent>

    <CFRETURN reReplaceNoCase(LOCAL.result, "<script\b[^<]*(?:(?!<\/script>)<[^<]*)*<\/script>", "<b>(BugLogHQ: JavaScript removed to minimize XSS risks!)</b>","all")>
</cffunction>

24 hour view doesn't show current hour in the graph

I was going to try to just fix this myself and send a patch but I can't figure out where rs.criteria.startDate is being set so that I can adjust it for this view.

Basically, most views show the current hour/minute/whatever at the right edge of the graph, but the 24 hour view shows the 24 hours before now. So if the current time is 9:30am, then the graph shows 9am yesterday through 8am today.

Compare this to the 3-hour view. Current time is 10:30am, graph shows: 7am-10am, and the presumption is that the bar for 10am could just keep growing until the hour is complete.

v1.8: Two minor issues ("CFC" test and link from user edit screen to API security)

While I was trying out v1.8 to make sure it worked with Oracle, noticed two minor quirks:

  1. In the list of listeners on the "BugLog Listeners" screen, only SOAP and Post / Rest are listed. But if you click the "Test" link for either, at the bottom of the resulting test page the list of test links includes the "CFC" test option.

  2. In the new edit screen for editing a user account in BugLogHQ, the help text under the new "User API" option includes a link back to the "API Security" screen. But the URL is wrong: it's currently "index.cfm?admin.main&panel=APISecurity" instead of "index.cfm?event=admin.main&panel=APISecurity"

Mark as FIXED and archive

This would be a nice feature. Would also need a timestamp. Or even better, ability to link to the changeset in a DVCS like github or bitbucket.

RuleProcessor Error: Undefined setting 'debug.email'

After a fresh install of v1.8.2 and enabling the "firstMessageAlert" in the BugLogHQ Admin i receive the following error:

RuleProcessor Error: Undefined setting 'debug.email'

These are my settings of the firstMessageAlert
bildschirmfoto 2014-01-08 um 04 49 30

And here's the full StackTrace:

Undefined setting 'debug.email'
at components.config_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\config.cfc:27):27
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.ComponentImpl._call(ComponentImpl.java:616):616
at railo.runtime.ComponentImpl._call(ComponentImpl.java:499):499
at railo.runtime.ComponentImpl.call(ComponentImpl.java:1715):1715
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at components.baserule_cfc$cf._2(C:\inetpub\wwwroot\mnk_bugs\components\baseRule.cfc:228):228
at components.baserule_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\baseRule.cfc):-1
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.type.scope.UndefinedImpl.call(UndefinedImpl.java:700):700
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at components.baserule_cfc$cf._1(C:\inetpub\wwwroot\mnk_bugs\components\baseRule.cfc:127):127
at components.baserule_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\baseRule.cfc):-1
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.callWithNamedValues(UDFImpl.java:198):198
at railo.runtime.type.scope.UndefinedImpl.callWithNamedValues(UndefinedImpl.java:709):709
at railo.runtime.util.VariableUtilImpl.callFunctionWithNamedValues(VariableUtilImpl.java:738):738
at railo.runtime.PageContextImpl.getFunctionWithNamedValues(PageContextImpl.java:1513):1513
at extensions.rules.firstmessagealert_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\extensions\rules\firstMessageAlert.cfc:116):116
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.type.scope.UndefinedImpl.call(UndefinedImpl.java:700):700
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at extensions.rules.firstmessagealert_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\extensions\rules\firstMessageAlert.cfc:75):75
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.callWithNamedValues(UDFImpl.java:198):198
at railo.runtime.ComponentImpl._call(ComponentImpl.java:617):617
at railo.runtime.ComponentImpl._call(ComponentImpl.java:499):499
at railo.runtime.ComponentImpl.callWithNamedValues(ComponentImpl.java:1728):1728
at railo.runtime.tag.Invoke.doComponent(Invoke.java:203):203
at railo.runtime.tag.Invoke.doEndTag(Invoke.java:176):176
at components.ruleprocessor_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\ruleProcessor.cfc:79):79
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.type.scope.UndefinedImpl.call(UndefinedImpl.java:700):700
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at components.ruleprocessor_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\ruleProcessor.cfc:60):60
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.type.scope.UndefinedImpl.call(UndefinedImpl.java:700):700
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at components.ruleprocessor_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\ruleProcessor.cfc:21):21
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.ComponentImpl._call(ComponentImpl.java:616):616
at railo.runtime.ComponentImpl._call(ComponentImpl.java:499):499
at railo.runtime.ComponentImpl.call(ComponentImpl.java:1715):1715
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at components.bugloglistener_cfc$cf._1(C:\inetpub\wwwroot\mnk_bugs\components\bugLogListener.cfc:122):122
at components.bugloglistener_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\bugLogListener.cfc):-1
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.ComponentImpl._call(ComponentImpl.java:616):616
at railo.runtime.ComponentImpl._call(ComponentImpl.java:507):507
at railo.runtime.SuperComponent.call(SuperComponent.java:62):62
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at components.bugloglistenerasync_cfc$cf.udfCall(C:\inetpub\wwwroot\mnk_bugs\components\bugLogListenerAsync.cfc:60):60
at railo.runtime.type.UDFImpl.implementation(UDFImpl.java:94):94
at railo.runtime.type.UDFImpl._call(UDFImpl.java:307):307
at railo.runtime.type.UDFImpl.call(UDFImpl.java:211):211
at railo.runtime.ComponentImpl._call(ComponentImpl.java:616):616
at railo.runtime.ComponentImpl._call(ComponentImpl.java:499):499
at railo.runtime.ComponentImpl.call(ComponentImpl.java:1715):1715
at railo.runtime.util.VariableUtilImpl.callFunctionWithoutNamedValues(VariableUtilImpl.java:712):712
at railo.runtime.PageContextImpl.getFunction(PageContextImpl.java:1503):1503
at util.processqueue_cfm$cf.call(C:\inetpub\wwwroot\mnk_bugs\util\processQueue.cfm:12):12
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:834):834
at railo.runtime.PageContextImpl.doInclude(PageContextImpl.java:786):786
at railo.runtime.listener.ModernAppListener._onRequest(ModernAppListener.java:206):206
at railo.runtime.listener.MixedAppListener.onRequest(MixedAppListener.java:18):18
at railo.runtime.PageContextImpl.execute(PageContextImpl.java:2167):2167
at railo.runtime.PageContextImpl.execute(PageContextImpl.java:2134):2134
at railo.runtime.engine.CFMLEngineImpl.serviceCFML(CFMLEngineImpl.java:335):335
at railo.loader.servlet.CFMLServlet.service(CFMLServlet.java:29):29
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848):848
at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:648):648
at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:455):455
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137):137
at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:559):559
at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231):231
at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1072):1072
at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:382):382
at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193):193
at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1006):1006
at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135):135
at org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:255):255
at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154):154
at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116):116
at org.eclipse.jetty.server.Server.handle(Server.java:365):365
at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:485):485
at org.eclipse.jetty.server.AbstractHttpConnection.headerComplete(AbstractHttpConnection.java:926):926
at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.headerComplete(AbstractHttpConnection.java:988):988
at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:635):635
at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:235):235
at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82):82
at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:627):627
at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:51):51
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608):608
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543):543
at java.lang.Thread.run(Thread.java:722):722

Latest update

Not a huge deal, but the versiontag was not updated to reflect 1.7.4 and the bugloghq.com site still says 1.7.1.

v1.8 Bug: Couple of valueList() statements that throw syntax errors

There are 3 instances in the BugLog code:

components/hq/appService.cfc, lines 692 and 703
components/bugLogListener.cfc, line 333

...where the variable inside the valueList() function is enclosed in double-quotes. In ColdFusion 9.0.1 (on my box, anyway), those lines throw the error "Complex constructs are not supported with function ValueList" and prevent BugLogHQ from even running.

Removing the double-quotes solves the problem.

v1.8 and Oracle: Need shorter constraint name in Oracle install script

Oracle sets a 30-character limit on constraint names, and the final foreign key constraint name for the new BL_UserApplication table exceeds that limit.

Easy fix: just change constraint name from "fk_userApplication_ApplicationId" to something like "fk_userApplication_AppId"

With that fixed, the install script runs perfectly. And that was the only Oracle-specific issue I found with version 1.8.

General Settings: Setting Feeds to Public

I tried to set the Allow Public Access To RSS feed to public and get an error after submitting the form.

Here are the details:
Could not find the ColdFusion component or interface listener. Ensure that the name is correct and that the component or interface exists.
The error occurred on line 24.

File: BugLogHQ\listeners\bugLogListenerWS.cfc:24

Let me know if you need some more info.

Use of cgi.http_method in BugLogListenerREST

While working on making BugLogHQ compatible with Oracle (looking good so far, should have code to contribute back soon), I got an error while running the test of the REST listener on my local machine (Mac OS, Apache, CF 9.0.1). Tracked the error back to line 21 of BugLogListenerREST.cfm, where the source value for the bug log entry is pulled from "cgi.http_method".

Unless I'm missing something, there is no "http_method" key in the CGI scope. This line should be using cgi.request_method. Once I fixed that line on my machine, it worked fine.

Add "Tags" for categorizing different types of logging.

We want to use BugLogHQ for our info logging as well as bug logging.

Because we have an enormous application, I would like to split the logging up by feature.

Being able to add a "Tag" or "Tags" to an entry, would allow me to do this. And others might find a use for it too.

Invalid API Key while deleting Issues

When i would like to delete some issues i get the error "Invalid API Key".

I get this error only when i select follow option:

"Delete all reports with the same message on this application"

And only when i have a lot of errors with the same message, i have now 3000.

Timezone setting causes failure in application

Changing the Timezone in the buglog-config.xml.cfm to UTC-5 (or some such value) causes the application to report an error with the format.

Expression Exception - in C:_web\bugLog\hq\includes\udf.cfm : line 76
{ts '2013-06-17 07:59:56'} is an invalid time format.

To fix this, remove the {ts } portions of the date time return strings in /hq/includes/udf.cfm inside of the dateConvertZ(). (This is on CF9)

return "{ts '" & DateFormat(targetDate, "yyyy-mm-dd ") & TimeFormat(targetDate, "HH:mm:ss") & "'}";
should be
return DateFormat(targetDate, "yyyy-mm-dd ") & TimeFormat(targetDate, "HH:mm:ss");

return "{ts '" & DateFormat(targetDate, "yyyy-mm-dd ") & TimeFormat(targetDate, "HH:mm:ss") & "'}";
should be
return DateFormat(targetDate, "yyyy-mm-dd ") & TimeFormat(targetDate, "HH:mm:ss");

return "{ts 'yyyy-mm-dd HH:mm:ss'}";
should be
return 'yyyy-mm-dd HH:mm:ss';

executing listener tests from settings panel

Version: 1.7.4
Server: CentOS / Tomcat 7.0.35 / Railo 4.0.4

I'm getting an uncaught exception while trying to execute a test of the API listeners. The error message reads "Invalid API Key". Adding the apikey URL parameter solves the issue. Should this value be appended to the "test" hrefs on the listeners page?

I'm new to BugLog, so I might be missing something entirely.

"Invalid data '' for CFSQLTYPE CF_SQL_NUMERIC." when trying to sign in or "The getUsername method was not found."

Just installed BugLog for the first time. After changing the dbtype to mssql I got this error "Invalid data '' for CFSQLTYPE CF_SQL_NUMERIC." when trying to sign in. The solution was to add a record to bl_userApplication with userID=1 and applicationID=1. Maybe this should be in the sql script?

More details - I was not able to see anything, but the message(no stack trace) until I fixed the problem, so I had to dig in to the code to debug:
Message: Invalid data '' for CFSQLTYPE CF_SQL_NUMERIC.
Type: Database
Detail:
Tag Context:
I:\G\wwwroot\buglog\components\lib\dao\dbDataProvider.cfc [23]
I:\G\wwwroot\buglog\components\lib\dao\DAO.cfc [31]
I:\G\wwwroot\buglog\components\appFinder.cfc [42]
I:\G\wwwroot\buglog\components\hq\appService.cfc [692]
I:\G\wwwroot\buglog\components\hq\appService.cfc [657]
I:\G\wwwroot\buglog\hq\handlers\general.cfc [452]
I:\G\wwwroot\buglog\core\coreApp.cfc [210]
I:\G\wwwroot\buglog\core\coreApp.cfc [95]
I:\G\wwwroot\buglog\hq\index.cfm [27]

I was also seeing the following error when resetting the app:

The getUsername method was not found.
Either there are no methods with the specified method name and argument types or the getUsername method is overloaded with argument types that ColdFusion cannot decipher reliably. ColdFusion found 0 methods that match the provided arguments. If this is a Java object and you verified that the method exists, use the javacast function to reduce ambiguity.

The error occurred in I:\G\wwwroot\buglog\hq\includes\header.cfm: line 24
Called from I:\G\wwwroot\buglog\hq\layouts\main.cfm: line 32
Called from I:\G\wwwroot\buglog\core\core.cfm: line 2
Called from I:\G\wwwroot\buglog\hq\index.cfm: line 31
22 : Settings
23 :   |  
24 : #request.requestState.currentUser.getUsername()#
25 : ( Log off )
26 :

1.8 roadmap/todo?

Do you have a general list of stuff that still needs to be implemented for 1.8?

As you can see, your project has attracted a lot of attention because it's so useful and many of us would be glad to help out. So, knowing which items could be implemented by us so you'll have more time for others would be quite helpful.

Add option to add user comments to bug reports

On every report any user can add a comment or note. Then whenever the same type of bug happens again (maybe by comparing checksum or some other mechanism), the saved notes will be displayed again. The idea is that the notes could refer to how to debug a particular type of error, or special instructions that needs to be followed when a particular error happen.

SQL "null" argument still needs to be set in a few spots

Seems there are still a few cases similar to issue #72

In this case it happened while I was viewing a bug entry and wanted to delete the entry along with all its siblings.
Database in question is an MS SQL Server, though setting the "null" argument in the cfqueryparam tags should probably be a more versatile remedy.

Exception Summary
Application:    bugLogHQ
Host:   intra1
URL:    http://intra1/buglog/hq/index.cfm
Server Date/Time:   03.12.2013 10:02
Message:    Invalid data '' for CFSQLTYPE CF_SQL_NUMERIC.
Type:   Database
Detail:     
Tag Context:    
Y:\intranet\bugLog\components\lib\dao\dbDataProvider.cfc [64]
Y:\intranet\bugLog\components\lib\dao\DAO.cfc [47]
Y:\intranet\bugLog\components\hq\appService.cfc [318]
Y:\intranet\bugLog\hq\handlers\general.cfc [524]
Y:\intranet\bugLog\core\coreApp.cfc [210]
Y:\intranet\bugLog\core\coreApp.cfc [95]
Y:\intranet\bugLog\hq\index.cfm [27]
Script Name (CGI):  /buglog/hq/index.cfm
User Agent:     Mozilla/5.0 (Windows NT 6.1; WOW64; rv:26.0) Gecko/20100101 Firefox/26.0 ColdFire/1.11.208.251
Remote Address:     192.168.110.79
Referrer:   http://intra1/buglog/hq/index.cfm?event=entry&entryID=313771
Query String:   
Request Method:     POST
ColdFusion ID:  [SESSION]      CFID = - ; CFTOKEN = — ; SESSIONID = 84309817417cbff85cdd6869344e4bf17497
[CLIENT]      CFID = — ; CFTOKEN = —
[COOKIES]      CFID = 9464695 ; CFTOKEN = 68838170 ; JSessionID = 84309817417cbff85cdd6869344e4bf17497

Exception Info
Suppressed:     Empty array
SQLState:   n/a
sql_type:   CF_SQL_NUMERIC 

Too many redirects

I have just set up the app but cannot get to the Admin screens. The test page at http://mysite.local/bugLog/test/client.cfm works fine but when I go to /buglog/hq/index.cfm I get the following:

The webpage at http://mysite.local/buglog/hq/index.cfm?event=login&nextevent=login&nextevent=login%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin%2Clogin& has resulted in too many redirects.

Has anyone else seen this?

Changing email server

I would like to have the option of specifying a different email server than the CF server default. We use sendgrid.com to send emails, but I don't want to have to use it for this since it eats up credits that would be used for client emails.

Thanks!

Design is gone - or im dump

Or to be correct: The design has never appeared :(
I've downloaded BugLogHQ v1.8.2 and installed it on my server under the following URL:
http://bugs.mandelkind.ch/

It seems that BugLogHQ is not meant to running on its own URL - what i hardly believe - or I'm missing something.

A quick hint into the right direction would make me very happy!

Also, is it possible to run BugLogHQ without adding any mapping to the Server?
If so, what I have to do to make this possible?

Many Thanks!!

Dashboard error due to localized (default) date

Already reported this through the Google group, but here's a repost to be on the safe side:

I just tried the stable and (1.7.4) the beta version (1.8) in a VM with CF9.0.2 and both versions seem to experience a "The STARTDATE argument passed to the searchEntries function is not of type date." error right after installing the application.
Only change to the vanilla config was changing the "mysql" to "mssql" to get it to work with a SQL Server 2008 Express instance.

Tag context (taken from 1.8):
C:\www\buglog\components\hq\appService.cfc [112]
C:\www\buglog\hq\handlers\general.cfc [138]
C:\www\buglog\core\coreApp.cfc [210]
C:\www\buglog\core\coreApp.cfc [95]
C:\www\buglog\hq\index.cfm [27]

The culprit seems to be a localized date ("Mai, 14 2013 11:35:37") on this German system, as seen in a dump file generated by adding a writeDump(criteria) to the dashboardContent() in the handlers/general.cfc
Without taking too close a look at the source, my first suspect would be the line "startdate = now()" in the method normalizeCriteria() of the same component.

Thanks in advance for taking a look at the file in question.

Add a listener that works with Amazon's SQS

The idea is that a custom buglog client instead of calling the buglog server directly, will put the bug reports in an Amazon's SQS queue. Then on the server side, a listener will regularly poll the queue and obtain the reports from there.

This would help by decoupling the client application with the buglog server.

Add "Template" and "LineNumber" to Entry schema.

In our old bug log that we wrote internally, we had the template and line number in the entry. So, doing aggregates and searching by template were easy. Would you be opposed to adding these as optional properties when submitting an entry?

Official constant for CFDump's "top" parameter in CF client service

This is somewhat related to the sanitizeDump() introduced in issue #30.

When dumping out extra data, related ORM entities can quickly blow up into a ton of used memory, because by the default the "top" parameter of the tag is set to 9999, meaning the tag will cascade down the next 9998 encapsulation instances as well Resulting heap memory errors due to this are not that uncommon in some more complex applications.

Adding something like "variables.max_dump_depth" would make it the user's responsibility to specify that.

Making it an optional argument for the notifyService() would allow even for more flexibility, but probably cause more work as well, since it changes the facade of the interface (might have top be reflected in other client services).

Send to Trello

Trello recently added the ability to create cards via email. It would be cool if every bug-detail page showed a "send to trello" button that would create a trello card linking to the current bug. I haven't dug into the functionality much yet but I expect it's as simple as subject, body, to-address, so you should only need to save a trello email address in your config.

Certainly would require more research into the Trello feature, but just wanted to get this idea out of my head and into an ER. :)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.