Inside the Briefcase

Driving Better Outcomes through Workforce Analytics Webcast

Driving Better Outcomes through Workforce Analytics Webcast

Find out what’s really going on in your business...

Legacy Modernization: Look to the Cloud and Open Systems

Legacy Modernization: Look to the Cloud and Open Systems

On the surface, mainframe architecture seems relatively simple: A...

Still keeping your hybrid power systems indoors?  It’s time for change.

Still keeping your hybrid power systems indoors? It’s time for change.

Mobile telecommunications network equipment is expected to work without...

As the Network Changes, Engineers Are Embracing the DevOps Model

As the Network Changes, Engineers Are Embracing the DevOps Model

Businesses that have embraced digital transformation with a clear...

The 5 Most Common Application Bottlenecks

The 5 Most Common Application Bottlenecks

Application bottlenecks can lead an otherwise functional computer or...

Develop a Cloud Computing Error Logging Strategy

June 7, 2011 No Comments

Error handling is such a pedestrian issue, you take it for granted. Same thing with transaction and trace logs – these are just so obvious. In a simple virtualization cloud (e.g., a MySQL server) you can take low-level error logging for granted at several layers of the software stack.

But that doesn’t mean you can take persistence of those logs for granted. Your logs may be wiped out if you didn’t configure the VM properly, or if you didn’t pay your cloud hosting provider to persist the logs if the VM crashes. Without those server-side logs, your troubleshooting is set back several hours, if not days. In unattended systems, the lack of persistent logs becomes a serious issue, and there are good forensic reasons why you’ll want to archive logs for long periods. So don’t skimp here.

Read more…

CLOUD COMPUTING

Leave a Reply

(required)

(required)


ADVERTISEMENT

bpm online Boston May 11

UC Expo

SSOW

sptechcon

ITBriefcase Comparison Report