Have you got both background and event manager services running?
yes, they're the only 2 though
Thanks Martyn I'll look into that
OK. Had a good look through that and it looks like it's specifically for itegration with LDSD and LPM. Step 1 asks this question though:
1. Do you have the event generator behaviour on your object within LDSD object designer? (See step 3 if you are unsure how to check this)
2. Do you have rows in the tps_event_queue and / or the ev_event tables in your LDSD database?
3. Within your LPM workflow do you have the web service event near the end of the workflow? (See section x for more details)
If the answers to the above are all yes (or at least 1 and 3 OR 2 and 3) then this guide is for you.
I can only answer yes to question 2 as I'm not using LPM at all. I just want to create an incident when we receive 1 or more specific event types
I don't have an Integration Process Source or a Business Object Source created but that looks like it's for the Round Trip set up. I just want to log an incident and let LDSD handle it from there
More rummaging around and.....
I have the Event/Network Source enabled (it seems to be called 2 different things depending where you look). So each of these events should create a separate incident as they have a different title
The rules I assume is the Event Definition as shown below:
Both Event Definitions test ok and show an individual event when Test is clicked:
The event Definition in the screenshots has the Event Types value set to 'Password Manager' instead of PassWord Manager'. Tyr changing the event definition so that the Value matches the event type exactly (same case).
Well spotted Martyn. I've changed it and restarted the services but no joy
Jason, can you post a new test of your Event Definition results with the Configuration Item in the shot?
Also, not knowing how much you've tested this previously. Event Manager will not process new rows for any tickets its created matching a particular event definition until the previous tickets are at a CLOSED status. That's the other thing you'll want to check. That's the Event Identification parameters trying not to create duplicate tickets for the same thing.
I've never managed to get it to log an incident yet so there are no pre-existing incidents, which makes me think that it might be something to do with the Event Source Identification
Here's the config item
Here are the network source parameters. So i'm assuming if there is a change in any one of the event identifiers it will consider it a new Incident (in my case), unless an incident for it has been closed already
I don't even have a log file being generated though, which makes me think that it's something to do with services but they are starting fine
Yes, that's it. The service is running as a system account but I'#ve tried with a domain admin as well with the same effect
If you're not sure if its working correctly, I'd specifically check steps 18 and 16 in the link that Martyn supplied. One will make sure that the account you're using to run the service is able to login, the second step is to just test it manually. I'd try taking that criteria down to just one test, something where EventType CONTAINS 'password' and see if that picks it up. Then once you have that working increase the criteria afterwards.
Can you list what you have setup in "Event Identification"; is it just the items in view or are some later on down if you scroll?
I assume Parameter 1 is the PC name where the password reset happened though cant quite see from the screenshot. If so that would be expected under Event Identification; assuming you do this as the PC's where you are doing the PW resets aren't instances in the CMDB such that you can reference under Configuration Item column instead?
Then to me you don't need configuration item in there as that will always be "Active Directory" so plays no active part in identifying a specific instance of an Incident. Doesn't stop you mapping it though if you still need to show the "service" affected on the Incident.
Also if it were me I would use Device Status and pass a value "Success" of "Failure" etc to it rather than use the Title but that said it should still work like that OK.