derhally

When you say you can not login, what happens?

I will submit a defect for the documentation to be fixed. Thanks for pointing that out.

The ObjectID is the value of the primary key of the object type. e.g. NodeID for nodes, InterfaceID for interfaces, etc...

The Orion.APM.PortEvidence and Orion.APM.ProcessEvidence entities should give you access to the detail, hourly and daily data. You will notice that the detail stats will have a RecordCount of 1, while stats that were aggregated into Hourly and daily will be higher.

I've updated the code to allow you to specify FieldAssignment as you suggested. I've updated the information in the post. Let me know if that works for you.

Thanks for the feedback. We definitely want to support custom/required fields.

Looks like you have things almost working. We were missing some logging of some errors returned by jira so I've updated the zip attached to the main post with a new build that provides more logging. You can try that and see if it gives any clue. Either way, what kind of Jira project did you create. Do you know if you have…

The image you posted is not showing up. WebhookListenUrlRoot is the url that JIRA will callback on with events. It should be set to the address that is reachable by JIRA. You can also change the port to something that is not currently being used.

What version of Orion are you targeting? I used the latest Orion SDK with the attached script with success.

The logout button is available in IE, and not in FireFox. All it does is try to close the current window you are in which doesn't work in FireFox. The logout button isn't really useful when we are using windows authentication because you will be automatically logged in if you ever go back. In the next service pack we will…

Please do not post the same question to multiple threads. I answered your question in the first thread you posted in.

What hardware are you using for your gateways? That information would helpful for us when looking at polling PRI stats.

Are you logged in using the same account? Or do you have any View Limitations for the view you are on?

I answered your question in the other thread.

Below is what it looks like when I trace my activity. I noticed that there is a typo for the first column in your query, your column is missing the "t", it should be AlertDefID. If you are still having issues look at the service log file to see if it showing any errors. The file should be located at C:\Documents and…

The Unmanage verb takes only one node ID. So you would have to iterate over the results of your query call it once for each node.

We will be releasing service pack 2 for EOC 1.0 that will fix an issue with polling Orion 9.1.

The group members parameter is not correct. The MemberDefinitionInfo needs a Definition element. This definition for a specific group would be something like swis://host/Orion/Orion.Groups/ContainerID=1 so the xml would be something like <ArrayOfMemberDefinitionInfo xmlns='http://schemas.solarwinds.com/2008/Orion'>",…

Were you upgrading from 2.0 to 2.1?

What appears in the event log is based on the trigger action. What Orion shows you is the name of the alert definition. You can get that by using the following SWQL query SELECT Def.Name, AlertStatus.ActiveObject, AlertStatus.ObjectType, ObjectName FROM Orion.AlertStatus JOIN Orion.AlertDefinitions Def ON…

Currently it is no possible to do that with this verb. This verb doesn't support taking that as an argument. The arguments are as follows * DefinitionId * ObjectType * ObjectId * Notes If you wish, you can use the Notes value to store the user who acknowledged the alert.

I'm not sure why that is not working, you can do the following for now. if (!(Get-PSSnapin -Name "SwisSnapin" -ErrorAction SilentlyContinue)){ Add-PSSnapin SwisSnapin -ErrorAction SilentlyContinue}$swisTarget = 'localhost'$username="admin"$password=""$swis = Connect-Swis -host $swisTarget -UserName $username -Password…

You can use the SDK to add entries to the Orion.WorldMap.Point entity. Once you do that, the nodes will show up on the map.

SWQL Studio accepts a select statement that you want to run. If you are familiar with SQL you should be able to construct a similar query in SWQL and run it SWQL Studio The scripts provided need to be run in their respective scripting environments. perl, powershell, python, etc...

VoIP monitor works with 6.0. Also we've found that SNMP support is disabled by default with CUCM 6.1, so enabling the SNMP service in call manager will fix the problem where you get an error saying "Target does not support CISCO-CCM-MIB"

While port 17778 is a valid port in Orion, it is mainly used by 3rd party who want to integrate with Orion. You shouldn't need to open port 17778 between your poller and main server.

This is already possible. There are two scenarios: 1) Go to the view manager in the admin section and edit your views. You can specify the settings of the resources under the resources tab. When you save the changes you can specify whether to push the changes to all users or not. 2) EOC supports personalized pages so that…

VoIP monitor uses udp jitter for its IPSLA operation. From what I've read from cisco documentation it doesn't look like disabling source-routing would effect that. I believe source-routing can be used by operations such as pathJitter and pathEcho which our IPSLA tools do not use.

what is being reported for "Status" when you look at the Operation details resource for that operation?

The creation of the IPSLA operations probably failed. I would open a ticket with support to to help you. Please run the Diagnostics utility and attach the diagnostics file with your ticket in advance so that they can see why it failed.