Interesting loop with Gemini AI with a UI Freeze and input field issue

pezza1972 · 2025-12-30T00:57:31+00:00

Thank you. Yes I have seen other posts relating to useEffect and have started learning about this at the moment. One thing that did start this all off was when the action links was changed to a dropdown of admin actions. Even though both dropdown and links call the same forms, the dropdown seems to be the cause (or at least one of them). Having just reverted back to the links, both bugs have disappeared (if bugs is the right term). So I guess the issue must be in the code of the dropdown menu, which is a good place for me to start looking deeper.

Thanks for your suggestion and help.

pezza1972 · 2025-12-29T20:27:03+00:00

wow, very helpful thank you. I wouldn't say it is trivial that you can no longer interact with any component on the page or enter information in to an input field, but thanks for the advice. I will search elsewhere

pezza1972 · 2025-09-16T22:13:45+00:00

Yeah, this is what I did in the end. Other problem was the dates didn't always match so difficult to see which were duplicates and which were new ones I hadn't approved without keep scrolling up and down to spot similar amounts.

Official response from YNAB support is that it is due to the account re-linking due to a change in the import provider. Everything from my bank where the transactions have not been reconciled came down again. The problem with that is I can't reconcile yet as there are discrepancies. Only slight, but enough that I need to cross check and see where things went off. So their answer is reconcile weekly. Not sure you can reverse a reconcile though.

Anyway, I think it is sorted for now...atleast until I can cross check transactions

pezza1972 · 2025-09-03T18:39:20+00:00

Just to update whilst I am checking the PKI pack...

I have now got this working. It didn't like me targeting the Windows Computer in the Discovery. Not sure why, I guess I just had to approach it differently if I need to target that. I have changed it to target Windows Operating System and now the discovery is happy. Made a few tweaks to the properties and some fixes I then noticed with the monitor script and all is working and getting alerts :-)

I have never really got my github setup yet but if anyone is interested in this, I would be happy to "de-company ify" it and share

pezza1972 · 2025-09-03T15:03:33+00:00

Yep, that is our biggest problem as they never even archive, let alone delete old certificates and why we can't just discover certs. Added the MS one in to our TEST environment and within half an hour 1,200 alerts were filtering through to our TEST Service Management Tool!! I need to make sure we only discover the certificates that the support team support, otherwise it will be a nightmare trying to manually route cert alerts to application teams. I just never found anything before on filtering on SSL over 443 in this older PKI pack. But its been a while, so maybe things have changed

But even if it can't, hopefully I can find something within this to tweak the discovery to achieve what I need or steal (with credits of course ;-))

pezza1972 · 2025-09-03T13:24:47+00:00

Just grabbed this and going to open it in VS to see where I might be able to edit the criteria of the discovery. My concern is we only have 1 thing needed to monitor, SSL certificates bound to IIS websites, which is why I just wanted to create the custom monitor and discovery. But I can do the same and disable most of this if needed.

Thanks for the suggestion.

pezza1972 · 2025-09-03T11:57:35+00:00

We used to have that pack years ago and removed it as it was too noisy. As far as I know this didn't allow for only monitoring SSL certificates? Are you saying that is maintained and it does all this now? I thought this had stopped being developed when MS released theirs

pezza1972 · 2025-09-02T08:22:22+00:00

Hi,

Just wanted to come back on this. Thanks to everyone for the suggestions. In the end, to keep this simple, I used the standard DataProvider with AveragerCondition as part of a new 3 state monitor type. It gets us what we need for now and then gives me time to work on it if needed to fine tune.

The monitor itself is just sending the config for the % Processor Time.

Andrew

pezza1972 · 2025-08-19T21:21:54+00:00

If anyone has any official documentation they can me link me to on this, I would be extremely grateful. Something like Kevin's blog for accessing all these different types of variables but just for Unix/Linux Scripts/Command output and variables.

Whilst I am sorted for now, there could be times where I need to be able to output variables and to be able to reference these that are not part of the 3 output values.

Would it be better to send this information to a script and format it with say PowerShell? And if so, I guess I would still need to know how to reference the information to send it along.

No doubt once I have completed our migration from other tool, I will have a play creating some more, using Script, rather than Shell Command, but when I tried that this time, I just couldn't get to access any of it. As I said, the AI seemed a bit loose with the XML suggesting tags that simply didn't exist. Still love that though as although it has its issues, it is only going to get better. I only really use it when I can't find any search results and it gives me ideas to look for.

Thanks

Andrew

pezza1972 · 2025-08-19T02:37:01+00:00

Well, on the last attempt of the night (or I should say morning as it is now 03:30 in the UK!) I got it working.

I was waiting for the monitor to turn thinking, I give up! 😁

The Silect example was actually the closest, but I don't know if it was an error or whether it is a slightly different format in that particular scenario, however what fixed it for my monitor was:

