configstatus.v1

Key represents config diff key

Uri represents the HTTP URI client can use to GET config diff and associated errors

A_device_id is the serial number of the device on A side (left hand side)

A_type is the config type on A side (left hand side)

A_time is the time at which to fetch config on A side (left hand side)

B_device_id is the serial number of the device on B side (right hand side)

B_type is the config type on B side (right hand side)

B_time is the time at which to fetch config on B side (right hand side)

Line_num represents line number, if any

Configlet_name represents the originating configlet name. Configlet_name

and line_num point to the line where config warning or config error originate.

Device_id is the serial number of the device

Type describes the config type

source_id identifier to distinguish between multiple instances of the source type

source_id is :

configlet name for CONFIG_SOURCE_TYPE_NETWORK_PROVISIONING_CONFIGLET

studio id for CONFIG_SOURCE_TYPE_STUDIO

configlet id for CONFIG_SOURCE_TYPE_STUDIO_STATIC

Number of lines with code no-operation

Number of lines with code IGNORE

Number of lines with code ADD

Number of lines with code DELETE

Number of lines with code CHANGE

Number of designed config errors

Number of designed config warnings

Timestamp at which running config is updated

Timestamp at which designed config is updated

The HTTP URI client can use to GET running config and associated errors

The HTTP URI client can use to GET designed config and associated errors

The HTTP URI client can use to GET config diff and associated errors

Digest (SHA-256) of the config diff.

Uri represents the HTTP URI client can use to GET config body and associated errors

line number in A this diff applies to

line number in B this diff applies to

line number of the parent command in B

content of config line in A

content of config line in B

Config filter code of the line in A

Config filter code of the line in B

line number of the parent command in A

key uniquely identifies the configuration

config describes the security profile config body

nop_lines is the number of lines with code no-operation

ignored_lines is the number of lines with code IGNORE

added_lines is the number of lines with code ADD

deleted_lines is the number of lines with code DELETE

changed_lines is the Number of lines with code CHANGE

digest is the digest (SHA-256 hash) of the security profile configuration diff

running_config_update_time is the timestamp at which running security profile

or running config is updated

designed_config_update_time is the timestamp at which designed security profile or

designed config is updated

key represents security profile config diff key

diff represents diff entries

key uniquely identifies the Summary

summary is the security profile configuration compliance summary

Device_id is the serial number of the device

UNSPECIFIED indicates config line did not match any partial config management (PCM) filter

MANAGED_LINE indicates config line matches managed PCM filter hence is managed

UNMANAGED_LINE indicates config line matches unmanaged PCM filter hence is not managed

CONFIG_SOURCE_TYPE_NETWORK_PROVISIONING_CONFIGLET - configlet created from

the network provisioning workflow.

CONFIG_SOURCE_TYPE_STUDIO - config generated from a regular studio

SCONFIG_SOURCE_TYPE_STUDIO_STATIC - static config from studios framework

IN_SYNC indicates designed config and running config are identical

OUT_OF_SYNC indicates designed config and running config are not identical

NOP indicates no change. A and B are identical at this line

IGNORE indicates a line that’s ignored in either A or B.

One of a_line_num or b_line_num will be -1

ADD is an addition of a line from A

DELETE is deletion of a line from B

CHANGE is a modification to a line in A

DEVICE_WARNING indicates device warning

DEVICE_ERROR indicates device error

UNREACHABLE_DEVICE indicates the device cannot be reached

CONFIG_FILTER_ERROR indicates error from partial config management filters

INTERNAL indicates internal errors

Key uniquely identifies a ConfigDiff instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

ConfigDiff instance in this response.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Error is an optional field.

It should be filled when there is an error in the GetSome process.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each ConfigDiff at end.

* Each ConfigDiff response is fully-specified (all fields set).

* start: Returns the state of each ConfigDiff at start, followed by updates until now.

* Each ConfigDiff response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each ConfigDiff at start, followed by updates

until end.

* Each ConfigDiff response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this ConfigDiff’s last modification.

