Monday Monitor Tips: Oracle Custom Metrics

One of the popular features of Redgate Monitor has been the ability to add custom mertics for various purposes. This has been popular, and along with our curated list at sqlmonitormetrics.com, it’s a feature that’s used by many.

It has been a SQL Server only function for awhile, but customers have requested other platforms. We’ve added the capability for Oracle and PostgreSQL.

This is part of a series of posts on Redgate Monitor. Click to see the other posts.

Adding Custom Metrics

You can see on my custom metric config page that I have a few business metrics added. I recommend these to customers as often a business metric catches an issue before it appears in Perfmon type data. Let’s add a new metric. I’ll click the

2026-04_0236

I’ll click the “Add a custom metric on the right side” and will get a new form.

2026-04_0237

This form used to be mostly the same, but the “Choose where to collect data from” didn’t have a drop down. It only had the 1. Select instances and the 2. Select databases (to the right). This new drop down is where you pick the platform.

2026-04_0238

If I click the drop down, I see three choices: SQL Server, Oracle, and PostgreSQL.

2026-04_0239

I can select Oracle and my select database section disappears. This is because an instance and a database are the same thing in Oracle.

2026-04_0242

If I select PostgreSQL, I can still select databases.

2026-04_0240

The rest of the form works the same way. When I’ve selected Oracle, I get a default query listed that lets me know the structure of my result set. I need to return an integer with the con_id, a metric value that is a scalar and an optional string with details.

From there things work as they do with other metrics.

Summary

This post shows a new capability in Redgate Monitor for Oracle, where you can track your own data, as you see fit, and then let Redgate Monitor alert on changes, graph this over time, and help you better understand your system.

We are enhancing and adding to Redgate Monitor every week, but there are always more things that many of you want, and custom metrics give you the ability to choose what you want to monitor.

Redgate Monitor is a world class monitoring solution for your database estate. Download a trial today and see how it can help you manage your estate more efficiently.

Posted in Blog | Tagged , , | Leave a comment

Working Better Under Pressure

One of my colleagues wrote a great post about DBAs and developers, about how a DBA’s pushback on bad code isn’t to be difficult, it’s because they can see the future. I never thought of myself as a modern-day Nostradamus, predicting the future of system performance. Apparently I had another title besides DBA.

Working under pressure and with short deadlines often leads to short cuts. I’ve made them. I’ve implemented quick hot fixes. I’ve forgotten to port changes back to development databases. I’ve increased our tech debt load, just to solve a more immediate problem.

The challenge is cleaning things up later, when we have more deadlines and things to fix. It seems that we never have enough time to do the job the way we would like, and there’s certainly no time to go back later and fix things. Most management won’t make this a priority until things get so bad that we have to rewrite a lot of code (which we should never do).

DevOps, pipelines, automations, and yes, AI, helping can reduce some of the tech debt we create if we use those tools appropriately. Which is a big IF. Often we have more immediate pressures that prevent us from finding time to invest in our systems or in ourselves.

Getting a handle on bad code, checking it early, and doing so every time with automation can help prevent some of these issues, even when we are in a hurry. That’s why it pays to adapt our work and learn from others. Listen to that DBA that keeps your systems alive. Listen to the DevOps engineers that want you to automate things. Certainly, make them prove their suggestions work, but adopt those patterns. Learn to work with them, rather than against them.

They can see the future.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

Posted in Editorial | Tagged , , | 1 Comment

A New Word: Soufrise

soufrise – . The maddening thrill of an ambiguous flirtation, which quivers in tension halfway between platonic and romantic – maybe, but no, but maybe – leaving you guessing what’s going on inside their chest, forced to assume that at any given moment their attraction is both alive and dead at the same time.

I don’t think in terms of romance here, having been married for nearly 28 years, but I do think about this in terms of my career.

When I’ve been approached about opportunities or jobs, or someone expresses interest (or I do), it feels a little like soufrise. It’s both a real opportunity or they really want to hire me, like a romanace. Or maybe it’s just a conversation that’s exploratory without any real intention of moving forward (platonic).

This is a hard place to be, where you might want things to go one way or the other, and the other party might feel differently.

To me, this is where communication matters, though I certainly understand not necessarily wanting to answer the question about whether this is a romantic or platonic relationship.

From the Dictionary of Obscure Sorrows

Posted in Blog | Tagged | Leave a comment

Who is Irresponsible?

There was a post on X recently from a founder in the EU about an engineer using Claude and ChatGPT to build a feature. I am not sure how true these posts are or if they are designed to just create engagement, but it’s still an interesting topic. The part that makes me think is that (supposedly) the engineer was fired because their “data” (code) was sent to American servers. The code was then deleted and the feature will be built without AI.

First, read some of the responses before you form an opinion. There are some funny ones in there. There are a few I think are overblown and silly, and I skim past them. Someone is always more upset than I am, and more than I think they rationally should be, so I tend to let their outrage flow by me.

There are two interesting things here. First, the debate about sending data to America. There certainly is some cause for concern here if data is being sent to a place outside of the EU where GDPR rules might apply. There possibly could be some legal issue here, though I doubt some of the responses about all code being compromised are an issue here. I don’t think code is PII, though if it were re-used or appears in AI output, perhaps investors could sue this company.

The second thing here is whether someone should be fired for doing this. There might be a policy and some training about not doing this, and in that case, perhaps the person should be fired. However, I find this kind of thing happening too often, and it’s the type of thing that has happened before AI where people used outside sources (SQL Server Central, Stack Overflow, etc.) to post code in a question and get an answer. And then often use that code without changing or testing it.

Is this rational? Some people might say yes, some no, many unsure. In the past, before AI, what would you think? To me, sometimes there have been solutions engineers have found but couldn’t use code written by someone else. There are real IP/copyright concerns here. You could rebuild the solution, rewriting the code, which in some sense is what Google did with Java APIs and successfully defended that effort. If another human or an AI gives you code, can you rewrite that code, keeping the same idea for the solution?

I think that in most cases this is acceptable. I use AI for a lot of things and I throw away a lot of AI output, but it often gets me started down a path, whether in writing, coding, or something else.

Who was more irresponsible here, the founder or the engineer? I think the former.

Steve Jones

Listen to the podcast at Libsyn, Spotify, or iTunes.

Note, podcasts are only available for a limited time online.

Posted in Editorial | Tagged , , | Leave a comment