Hello!
I am trying to follow along this training: https://community.dataminer.services/video/dataminer-inspire-creating-a-driver-from-scratch/ And i have my AWS server setup, like in the training. I added it to DataMiner, but the state is "not initialized" and i cannot perform any tasks on it (as they are described in the training). Can someone explain to me how this initialization works and what i need to do to make it happen?
Many thanks!
Hi Roxanna,
Parameters in an element will show "not initialized" until a value has been set in those parameters.
Parameters can be set from different sources, based on their purpose.
e.g.
-a parameter for a username or password is typically set by the user.
-a parameter representing a KPI is typically set by a retrieved value from the remote data source (through a QAction, action, SNMP reply, etc).
Which parameters are currently "not initialized"?
Have you already added the HTTP sessions, triggers, and actions to your protocol?
Hey, Ive! Thanks for reaching out!
So, what i am trying to do is poll a CloudWatch API from AWS and retrieve information on some metrics of an EC2 instance. i configured the QActions and params as in the video-training, but all i get is “not initialized” on DataMiner Cube. I am trying to attach a picture, but i don’t see the button for it anymore. :/
EDIT: I managed to attach a picture to the question. Also, i wanna mention that i restarted the element in DMCube, as taught in the training, but i don;t get the same result. The trainer gets the field populated with the metric data in json format, i get “not initialized”.
Hi Roxanna,
Thank you for the additional information.
To start the investigation, can you please check the following things:
1. If you right-click the element and choose View -> streamviewer, you get an overview of all communication between DataMiner and the remote data source. Do you see any communication here? (you might need to restart your element to see a request pass by in case you use an after startup trigger).
2. If you right-click the element and choose View -> log, you get the element logging. Are there any errors visible here?
If i do View > Stream Viewer, i see nothing. the window is blank.
this is what i have in View > Logs
Logfile “aws_winserver_api” from agent “10.0.0.4”…
2021/04/14 12:17:56.520|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 5; Error: 5; Debug: 5 (init)
2021/04/14 12:17:56.529|SLDataMiner.exe – aws_winserver_api|8592|CElement::SetState|DBG|0|** Setting state finished.
2021/04/14 12:17:56.530|SLDataMiner.exe – aws_winserver_api|8592|CElement::CreateObjects|INF|-1|** Creating objects for element aws_winserver_api (23)
2021/04/14 12:17:56.530|SLDataMiner.exe – aws_winserver_api|8592|CElement::Start|INF|-1|** Creating objects for element aws_winserver_api (23)
2021/04/14 12:17:56.564|SLDataMiner.exe – aws_winserver_api|8592|CElement::GetPortInfoAsString|DBG|5|0 0 3 0 2 0 3 0 1500 ByPassProxy 80 monitoring.us-east-2.amazonaws.com 30000 0 0 0 -1 1500 0
2021/04/14 12:17:56.565|SLProtocol – 1976 – |16828|CProtocol::InitFunc|CRU|0|– Start Init
2021/04/14 12:17:56.565|SLProtocol – 1976 – |16828|CProtocol::Init|INF|1|Creating protocol Aws cloudwatch api
–> version 1.0.0.1 (1.0.0.1)
2021/04/14 12:17:56.566|SLProtocol – 1976 – |16828|CProtocol::InitFunc|CRU|0|ReadSettings
2021/04/14 12:17:56.596|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|Log elementInProtocol
2021/04/14 12:17:56.604|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeDefinitions
2021/04/14 12:17:56.604|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeParameters
2021/04/14 12:17:56.605|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|LoadOthersAndExceptions
2021/04/14 12:17:56.605|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Simulation
2021/04/14 12:17:56.605|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Element data
2021/04/14 12:17:56.607|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::LoadElementDataSinglePIDs|CRU|-1|Querying elementdata
2021/04/14 12:17:56.640|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Reading item data
2021/04/14 12:17:56.641|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Begin processing parameters
2021/04/14 12:17:56.642|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Find ids
2021/04/14 12:17:56.642|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Removing duplicates
2021/04/14 12:17:56.642|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Initializing hash table
2021/04/14 12:17:56.642|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|Loading parameters
2021/04/14 12:17:56.643|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitializeParameters|CRU|-1|done Loading parameters
2021/04/14 12:17:56.643|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeCommands
2021/04/14 12:17:56.643|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeResponses
2021/04/14 12:17:56.643|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializePairs
2021/04/14 12:17:56.643|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeGroups
2021/04/14 12:17:56.644|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeTimers
2021/04/14 12:17:56.644|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeTriggers
2021/04/14 12:17:56.644|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeActions
2021/04/14 12:17:56.644|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeQActions
2021/04/14 12:17:56.645|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|Cleaning QAction Instances
2021/04/14 12:17:56.646|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeSessions
2021/04/14 12:17:56.646|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupParameters 162(#) * 444(b) = 71928
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CheckDBTables|DBG|-1|BuildIndex for PID 65135 took 0 ms
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CheckDBTables|DBG|-1|BuildIndex for PID 65143 took 0 ms
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CheckDBTables|DBG|-1|BuildIndex for PID 65073 took 0 ms
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CheckDBTables|DBG|-1|BuildIndex for PID 65148 took 0 ms
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CheckDBTables|DBG|-1|BuildIndex for PID 65059 took 0 ms
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CheckDBTables|DBG|-1|BuildIndex for PID 65062 took 0 ms
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::CompleteLoadSequence|DBG|-1|Load Sequence: 65132,65146,65139,65049,65054,65060,65068
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|LinkReadWrite
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeAlarmLevelLinks
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeReplication
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|InitializeVirtualFunctionBinding
2021/04/14 12:17:56.650|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupCommands 0(#) * 112(b) = 0
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupResponses 0(#) * 224(b) = 0
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupPairs 0(#) * 72(b) = 0
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupGroups 2(#) * 116(b) = 232
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupTimers 3(#) * 568(b) = 1704
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CTimer::InitTimerThread|DBG|2| Timer thread started (0x00002DD4 – 6400) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 10000)
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CTimer::InitTimerThread|DBG|2| Timer thread started (0x00002DE0 – 9016) (bInitial = 1, m_uiDataDisplayTime = 30000, m_uiTime = 60000)
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|6400|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CTimer::InitTimerThread|DBG|2| Timer thread started (0x00002DE4 – 1412) (bInitial = 1, m_uiDataDisplayTime = -1, m_uiTime = 3600000)
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupActions 5(#) * 68(b) = 340
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|9016|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupTriggers 4(#) * 84(b) = 336
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|1412|CTimer::TimerThreadFunc|DBG|2|Launched Timer thread
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|MakeCommands
2021/04/14 12:17:56.651|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupQActions 13(#) * 196(b) = 2548
2021/04/14 12:17:56.652|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|SetupSessions 0(#) * 140(b) = 0
2021/04/14 12:17:56.652|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|– Total not filled in size is 77088 b
2021/04/14 12:17:56.652|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::InitFunc|CRU|0|– Done Init
2021/04/14 12:17:56.652|SLDataMiner.exe – aws_winserver_api|8592|CElement::InitializeElement_SLElement|DBG|-1|Initializing SLElement…
2021/04/14 12:17:56.652|SLElement.exe|21804|CElement::Init()|DBG|-1|** Initializing IElement …
2021/04/14 12:17:56.652|SLElement.exe|21804|CElement::ReadSettings|DBG|-1|** Read Settings…
2021/04/14 12:17:56.653|SLElement.exe|21804|CElement::ReadSettings|DBG|-1|** Initialize Connections…
2021/04/14 12:17:56.653|SLElement.exe|21804|CElement::ReadSettings|DBG|-1|** Read Settings Complete…
2021/04/14 12:17:56.653|SLElement.exe|21804|CElement::Init|DBG|-1|** Initializing IElement Complete…
2021/04/14 12:17:56.653|SLDataMiner.exe – aws_winserver_api|8592|CElement::InitializeElement_SLElement|DBG|-1|Notifying view settings…
2021/04/14 12:17:56.653|SLDataMiner.exe – aws_winserver_api|8592|CElement::Start|DBG|-1|Starting protocol…
2021/04/14 12:17:56.653|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::Start|CRU|-1|Starting SLElement
2021/04/14 12:17:56.653|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Starting
2021/04/14 12:17:56.653|SLElement.exe|21804|CElement::Start2|CRU|-1|** Read DB
2021/04/14 12:17:56.653|SLElement.exe|21804|CElement::ReadDB|CRU|-1|** Read DB [latch]
2021/04/14 12:17:56.672|SLElement.exe|21804|CElement::ReadDB|CRU|-1|** Read DB [active alarms]
2021/04/14 12:17:56.687|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Read Templates
2021/04/14 12:17:56.687|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Read Templates
2021/04/14 12:17:56.687|SLElement.exe|21804|ElementStarter::LoadDescriptionParameters|CRU|-1|** Loading parameters from description.xml.
2021/04/14 12:17:56.688|SLElement.exe|21804|ElementStarter::LoadProtocolParameters|CRU|-1|** Loading parameters from protocol’s xml.
2021/04/14 12:17:56.688|SLElement.exe|21804|ElementStarter::LoadControlProtocolParameters|CRU|-1|** Loading parameters from element control protocol.
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Load relations
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65132- is 65132,65139,65146
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65146- is 65132,65139,65146
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65049- is 65049,65054,65060,65068
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65060- is 65049,65054,65060,65068
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65054- is 65049,65054,65060,65068
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65139- is 65132,65139,65146
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadRelations|INF|-1|Lock sequence(1) for PID -65068- is 65049,65054,65060,65068
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Load RCA Chains
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::RefreshPropertySourceInfo|CRU|-1|** Refreshing property source info
2021/04/14 12:17:56.691|SLElement.exe|21804|CElement::RefreshAllProcessingSequences|CRU|-1|** Refreshing all table column processing sequences
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::InitializeAdvancedNaming|CRU|-1|** Initializing Advanced Naming for all tables
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Detect Export protocol information
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Loading information
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Detect topology
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Destructing template
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Destructing filtered template
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Destructing trending
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Destructing filtered trending
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::LoadProtocol|CRU|-1|** Destructed
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::Start2|CRU|-1|** Destructing alarm info
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::Start2|CRU|-1|** Destructed
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Setting alarm count
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Initializing alarm socket
2021/04/14 12:17:56.692|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Checking masked info
2021/04/14 12:17:56.718|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Setting trend info
2021/04/14 12:17:56.718|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Notifying connected elements
2021/04/14 12:17:56.718|SLElement.exe|21804|CElement::StartFunc|CRU|-1|** Start Complete
2021/04/14 12:17:56.721|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::StartFunc|CRU|-1|LoadProperties returnes. 0x00000000
2021/04/14 12:17:56.721|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::Start|CRU|-1|Initializing Port
2021/04/14 12:17:56.721|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::Start|CRU|-1|Starting Timers
2021/04/14 12:17:56.721|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::StartTimers|CRU|0|Starting protocol thread.
2021/04/14 12:17:56.721|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::Start|CRU|-1|Starting Protocol done
2021/04/14 12:17:56.722|SLLog|ApplyLogLevels|CRU|-1|Log Levels: Info: 0; Error: 0; Debug: 0 (custom)
2021/04/14 12:17:56.722|SLDataMiner.exe – aws_winserver_api|8592|CElement::Start|DBG|-1|Complete.
2021/04/14 12:17:56.722|SLDataMiner.exe – aws_winserver_api|8592|CElement::SetState|DBG|0|** Setting state from 1 to 10 (RealState = 4)
2021/04/14 12:17:56.722|SLProtocol – 1976 – aws_winserver_api|4296|CProtocol::ProtocolThreadFunc|CRU|0|[Aws cloudwatch api/1.0.0.1] aws_winserver_api – ProtocolThread
2021/04/14 12:17:56.722|SLDataMiner.exe – aws_winserver_api|8592|CElement::Activate|DBG|0|** Alarm template :
2021/04/14 12:17:56.722|SLProtocol – 1976 – aws_winserver_api|4296|CProtocol::ProtocolThreadFunc|DBG|0|– Waiting for Polling to be enabled.
2021/04/14 12:17:56.722|SLDataMiner.exe – aws_winserver_api|8592|CElement::Activate|DBG|0|** Trend template :
2021/04/14 12:17:56.722|SLDataMiner.exe – aws_winserver_api|8592|CElement::InitializeLock|DBG|0|** Initializing lock status
2021/04/14 12:17:56.723|SLProtocol – 1976 – aws_winserver_api|4296|CProtocol::ProtocolThreadFunc|DBG|0|– Polling enabled.
2021/04/14 12:17:56.749|SLDataMiner.exe – aws_winserver_api|8592|CElement::InitializeLock|DBG|0|** Not locked.
2021/04/14 12:17:56.749|SLDataMiner.exe – aws_winserver_api|8592|CElement::NotifyRedundancy|DBG|0|** Redundancy Changes
2021/04/14 12:17:56.749|SLDataMiner.exe – aws_winserver_api|8592|CElement::NotifyServiceTriggers|DBG|0|** Service Triggers
2021/04/14 12:17:56.750|SLElement.exe|21804|CElement::NotifyAlarmState|DBG|0|** Element Alarmstate changed to 0
2021/04/14 12:17:56.766|SLProtocol – 1976 – aws_winserver_api|15512|CManagedScript::Load|ERR|-1|Compilation failed for QAction 2
(44,136): error CS0103: The name ‘QActionID’ does not exist in the current context
2021/04/14 12:17:56.766|SLManagedScripting.exe|ManagedInterop|ERR|-1|10|No CodeBuilder found for cookie0
2021/04/14 12:17:56.766|SLProtocol – 1976 – aws_winserver_api|4296|CQAction::Run|ERR|-1|QAction [2] triggered by [pid=2/idx=-1/pk=/user=] failed. (0x80040221)
Input: new =
Input: old =
Input: extra =
2021/04/14 12:17:56.781|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients connected Primary = 1, Derived = 0
2021/04/14 12:18:09.421|SLProtocol – 1976 – aws_winserver_api|16828|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients disconnected
2021/04/14 12:28:43.237|SLProtocol – 1976 – aws_winserver_api|12048|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients connected Primary = 1, Derived = 0
2021/04/14 12:29:16.142|SLProtocol – 1976 – aws_winserver_api|12048|CProtocol::HandleAnotherTelnetClient|DBG|0|Telnet clients disconnected
**********
Hi Roxana,
The following line in the logging points us to where things go wrong:
2021/04/14 12:17:56.766|SLProtocol – 1976 – aws_winserver_api|15512|CManagedScript::Load|ERR|-1|Compilation failed for QAction 2
(44,136): error CS0103: The name ‘QActionID’ does not exist in the current context
2021/04/14 12:17:56.766|SLManagedScripting.exe|ManagedInterop|ERR|-1|10|No CodeBuilder found for cookie0
Can you please check in your code for a “QAction” XML tag, where the id= attribute has the value “Qaction_ID” and replace it by a valid unique integer.
Please note that if you have DataMiner Integration Studio (DIS) you can use the validate button in the upper left-hand corner to pinpoint these issues faster.
Hi Roxanna,
Would you be able to share a screenshot of what you get?