Chatee ahora con Soporte
Chat con el soporte

Foglight 7.3.0 - Data Model Guide

The Foglight data model Data modeling tutorials Appendix: Groovy scripts Appendix: Internal database schema
acl_class Table acl_entry Table acl_object_identity Table acl_sid Table agent_client_defaults Table agent_config_binder Table agent_dc_manager_schedule_ids Table agent_dc_manager_state Table agent_manager_state Table alarm_alarm Table alarm_annotations Table alarm_loc_msg Table auditing_log Table baseline_config Table baseline_config_properties Table baseline_engine_profile Table baseline_observation_profile Table cartridge_cartridge_relation Table cartridge_components Table cartridge_installed_cartridges Table cartridge_items Table credential_data Table credential_lockbox Table credential_mapping Table credential_mapping_entry Table credential_order Table credential_policy Table current_version Table database_instance_id Table database_version Table derivation_calculation Table derivation_complex_definition Table derivation_definition Table fgl4_migration_agent Table fgl4_migration_data_span Table fgl4_migration_dcm Table fgl4_migration_host Table fgl4_migration_host_mapping Table fgl4_migration_log Table fgl4_migration_server Table incident_affected_objects Table incident_incident Table incident_linked_alarms Table incident_problem_ticket Table incident_problem_tickets Table licensing_licenses Table mgmt_object_size Table mgmt_observation_size Table mgmt_timeslice Table mgmt_timeslice_data_avail Table model_association Table model_property_formula Table model_query_criteria Table obs_binary_* Tables obs_metric_aggregate_* Tables obs_metric_scalar_* Tables obs_string_* Tables pcm_encoded_data Table persistable_config_model Table persistable_script Table persistence_column_mapping Table persistence_db_column Table persistence_db_schema Table persistence_db_table Table persistence_grouping_policy Table persistence_lifecycle Table persistence_lifecycle_period Table persistence_obs_key_purge_age Table persistence_obs_purge Table persistence_obs_purge_age Table persistence_observation_index Table persistence_operation Table persistence_retention_policy Table persistence_rollup_progress Table persistence_rollup_retry Table persistence_storage_config_xml Table persistence_storage_manager Table persistence_timeslice_table Table persistence_topobj_purge_age Table persistence_type_hierarchy Table registry_performance_calendar Table registry_registry_value Table registry_registry_variable Table report_output Table report_schedule Table rule_action_handler Table rule_action_message Table rule_action_registry_reference Table rule_action_variable_reference Table rule_blackout_schedules Table rule_effective_schedules Table rule_expression Table rule_firing_strategy Table rule_messages Table rule_rule Table rule_sev_to_clear_actn_hndlr Table rule_sev_to_fire_actn_hndlr Table rule_severity Table rule_severity_expression Table rule_severity_messages Table schedule_named_schedule Table script_annt Table script_annt_attr Table script_argument Table script_argument_annt Table script_argument_annt_attr Table script_example Table script_return_annt Table script_return_annt_attr Table sec_group Table sec_group_nesting Table sec_group_role_match Table sec_grouprole Table sec_jaas_source Table sec_object Table sec_object_mask Table sec_object_permission Table sec_object_type Table sec_permission Table sec_permission_def Table sec_policy Table sec_resource Table sec_role Table sec_user_alias Table sec_user_obj_permission Table sec_user_res_permission Table sec_usergroup Table sec_userrole Table sec_x_attribute Table sec_x_attribute_value Table tagging_service_mapping Table threshold_bound Table threshold_config Table topology_activity_calendar Table topology_activity_upgrade Table topology_object Table topology_object_history Table topology_property Table topology_property_annotation Table topology_property_history Table topology_property_name Table topology_property_value Table topology_service_state Table topology_type Table topology_type_annotation Table topology_type_history Table upgrade_pending_operations Table wcf_groups_by_cartridges Table wcf_resources Table

What is in "Model Roots"?

What is in “Model Roots”?

The ModelRoots property is essentially a collection of all the ModelRoot instances on the system. This is a subset of the other root properties, because some model roots are not instantiated if the cartridge is not being actively used. The ModelRoots and ModelInstances properties should not be used (especially when developing dashboards) because it is more efficient to use the root property that was added for specific ModelRoot types.

Cartridge developers can add their own element to ModelRoots by extending a special class called CollectionModelRoot.

How are Foglight 4 agents represented?

Foglight 4 agents are represented as follows:

•
Foglight 4 organizes data as tables inside agents running on hosts in an IPMap.
•
Foglight 5 creates objects that mimic this: F4Host, F4Agent, and F4Table.
•
Tooling converts the F4 DCMs into these classes.
•
Data shows up under All Collections > IPMap.
•
One object instance per sample, for example, one object for C:, another for D:.

Why might I need to navigate models?

You need to understand the model when building a query to return data. Alternatively, you might need to construct a path to a particular property of an object. The object lives in data model space; typically, there is more than one pathway to access it. You will want to choose the most efficient of these.

How do I create a model?

The simplest way to create a model is as follows:

1
Diagram the model and analyze it for flaws.
2
Create the cartridgename-topology-types.xml file for all the data types and their relationships in the model.
* 
NOTE: You can name the XML file as best fit for your model. The type definitions are merged into the server, but the XML file is not retained on the server, so there is no possibility of a name clash with XML files existing on the server. Once the cartridge development gets to the stage where there are several artifacts (for example, monitoring policy files, WCF modules, etc.) the cartridgename-topology-types.xml file is added to a cartridge along with the other components.
3
Populate the model using a Groovy script.
Documentos relacionados

The document was helpful.

Seleccionar calificación

I easily found the information I needed.

Seleccionar calificación