>meta->make_immutable;
no Moose;
1;
__END__
=head1 NAME
Zenoss - Perl interface to the Zenoss JSON API
=head1 SYNOPSIS
use Zenoss;
use Data::Dumper;
# Create a Zenoss object
my ponse is now an instance of Zenoss::Response
# now we can do things like
print $response->json();
print $response->http_code();
# get the response in a perl reference
my $ref = $r severity of 0,1,2,3,4 or 5
my $events = $api->events_query(
{
history => JSON::true,
params => {
severity => [0,1,2,3,4,5],
}
finition
my $definition = {
defaults => {
history => JSON::false,
limit => JSON::null,
uid => '/zport/dmd'
}
};
# Check the ar********************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Service - A JSON/ExtDirect interface to operations on services
=head1 SYNOPSIS
use Zenoss;
my $api = Zen defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,ition = {
required => ['uid'],
defaults => {
useFieldSets => JSON::true,
}
};
# Check the args
$self->_check_args($args, $definition);
# ************************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Mib - A JSON/ExtDirect interface to operations on MIBs
=head1 SYNOPSIS
use Zenoss;
my $api = Zenoss- defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,package Zenoss::Response;
use strict;
use JSON qw{};
use Moose;
with 'Zenoss::Error';
#**************************************************************************
# Public Attributes
#***************,
is => 'ro',
handles => {
# Proxy methods to HTTP::Response
json => 'decoded_content',
raw_response => 'as_string',
time => 'current_age',
},
required => 1,
);
# Perl reference format of the JSON return data
has decoded => (
is => 'ro',
isa => 'Ref',
builder =******************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Messaging - A JSON/ExtDirect interface to operations on messages
=head1 SYNOPSIS
use Zenoss;
my $api = Zen defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,
=pod
=head1 NAME
Examples covering the Zenoss JSON API
=head1 OVERVIEW
This page serves as collection of some quick examples designed to get one started. I will
try to add more occasionally.
=heviceName => 'newdevice',
deviceClass => '/Server/Linux',
model => JSON::true,
}
);
# Print the JobID that this device will be processed under
m*********************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Report - A JSON/ExtDirect interface to operations on reports
=head1 SYNOPSIS
use Zenoss;
my $api = Zeno defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,package Zenoss::Router;
use strict;
use File::Find;
use File::Basename;
use JSON qw{};
use LWP::UserAgent;
use HTTP::Request::Common qw{POST};
use Moose;
use Moose::Util qw {apply_all_roles};
use Zen***************************************************************
our $JSON_CONTENT_TYPE; *JSON_CONTENT_TYPE = \q{application/json; charset=utf-8};
#************************************************ease the transaction counter
$self->_increase_transaction_count;
# Build JSON request in HASHREF
my $JSON_DATA = {
action => $args->{'action'},
method => $args->{'method sort => 'lastTime',
dir => 'DESC',
history => JSON::false,
},
};
# Check the args
$self->_check_args($args, $definition);
sort => 'lastTime',
dir => 'DESC',
params => JSON::null,
},
};
# Check the args
$self->_check_args($args, $definition);
#nition = {
defaults => {
direction => 'DESC',
history => JSON::false,
},
};
# Check the args
$self->_check_args($args, $definition);
********************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::ZenPack - A JSON/ExtDirect interface to operations on ZenPacks
=head1 SYNOPSIS
use Zenoss;
my $api = Zen defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python, defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,as I dont have all the information. What I've placed here is what I know
from reading the Zenoss JSON API documentation. In the event the method calls become clearer I will update this.
=head2 $objn = {
defaults => {
updates => JSON::false,
deletion => JSON::false,
sendevent => JSON::false,
sort => 'name',
di
# Argument definition
my $definition = {
defaults => {
monitor => JSON::false,
start => 0,
limit => 50,
sort => 'name',
n = {
defaults => {
updates => JSON::false,
deletion => JSON::false,
sendEvent => JSON::false,
start => 0,
limit defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,*********************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Search - A JSON/ExtDirect interface to operations on searches
=head1 SYNOPSIS
use Zenoss;
my $api = Zenf this module is considered experimental! Zenoss
hasn't documented these calls in the Public API JSON Docs, thus I've pieced together what I could
from reading their code. Also, it would appear that defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,********************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Network - A JSON/ExtDirect interface to operations on networks
=head1 SYNOPSIS
use Zenoss;
my $api = Zen defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,********************************
no Moose;
1;
__END__
=head1 NAME
Zenoss::Router::Process - A JSON/ExtDirect interface to operations on processes
=head1 SYNOPSIS
use Zenoss;
my $api = Ze defaults and return content.
The documentation for this module was mostly taken from the Zenoss JSON API docs. Keep in mind
that their (Zenoss Monitoring System) programming is based around python,*************************************************
# Name: Template.pm
#
# Description: A JSON/ExtDirect interface to operations on templates
#
# Author: Patrick Baker
#
# Version:
# Argument definition
my $definition = {
defaults => {
query => JSON::null,
}
};
# Check the args
$self->_check_args($args, $definition);
#
# Argument definition
my $definition = {
defaults => {
query => JSON::null,
},
required => ['uid'],
};
# Check the args
$self->_check_me API methods
my $response = $api->device_getDevices();
# Print the JSON return
print $response->json;
=head1 DESCRIPTION
This module creates a connection to the Zenoss API, and te