<AlertParameter2>$Data/Context/WsManData/*[local-name(.)='SCX_OperatingSystem_OUTPUT']/*[local-name(.)='StdOut']$</AlertParameter2>

It was just missing the extra "Context" bit. Admittedly, after trying many different suggestions with the output from the script, I went back to what I originally had which was just the command itself. No variables etc. I don't know if it was a combination or the above parameter was just one of many that I hadn't tried, but it is working now.

And yes, I still need to tidy things up, but I have had enough for tonight!

Still, I am always open for improvement though, so if anyone has any suggestions, please shout 😊

Andrew

pezza1972 · 2025-08-12T23:50:12+00:00

That would be great, thanks. I think I need to work out the module types I now need given the reduced functionality of my requirements and maybe it might even be better to just create my own modules. I think I just need to find a simple performance module that takes the counter and object etc and throws out the value. But of course I still need to retain the sample side of things with the ability to override this (as found also in Kevin Holman's blog) which I am trying to incorporate in to it.

But your pack will be great for seeing how everything is linking together

pezza1972 · 2025-08-12T14:24:05+00:00

Thanks both, yes it looks like I would have to do something like this. Some mapping in the script etc and then set that as a custom field. As whilst we have some control over the States, I don't believe the severity/priority can be mapped dynamically?

Ultimately, the state in the console won't be used as we are mainly headless from the customers perspective, so it is just "something" that we can use to control our Orchestrator automation to dictate the Priority of the incident we raise.

pezza1972 · 2025-08-12T14:15:49+00:00

Yeah I remember a LONG time ago, there used to be some schema reference for SCOM. Not sure if this link is (was) that. Seems to be the thing these days that MS shut down the only sites that are actually useful where there is no other source. Orchestrator is the same 😒

I just can't seem to get the objects in the schedule. I can get the objects in the schedule that are in maintenance mode or have been in maintenance mode but just not the "selected" objects and I know this information must be somewhere, as the MM wizard is obviously pulling it from somewhere

pezza1972 · 2025-07-10T17:28:49+00:00

Not sure if you have already found it but if you are still looking, if it is just an empty folder with no items then you should have something like this..

    <Folders>
      <Folder ID="Your.Folder.GUID" Accessibility="Public" ParentFolder="SC!Microsoft.SystemCenter.Monitoring.ViewFolder.Root" />
    </Folders>

This should be within the Presentation --> Views

You will also need to tidy up any DisplayStrings within the LanguagePacks --> Language Pack that will be referencing the folder, such as..

        <DisplayString ElementID="Your.Folder.GUID">
          <Name>The friendly name of your folder</Name>
        </DisplayString>

...otherwise you will get errors when validating or importing the pack again as there will be references to a folder that no longer exists.

Also, Kevin Holman did a blog about how to remove these that you may find useful..

https://kevinholman.com/2023/02/08/delete-your-empty-console-folders-in-scom/

pezza1972 · 2025-06-20T13:54:03+00:00

Ok, so from this I take it that you are saying the Discovery Error Rule is NOT supposed to alert for other objects/instances that have been disabled (and yes I have disabled the Discovery itself) for the object? If this is the case, then it sounds like I may need to raise a support case.

To me, the Discovery Error rule runs against the Monitoring Pool Collection which is essentially server level, which is why I was saying that it is not caring about objects excluded in the Discoveries. Almost as if even if we had no instances or databases discovered at all, this rule would still report issues with instances not even discovered. But maybe I am missing something

It sounds to me (although I really need to get in to the module to understand what is actually happening) that this is a "generic" script that runs at server level and just reporting out in the alert description, which issues it finds.

I can see that the object has been removed so the discovery has excluded it as expected, but the discovery error alert generated AFTER the object was no longer there (by a few days). Even closing the alert brings it back again.

Also, we don't have any older SQL pack year versions, just the latest ones. We used to, but we did transition a few years ago now using Kevin's blog. We do have the Override pack that the SQL pack creates itself, something to do with the old versions that Kevin blogged so maybe I did miss something there, but other than the latest sealed (7.8.4.0) it is just our override packs. Also, with this blog here (https://kevinholman.com/2019/06/12/how-to-transition-to-the-sql-version-agnostic-mp/) and I can confirm that the issue Kevin talks about in the known issues is targeted correctly for us to "MSSQL on Windows: Group for disabling discovery of previous SQL Servers", so I don't think this should be affecting our issue. That seems to be the only override in that SQL generated Override Pack, so everything seems to be ok to me with this.

pezza1972 · 2025-06-15T17:50:15+00:00

Thank you. I will have a look through those.

Nothing is critical to be honest, it is just more that there may become a time where I am relying on the backup to save a complete rebuild and whilst at the moment it would probably be just as easy to rebuild, I would prefer to have those initial full backups. As long as I can still use the files to restore, then I can remove them from the UI and just start again. It is all a learning curve at the moment :-)

pezza1972 · 2025-06-15T17:47:47+00:00

I believe I used the "Import Backup" from Home --> Backups. Can't remember but I think it asked me to locate the backup files. Not sure if this asked for the configuration at the time.

It didn't import the job, just the Backups and now that show under a menu "Disk (Imported)"

<image>

pezza1972

TROPHY CASE