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; } } }

Status of deployment without parsing logs?

System

OD 6.2.1
Solaris

Wondering if it's possible, or if there's a mechanism in place (CLT or ENV variables, etc) to determine the status of the files in a completed deployment, without having to parse the logs to get that information. Status meaning the deployed/deleted/failed status for each file. I've skimmed the docs, but don't see anything.

The history behind this is that we still have an issue where sometimes files are being deployed as deletions, because OD is not seeing them in STAGING, when they should actually be in STAGING and should be deployed as regular content. This is wreaking havoc when it happens because as far as the deployment is concerned, it is a successful deployment - there's no indication that anything didn't work properly until the file is noticed as missing from the website. Not good. So while IW is pondering what's wrong (for 2 months now), we are having to have someone wake up in the middle of the night a couple times a week to verify that deployments scheduled at 2:00 am are actually working properly. There appears to be no solution on the horizon from IW, so we'd like to try and automate the detection of the problem by writing a DNR script that wakes up after a deployment, checks the status of each file, and if it deployed a deletion of a file, and that file exists in the workarea, send out a page to the on-call.

If anyone has any other ideas, I'd welcome them. I'd like to avoid having to parse the logs for this information (there are 4 logs with each production deployment), but if I have to I will. The reason I don't want to parse the logs is because I'd have to do it in shell script, and I don't really know shell script - we are not allowed to use perl here. Don't ask. Just don't.

Find more posts tagged with

Comments

nipper

You can write a DNR to keep tract of this information. I did this a number of years ago, just dumped the filename, status and date into a DB table.

Of course it is easy in Perl. But since you are a hightly paid contractor, I imagine you would do it in Java, taking several hours longer to write.

Seriously what it is the issue with writing a DNR ? That will know what it was sent and processed.

Migrateduser

You can write a DNR to keep tract of this information. I did this a number of years ago, just dumped the filename, status and date into a DB table.

Of course it is easy in Perl. But since you are a hightly paid contractor, I imagine you would do it in Java, taking several hours longer to write.

Seriously what it is the issue with writing a DNR ? That will know what it was sent and processed.

I'm not sure what you're asking me. Seriously - I'm not even trying to be a smartazz.

My main question is - can you get this information from somewhere easy, so I don't have to parse the logs to get it? I will likely be using shell scripting, which I am not really familiar with, so I'd like to keep it as simple as possible. Not using Java, unless I absolutely have to.

Or is parsing the logs the only way to get this info?

nipper

OK, so you basically have 2 choices if you want to use OOTB DNR.

IWOV includes examples for Perl and Java.

When a DNR is kicked off, the manifest is fed to the process via STDIN. An example is in $ODHOME/solutions/perl/manifest.data

That can easily be parsed by Perl or Java. You *should* be able to get the data in a regular shell script as well. If you need to parse (which you will) you will need to use awk. By then you will be cursing me. After the data is parsed, you need to figure out what to do with it.

ISCBorisB

If you have Perl installed on Target you can use IWXML Module to obtain succeeded/failed File lists, see for example [thread=1037]here[/thread]

Oops - haven't noticed strict Perl ban - sorry

nipper

.....we are not allowed to use perl here. Don't ask. Just don't.

Bo, I certainly agree & I think Smitty does, but his boss does not.

vpatel

Have you looked at this class: CSDetailDeploymentStatus?

Not sure if this will have the level of info you are looking for. I can check if this will have the necessary info that you may need but it may take a few days for me to test it out.

HTH!

Migrateduser

OK, so you basically have 2 choices if you want to use OOTB DNR.

IWOV includes examples for Perl and Java.

When a DNR is kicked off, the manifest is fed to the process via STDIN. An example is in $ODHOME/solutions/perl/manifest.data

That can easily be parsed by Perl or Java. You *should* be able to get the data in a regular shell script as well. If you need to parse (which you will) you will need to use awk. By then you will be cursing me. After the data is parsed, you need to figure out what to do with it.

That was very helpful. I will ask one of my coworkers who knows shell how to read STDIN in a shell script. Thanks - this is great news!

Migrateduser

If you have Perl installed on Target you can use IWXML Module to obtain succeeded/failed File lists, see for example [thread=1037]here[/thread]

Oops - haven't noticed strict Perl ban - sorry

Boris - you meanie. I could do this in perl in 5 minutes. They just won't let me. Thanks for the tease, though. Smiley Tongue

Migrateduser

Have you looked at this class: CSDetailDeploymentStatus?

Not sure if this will have the level of info you are looking for. I can check if this will have the necessary info that you may need but it may take a few days for me to test it out.

HTH!

I don't want to use Java for this, but thanks.

ISCBorisB

Boris - you meanie. I could do this in perl in 5 minutes. They just won't let me. Thanks for the tease, though.

Wasn't teasing - I swear Smiley Happy

. I really have not noticed until your "Do not ask!" remark to Andy

nipper

Boris - you meanie. I could do this in perl in 5 minutes. They just won't let me. Thanks for the tease, though.

Yea well you can write it in 5 minutes, but seeing the quality of Perl you write, I think we would all be able to buy plane tickets for about $5 each way shortly there after. Smiley Tongue

vpatel

I don't want to use Java for this, but thanks.

This is interesting -- Perl/shell scripting is out and you don't want to use Java. Just out of curiosity -- do you have some perceived solution in mind already here and just trying to validate it?

Adam Stoller

This is interesting -- Perl/shell scripting is out and you don't want to use Java. Just out of curiosity -- do you have some perceived solution in mind already here and just trying to validate it?

perl is out (I've been where he is - the IT folks don't mind using Perl, but the business side does) - and he said he's hoping to avoid java. Shell scripting is still a possibility.

The problem is that shell scripting doesn't provide good robust XML parsing (which the STDIN input from OD is in) - but you should be able to do something with grep / sed / awk in shell to get the desired information out of the data.

Migrateduser

perl is out (I've been where he is - the IT folks don't mind using Perl, but the business side does) - and he said he's hoping to avoid java. Shell scripting is still a possibility.

The problem is that shell scripting doesn't provide good robust XML parsing (which the STDIN input from OD is in) - but you should be able to do something with grep / sed / awk in shell to get the desired information out of the data.

Yes - thank you for clarifying. With Andy's help I was able to get the status of the deployment using a DNR on the source side (in perl as a test). So at least I know the format of the data I'm getting. Now I can try and figure out how to do the actual task in shell. I'm still going to try and convince them to let me do it in perl sine it is a temporary solution.

Also may go in a different direction. There are a few options here.