nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

fix OpenDeploy log viewer

NathansDIS

Does IW have any plans to implement some usable functionality to the OpenDeploy log viewer? The current interface is unusable as far as I can tell, and I resort to reading the flat files in ODNG\log. This works fine for me, but my users don't have access to these files, just the UI. It sure would be nice if my users could actually see what was deployed via the 'view log' interface in OD.

Any timeline for getting a decent log viewer implemented in this product? Thanks for your time.

Regards,

Nathan
Washington State DIS.

Find more posts tagged with

Comments

Adam Stoller

The following posts were in a thread that you contributed to a while back:

one
two
three -- Todd explicitly references feature request #32102
four
five
six
seven
eight

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

NathansDIS

Thx for the reminder Fish-

I did remember that post as I was nagged by users yet again about how to use the log viewer. The road certianly seems to be paved with good intentions and since we are already in **** with this feature, I'm hoping that we will soon be getting a vastly improved log viewer. My theroy is to keep passing on our desire for a usable feature in the hopes that someone with clout at IW will take notice, run with it, and make a new log viewer a priority for improving the product.

Anyone from Interwoven care to speak to when we can expect the feature request for an upgraded log viewer to be implemented??

Thx again,

-n

Adam Stoller

Have you at least taken the time to make sure your organization is listed among the interested parties for that feature request?

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

NathansDIS

Ya, Todd said he added us to the FR on 09/24/04 in response to my participation in the post you referenced previously. However, I haven't heard anything back from this or any of the other FRs I have been added to, but i've only been doing the IW thing for 9 months now...

-n

Migrateduser

This is something I'd like to see addressed as part of a UI update release. But this is not in plan just now.

In the meantime, I'll continue adding suggestions to the referenced feature request.

Others interested in seeing improvements to the log viewer should contact support (or me) to have your company attached to the feature request.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

not that it matters, but please add federated investors Smiley Wink

are there any FRs to consolidate IW logging or add error reporting?

NathansDIS

So, there is no time in the foreseeable future that this will be updraded? Will you be notifying people who are on the FR when this finds it way onto the product roadmap?

Thx,

-nathan

Migrateduser

> please add federated investors

Done.

> are there any FRs to consolidate IW logging or add error reporting?

Can you elaborate on those requests? By consolidating logging, do you mean combine micro and macro logs into a single log?

By error reporting, do you mean something beyond the existing OD reporting subsystem and SNMP traps?

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

Currently there are over 250 open feature requests against OpenDeploy and DataDeploy. So the challenge becomes prioritizing which features make it into each release cycle.

OD 6.0.2 is the next release. The feature set is locked and the release is entering QA in anticipation of a Feb beta. (I'll be posting more details about this release, as well as the ControlHub add-on product, soon.)

We haven't started detailed planning on the next OD release after 6.0.2 yet. That will be the next opportunity to address a portion of the 250+ open FRs, including the log viewer request.

As a product manager, I appreciate the user input because it helps me gauge demand for certain features. We've got a mechanism for tracking demand, which I use religiously. However, we don't have an automated way to inform those customers attached to the various FRs of their disposition.

So, my approach has been to post details about what's coming in a release so that there are no (or minimal) surprises. In addition, you can always check with Tech Support (or me directly) on the status of a particular FR.

I hope that helps...

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

> Can you elaborate on those requests? By consolidating logging, do you mean combine micro and macro logs into a single log?

i mean in a more general sense...TS, DD and OD have a myriad of log files spread out in different folders all over the installs. it would be nice if there was a central location/access point for them all or at least the critical ones

> By error reporting, do you mean something beyond the existing OD reporting subsystem and SNMP traps?

again i mean more generally...all our error reporting for TS, OD, and DD is done thru customized perl scripts which parse the flat log files (i.e. iwddd.log). it would be nice if there was something more robust/user friendly

NathansDIS

Hi Todd-

It certianly sounds like you are doing the best with the tools you have. Could you please consider making this FR a part of the next release regardless of the real or perceived demand? We have customers who demand to use FTP to check that files are being deployed to their website because there is no way to check which files were deployed with OpenDeploy logviewer. Having to use FTP to check which files were deployed really flies in the face of the concept of content management.

How do you recommend that the OD users check which files were deployed? Is there a workaround that anyone is using? Thx,

-Nathan
Washington DIS

Migrateduser

Thanks for the clarifications.

With respect to the logs, OD/DD 6.0.1 consolidates the logging of both products. This is, in part, the result of the tighter integration of the two products as compared to the 5.x generation.

TeamSite is really a separate product from OD/DD. So, I'm not sure consolidating logs from both products would be appropriate. I'm not personally familiar with TeamSite logging, but if you feel that its logging could be improved, then you should file a feature request against TeamSite with your suggestion. Tech Support or a TeamSite product manager should be able to help with that.

As for reporting, take a look at the OD reporting feature (introduced in 5.6) and the TeamSite reporting feature (introduced in 6.5.)

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

Migrateduser

Try using the OD reporting feature, which was introduced in OD 5.6. This will tell you which files were deployed.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

NathansDIS

Unfortunately support had me disable the reporting feature when we upgraded to OD 6.0 due to horrendous performance. At the time, support said that the supplied database was intended for POC only, and not for production systems. I found it strange that the DB was to blame even though the upgrade cleared out the DB tables to change to the new schema. Any idea if this performance problem has been addressed in any of the subsequent OpenDeploy service packs or patches?

Thx for your time,

-Nathan

Migrateduser

Yes, the event reporting issue in OD 6.x is being investigated by engineering. I don't think it has anything to do with the demo reporting database, nor with the bundled database used by each base server or receiver for store-forward.

Rather, I think it is related to the event publisher (i.e., the base server or receiver) attempting to publish events when there's no event subscriber (i.e., the OD admin server.) If you want to give it a try, start the base server with event reporting enabled. Then start the OD admin server with event reporting enabled. If everything starts ok and the subscription connection is intact, I think the performance issue is not present.

There is an REA open for this. (REA stands for Request for Engineering Assistance.) Please contact Tech Support and ask them to attach your support case to REA #57721.

Also, note that if you end up using the OD reporting feature in production, please configure it for a commercial database rather than the bundled demo database.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com

NathansDIS

Thx for the info Todd. You're one of the good ones...

-nathan
Washington DIS

Migrateduser

You can check which files were deployed via the OD gui but its not very nice...

deployments > view deployments > name

click on one of the "view log" action buttons in the bottom frame. arrow back and page and u get entries like this:

client: Sending [.\daf\pdf\G28951-01.pdf] [reason src-is-newer] -- OK

it would be far nicer if these were all aggoed into 1 file or central report.

todd, i was more concerned with error reporting than say reporting on how many deployments were executed. are there any current/planned improvements for error flagging/capturing/reporting and notifications? as i mentioned our im not a huge fan of our current process of utilizing perl scripts to traverse flat log files

Migrateduser

The OD reporting feature tells you which deployments failed/succeeded/completed with errors, and provides a concise manifest of deployed/deleted/failed files. This is much easier on the eyes than looking at the logs, and doesn't require automated parsing. The info is also available in the reports database, in case you don't want to use the admin UI to view the info.

As for capturing additional details about failure cause in reports, this is requested in FR #36867. For now, if a report shows that a deployment or a file failed to deploy, you still need to consult the logs.

Regarding notifications, OD 6 introduced an SNMP agent that can be configured to send a trap upon receiver or deployment failure. This is in addition to the existing ability to trigger a DNR on failure, which can send an e-mail notification.

Todd Scallan
Director of Product Management
Interwoven
t: 408-530-7167
e: tscallan@interwoven.com