Operation indicates how the ConfigDiff value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Key uniquely identifies a Configuration instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

Configuration instance in this response.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Error is an optional field.

It should be filled when there is an error in the GetSome process.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each Configuration at end.

* Each Configuration response is fully-specified (all fields set).

* start: Returns the state of each Configuration at start, followed by updates until now.

* Each Configuration response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each Configuration at start, followed by updates

until end.

* Each Configuration response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this Configuration’s last modification.

Operation indicates how the Configuration value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Time holds the timestamp of the last item included in the metadata calculation.

Operation indicates how the value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Count is the number of items present under the conditions of the request.

Key uniquely identifies a SecurityProfileDiff instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

SecurityProfileDiff instance in this response.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Error is an optional field.

It should be filled when there is an error in the GetSome process.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each SecurityProfileDiff at end.

* Each SecurityProfileDiff response is fully-specified (all fields set).

* start: Returns the state of each SecurityProfileDiff at start, followed by updates until now.

* Each SecurityProfileDiff response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each SecurityProfileDiff at start, followed by updates

until end.

* Each SecurityProfileDiff response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this SecurityProfileDiff’s last modification.

Operation indicates how the SecurityProfileDiff value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Key uniquely identifies a SecurityProfileDiffSummary instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

SecurityProfileDiffSummary instance in this response.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Error is an optional field.

It should be filled when there is an error in the GetSome process.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each SecurityProfileDiffSummary at end.

* Each SecurityProfileDiffSummary response is fully-specified (all fields set).

* start: Returns the state of each SecurityProfileDiffSummary at start, followed by updates until now.

* Each SecurityProfileDiffSummary response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each SecurityProfileDiffSummary at start, followed by updates

until end.

* Each SecurityProfileDiffSummary response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this SecurityProfileDiffSummary’s last modification.

Operation indicates how the SecurityProfileDiffSummary value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Key uniquely identifies a SecurityProfile instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

SecurityProfile instance in this response.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Error is an optional field.

It should be filled when there is an error in the GetSome process.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each SecurityProfile at end.

* Each SecurityProfile response is fully-specified (all fields set).

* start: Returns the state of each SecurityProfile at start, followed by updates until now.

* Each SecurityProfile response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each SecurityProfile at start, followed by updates

until end.

* Each SecurityProfile response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this SecurityProfile’s last modification.

Operation indicates how the SecurityProfile value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.

Key uniquely identifies a Summary instance to retrieve.

This value must be populated.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Time carries the (UTC) timestamp of the last-modification of the

Summary instance in this response.

Time indicates the time for which you are interested in the data.

If no time is given, the server will use the time at which it makes the request.

Value is the value requested.

This structure will be fully-populated as it exists in the datastore. If

optional fields were not given at creation, these fields will be empty or

set to default values.

Error is an optional field.

It should be filled when there is an error in the GetSome process.

PartialEqFilter provides a way to server-side filter a GetAll/Subscribe.

This requires all provided fields to be equal to the response.

While transparent to users, this field also allows services to optimize internal

subscriptions if filter(s) are sufficiently specific.

TimeRange allows limiting response data to within a specified time window.

If this field is populated, at least one of the two time fields are required.

For GetAll, the fields start and end can be used as follows:

* end: Returns the state of each Summary at end.

* Each Summary response is fully-specified (all fields set).

* start: Returns the state of each Summary at start, followed by updates until now.

* Each Summary response at start is fully-specified, but updates may be partial.

* start and end: Returns the state of each Summary at start, followed by updates

until end.

* Each Summary response at start is fully-specified, but updates until end may

be partial.

This field is not allowed in the Subscribe RPC.

Value is a value deemed relevant to the initiating request.

This structure will always have its key-field populated. Which other fields are

populated, and why, depends on the value of Operation and what triggered this notification.

Time holds the timestamp of this Summary’s last modification.

Operation indicates how the Summary value in this response should be considered.

Under non-subscribe requests, this value should always be INITIAL. In a subscription,

once all initial data is streamed and the client begins to receive modification updates,

you should not see INITIAL again.